This article rings very true for me at my current company, the tech lead is always off to add more fancy new tech to the stack, and we still manage to accumulat

This article rings very true for me at my current company, the tech lead is always off to add more fancy new tech to the stack, and we still manage to accumulate a ton of tech debt. Adding a load of automated tests is the first thing we need to do start being able to iterate more quickly. (I view this as both paying down technical debt and solving the right problem). Thankfully that was discussed just the other day in our tech debt meeting (while the tech lead was saying how we need to add a Neo4j database, a Leucene search index and remote procedure calls - he had read an article saying how that is cool again).