Speed vs Quality in Software Development // Beyond Coding Podcast #34 - Patrick Akil & Albert Brand

Maintenance Dilemma

The software maintenance dilemma often revolves around deciding when to continue maintaining existing software versus investing in a new solution. Albert Brand emphasizes the importance of recognizing when a system is no longer viable and the need for discussions on whether to evolve or rebuild software. He notes that the decision is often influenced by business-level considerations, which can lead to costly digital transformations that may not always be justified 1. Patrick Akil adds that the initial quality of software plays a crucial role in its longevity and ability to maintain speed without frequent rebuilds 1.

When can we shove it to its grave? And I think that we should actually have better discussions about that, especially on a business level.

--- Albert Brand

Navigating work challenges, especially in a fast-paced environment, requires mental resilience and adaptability. Albert shares his strategy of jotting down ideas to maintain mental clarity and productivity, even when not in the flow 2.

   

Evolving vs Rebuilding

Evolving versus rebuilding software involves strategic decisions that can significantly impact a company's growth and efficiency. Albert discusses the challenges faced by companies like Uber, which had to scale rapidly and make tough choices between evolving their existing systems or rebuilding them from scratch 3. He highlights the "not invented here syndrome," where companies prefer to build custom solutions rather than utilizing existing tools, often leading to unnecessary complexity 3.

Rebuilding it means that you are busy for a year and then just have to hope that it will be faster than before.

--- Albert Brand

Patrick points out that leveraging off-the-shelf solutions can be a more efficient approach, allowing companies to scale without the burden of constant redevelopment 3.