Let's start by looking at the simple math of 10-100x productivity. 10x productivity means ten times the outcomes, not ten times the lines of code. This means what you used to ship in a quarter you now ship in a week and a half. These numbers should make even the truest AI believer pause. The amount of product ideation, story point negotiation, bugfixing, code review, waiting for deployments, testing, and QA in that go into what was traditionally 3 months of work is now getting done in 7 work days? For that to happen each and every one of these bottlenecks has to also seen have 10x productivity gains.
Any software engineer who has worked on actual code in an actual company knows this isn't possible. You can't compress the back and forth of 3 months of code review into 1.5 weeks. When you code review you:
Tag your reviewer
Hope they will get to it sooner rather than later (which will be tough because they are apparently code reviewing 10x as much code as before)
Context switch to something else while you wait
See a notification (perhaps immediately, perhaps 2 hours after your reviewer went offline for the day)
Context switch back to the review
Read their comments
Respond accordingly
Rinse and repeat.
This process can be made fairly efficient at a competent company with good standards and communication practices. But you're telling me you made this process 10 times as efficient to handle 10x the work? This simply can not be done.
reify•1mo ago
Curing Your AI 10x Engineer Imposter Syndrome
https://colton.dev/blog/curing-your-ai-10x-engineer-imposter...
The Math
Let's start by looking at the simple math of 10-100x productivity. 10x productivity means ten times the outcomes, not ten times the lines of code. This means what you used to ship in a quarter you now ship in a week and a half. These numbers should make even the truest AI believer pause. The amount of product ideation, story point negotiation, bugfixing, code review, waiting for deployments, testing, and QA in that go into what was traditionally 3 months of work is now getting done in 7 work days? For that to happen each and every one of these bottlenecks has to also seen have 10x productivity gains.
Any software engineer who has worked on actual code in an actual company knows this isn't possible. You can't compress the back and forth of 3 months of code review into 1.5 weeks. When you code review you:
This process can be made fairly efficient at a competent company with good standards and communication practices. But you're telling me you made this process 10 times as efficient to handle 10x the work? This simply can not be done.https://news.ycombinator.com/item?id=44798189