✳flâneur — a map of the web's best reading
Always Be Shipping - Adam Drake
adamdrake.com · 1,936 words · saved by 1 readers
Adam Drake is an advisor to scale-up tech companies. He writes about ML/AI/crypto/data, leadership, and building tech teams.
Always Be Shipping Introduction Sometimes when I'm advising startups the topic of a feature freeze comes up in a variety of contexts. The context I'm referring to is one in which technical debt, poor architecture decisions, and other related issues, have accumulated in a system to the point that it has become seemingly unmanageable. The situation has allegedly become so dire that all new development of features for the business must stop in order to dedicate all developer time and energy to cleaning up the mess. This cleaning up process, which the technical staff often referred to as refactori
Explore this link on the map →saved by
related reading
- Things You Should Never Do, Part I – Joel on Softwarejoelonsoftware.com
- How I ship projects at big tech companiesseangoedecke.com
- You don’t have to be a founder | MIT Admissionsmitadmissions.org
- Stop saying “technical debt” - Stack Overflowstackoverflow.blog
- Choose Boring Technologyboringtechnology.club
- Karri Saarinen on X: "Every feature should earn its place" / Xx.com
- A Bunch of Programming Advice I'd Give To Myself 15 Years Ago | Marcus' Blogmbuffett.com
- claude code is not making your product betterethanding.substack.com
- The Joel Test: 12 Steps to Better Code – Joel on Softwarejoelonsoftware.com
- Scaling with common sense #2: Being future ready. - Zerodha Tech Blogzerodha.tech
- Technical debt - Wikipediaen.wikipedia.org
- Ask HN: How bad should the code be in a startup? | Hacker Newsnews.ycombinator.com