Heimir Thor Sverrisson, an engineering mentor at MojoTech with over 40 years in software development, dives deep into the critical role of software architecture. He discusses how poor architectural choices lead to failure and shares experiences from mentoring engineers and tackling technical debt. Heimer highlights a major bank's misguided performance fix, emphasizing the importance of upfront design versus agile practices. He also touches on the balance between rapid delivery and thorough planning, and his volunteer work in satellite software design.
40:58
forum Ask episode
web_stories AI Snips
view_agenda Chapters
menu_book Books
auto_awesome Transcript
info_circle Episode notes
insights INSIGHT
Importance of Architecture
Software architecture is the most crucial aspect of maintainability.
A flawed architecture makes building and maintaining software a losing battle.
insights INSIGHT
Architecture Evolution
Initial architectures can be flawed from the start or become unsuitable due to changing requirements or business pivots.
Upfront design and agile methodologies need to find a balance.
insights INSIGHT
Changing Project Landscape
Software development productivity has dramatically increased, enabling more smaller-scale projects.
Modern projects often prioritize rapid delivery, sometimes at the expense of thorough architectural planning.
Get the Snipd Podcast app to discover more snips from this episode
How Jack Welch Gutted the Heartland and Crushed the Soul of Corporate America – And How to Undo His Legacy
David Gelles
Atomic Habits
James Clear
Atomic Habits by James Clear provides a practical and scientifically-backed guide to forming good habits and breaking bad ones. The book introduces the Four Laws of Behavior Change: make it obvious, make it attractive, make it easy, and make it satisfying. It also emphasizes the importance of small, incremental changes (atomic habits) that compound over time to produce significant results. Clear discusses techniques such as habit stacking, optimizing the environment to support desired habits, and focusing on continuous improvement rather than goal fixation. The book is filled with actionable strategies, real-life examples, and stories from various fields, making it a valuable resource for anyone seeking to improve their habits and achieve personal growth[2][4][5].
Heimir Thor Sverrisson joins Robby to discuss the importance of software architecture in long-term maintainability. With over four decades in the industry, Heimir has witnessed firsthand how poor architectural decisions can set teams up for failure. He shares his experiences mentoring engineers, tackling technical debt, and solving large-scale performance problems—including one bank’s misguided attempt to fix system slowness by simply adding more CPUs.
Heimir also discusses his work at MojoTech, the value of code reviews in consulting, and his volunteer efforts designing radiation-tolerant software for satellites.
Episode Highlights
[00:01:12] Why architecture is the foundation of maintainability – Heimir explains why starting with the wrong architecture dooms software projects.
[00:02:20] Upfront design vs. agile methodologies – The tension between planning and iterative development.
[00:03:33] When architecture becomes the problem – How business pivots can render initial designs obsolete.
[00:05:06] The rising demand for rapid software delivery – Why modern projects have less time for deep architectural planning.
[00:06:15] Defining technical debt in practical terms – How to clean up code without waiting for permission.
[00:09:56] The rewrite that never launched – What happens when a company cancels a multi-million-dollar software project.
[00:12:43] How a major bank tackled system slowness the wrong way – Adding CPUs didn’t solve their performance problems.
[00:15:00] Performance tuning as an ongoing process – Why fixing one bottleneck only reveals the next.
[00:22:34] How MojoTech mentors instead of manages – Heimir explains how their consultancy approaches team development.
[00:27:54] Building software for space – How AMSAT develops radiation-resistant software for satellites.
[00:32:52] Staying relevant after four decades in tech – The power of curiosity in a constantly changing industry.
[00:34:26] How AI might (or might not) help maintainable software – Heimir shares his cautious optimism.
[00:37:14] Non-technical book recommendation – The Man Who Broke Capitalism and its relevance to the tech industry.
Jellyis the simplest, most affordable way to deal with your “contact@...” emails.
Tired of sharing an email login, or CCing colleagues to loop them into conversations? Terrified by the dizzying total cost of big-name “customer support” tools? Jelly is the answer. Whether it's for customer support, community organizing, or even managing band emails, Jelly helps your team share an email inbox and manage your conversations in a simple, elegant way. Use the "I got this” feature to communicate responsibility and private comments for internal discussions. Jelly is perfect for small teams — because it was built by a small team. And Jelly is actually affordable —team-based pricing means everyone can pitch in with your team’s conversations with customers, clients, and beyond.
Maintainable 
