
Sign up to save your podcasts
Or


“The goal of software is often to sustain an organization. An organization invests in software in order to achieve some goal and hopefully to sustain itself in helping it achieve that goal."
Mark Seemann is an acclaimed author, international speaker, and a highly experienced developer. In this episode, Mark shared some insights from his latest book, “Code That Fits in Your Head”, on how to write sustainable software and manage software complexity. Mark first started by sharing why he wrote this book and explained why software development is hard. He also pointed out the difference between software engineering and other physical engineering disciplines, especially on the set of constraints. Mark then explained the importance of writing sustainable software and shared the perspective that code is a liability instead of an asset. Towards the end, Mark shared about the Rule of 7 as a guideline to manage code complexity and a few practices we can use to build sustainable software, such as checklist, vertical slice, x-driven development, and command query separation.
Listen out for:
_____
Mark Seemann’s Bio
Follow Mark:
Our Sponsor
Today’s episode is proudly sponsored by Skills Matter, the global community and events platform for software professionals.
Like this episode?
By Henry Suryawirawan4.7
1313 ratings
“The goal of software is often to sustain an organization. An organization invests in software in order to achieve some goal and hopefully to sustain itself in helping it achieve that goal."
Mark Seemann is an acclaimed author, international speaker, and a highly experienced developer. In this episode, Mark shared some insights from his latest book, “Code That Fits in Your Head”, on how to write sustainable software and manage software complexity. Mark first started by sharing why he wrote this book and explained why software development is hard. He also pointed out the difference between software engineering and other physical engineering disciplines, especially on the set of constraints. Mark then explained the importance of writing sustainable software and shared the perspective that code is a liability instead of an asset. Towards the end, Mark shared about the Rule of 7 as a guideline to manage code complexity and a few practices we can use to build sustainable software, such as checklist, vertical slice, x-driven development, and command query separation.
Listen out for:
_____
Mark Seemann’s Bio
Follow Mark:
Our Sponsor
Today’s episode is proudly sponsored by Skills Matter, the global community and events platform for software professionals.
Like this episode?

272 Listeners

383 Listeners

290 Listeners

622 Listeners

584 Listeners

288 Listeners

43 Listeners

302 Listeners

228 Listeners

986 Listeners

189 Listeners

205 Listeners

204 Listeners

63 Listeners

228 Listeners