Software is like gardening - one day I'll go behind the shed and clean up. But if nobody ever goes there, does... — Mike Krieger

Software is like gardening - one day I'll go behind the shed and clean up. But if nobody ever goes there, does it matter a lot?

Author: Mike Krieger

Insight: There's something honest about treating technical debt like the messy corner behind the shed. We all know it's there. We all plan to deal with it eventually. But there's also a strange logic to asking: if the software still works, if users don't trip over it, does cleaning it up actually matter? The uncomfortable part is that this mindset usually wins until it suddenly doesn't. A small pile of shortcuts becomes a foundation made of toothpicks. Then one day a small change breaks everything, or onboarding a new developer becomes a nightmare, or the whole thing moves so slowly you can feel the drag. The "nobody's looking back there" approach works great until the moment it doesn't, and by then the cost of cleanup has multiplied. What makes this quote resonate isn't that it's right—it's that it captures a real tension in how we work. We're always choosing between shipping and polish, between solving today's problem and preventing tomorrow's. The trick isn't deciding maintenance never matters. It's recognizing that behind-the-shed work compounds invisibly, and occasionally going back there isn't optional—it's just preventive.

When neglect suddenly costs everything

Software is like gardening - one day I'll go behind the shed and clean up. But if nobody ever goes there, does it matter a lot?

There's something honest about treating technical debt like the messy corner behind the shed. We all know it's there. We all plan to deal with it eventually. But there's also a strange logic to asking: if the software still works, if users don't trip over it, does cleaning it up actually matter?

The uncomfortable part is that this mindset usually wins until it suddenly doesn't. A small pile of shortcuts becomes a foundation made of toothpicks. Then one day a small change breaks everything, or onboarding a new developer becomes a nightmare, or the whole thing moves so slowly you can feel the drag. The "nobody's looking back there" approach works great until the moment it doesn't, and by then the cost of cleanup has multiplied.

What makes this quote resonate isn't that it's right—it's that it captures a real tension in how we work. We're always choosing between shipping and polish, between solving today's problem and preventing tomorrow's. The trick isn't deciding maintenance never matters. It's recognizing that behind-the-shed work compounds invisibly, and occasionally going back there isn't optional—it's just preventive.

AI generated

Comments

Sign in to leave a comment or reply to one.

Sign in

Mike Krieger

Mike Krieger is a Brazilian-American entrepreneur and technologist, best known as the co-founder of Instagram, a popular photo and video sharing social media platform launched in 2010. He played a crucial role in the app's development and user experience design, helping it gain a massive user base before it was acquired by Facebook in 2012. Krieger's work has had a significant impact on social media and mobile app innovation.

Graph

Related