Bits and Pieces

Often, technical debt is conflated with code quality, and the terms often used interchangeably; it therefore carries a negative connotation. Today, it’s my mission to convince you otherwise.

One thing I have often struggled with reconciling in my time as a software architect, is the ease with which we are willing to decide to spin up new systems, compared to our willingness to retire or replace systems where alternative options may exist.

Deciding to build new software is arguably the single most significant architectural decision in any project, yet it often seems to occur without any real exploration of the problem space, and available products or services we might be able to leverage instead.