3 ms·
Step 0. Document everything in an organized manner, create runbooks, and forbid knowledge hoarding and manual processes only (so-and-so) knows.
by burnt-resistor 2y ago
Step 0. Document everything in an organized manner, create runbooks, and forbid knowledge hoarding and manual processes only (so-and-so) knows.
- swiftcoder 2y agoWhile it is the platonic ideal for operating an existing service, this is also a great way to kill your velocity if you are an early-stage project which needs to deliver results yesterday, and/or pivot on a dime, in order to stay funded...
- burnt-resistor 2y agoOr kill your velocity by playing with creaky, fragile hacks only you understand that duplicate code and are a huge mess. I've seen countless wannabe startups that stupidly accumulated so much technical debt with a "let's worry about that tomorrow" techbro attitude that they had a relative velocity of zero when asked to make minor changes.
- swiftcoder 2y agoBuilding for rapid iteration is a skill like any other, and a lot of engineers who work in big companies never learned it. Blindly staffing one's early stage startup with BigTech engineers is a pretty good way to tank a startup.