|
|
|
|
|
by skybrian
497 days ago
|
|
When one bottleneck is removed, that usually means the rate of change is bottlenecked somewhere else. Maybe in the release process, or testing? Or maybe the bottleneck is the willingness of customers to try new things? Risk-adverse customers will often avoid startups. Showing yourself to be trustworthy isn’t purely about the rate of feature development. If the other bottlenecks can’t be removed easily, instead of 10x features you could end up with fewer software developers. |
|
Having worked at early stage startups and mid sized companies there's already a 10-20x productivity gap between them due to this (even on brand new projects at large companies vs startups, where it's not an issue of legacy code).
As an example I just witnessed a large co hire a consulting company to help them "ideate" on a RAG app that barely worked and required 3 rewrites and ~18 months to make it to POC stage, even though a front end dev had a better working POC that he hacked together in a day and a half.
I've heard way worse horror stories from friends at Google / Meta / Apple.
What will happen when tiny startups of 3-8 people get 5-20x more productive and can ship new stuff daily?