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
saved by
related reading
- How I ship projects at big tech companiesseangoedecke.com
- How To Do Lessalexturek.com
- AI is removing the middle class of software engineeringblog.florianherrengt.com
- Managing technical debt at an agile companyvadimkravcenko.com
- Shipping at Inference-Speed | Peter Steinbergersteipete.me
- Thoughts on slowing the fuck downmariozechner.at
- A Bunch of Programming Advice I'd Give To Myself 15 Years Ago | Marcus' Blogmbuffett.com
- Notes on software qualityanthonyhobday.com
- Technical debt - Wikipediaen.wikipedia.org
- Why I Ignore The Spotlight as a Staff Engineer - Lalit Magantilalitm.com
- How to move fast toward the right thingfigma.com
- The Curse of Knowing How, or; Fixing Everything | Blognotashelf.dev