In 2010, hosting was a solved problem. You no longer needed to set up servers. A cloud account, and you were good to go.
Topic
Technical Debt
A collection of 13 issues
Throughout software development history, we have kept trying to hide complexity behind black boxes. JavaScript frameworks abstracted away how browsers render pages. WYSIWYG editors
Rebuilds have an expiry date. Every day a team isn’t shipping the new version, they move one step closer to declaring bankruptcy on
In the early days, technical co-founders were used to shipping fast. It meant SSH’ing into the production server and pushing straight to production.
This won’t take weeks, I know a library that can do this. I’ll have it implemented by tomorrow. It’s a familiar
Have you ever had a plumber come to your house, take one look at the pipes, and say, “What on earth did the last
Too often, I see founders outsourcing their software development to a freelancer or an agency—only to let them create infrastructure on their accounts.
Rebuilding a system is never my first choice, but sometimes it’s the only viable path forward. For example, years ago, many teams built
Have you ever heard this from a stakeholder? "The engineering team keeps talking about technical debt. I don't understand what they
I've previously discussed the consequences of technical debt. Let's explore an aspect that's often invisible to non-technical stakeholders: