71–80 of 96 posts
But business logic that needs to be trusted? Nooooo.
So very, very rarely 1000% faster. Most of the time 10% slower as I have to find and fix issues.
I'll still say it's a net improvement, but not by much. So let's say 10%.
Earlier quoted context omitted.
If you were 20x faster you'd have done an entire career's worth of progress this year. Have you? Are you making tons of money? Have you achieved 20x the amount than you have all previous years? Take a step back and realize what you're claiming here.
While the multiplier is less for me ( perhaps 3x or 4x ) I think the assumption that productivity gain leads to directly to more money is bit optimistic. Unless you are self employed, or run your own company, and actually get paid by results, being more efficient is seldom paid much. ( with luck you get promotion every two years or so or pay raise every year ) I have worked for too long in the field, but this year an…
It’s immeasurable. I use AI for powering through personal projects, which would not have gotten done without AI because I also have a job and a life. It allows me to focus on the product and requirements rather than the code. It’s hard to measure because the projects would simply not have gotten done without it.
The most fascinating thing about AI is how in a thread like this one, answers range between 0% and infinity.
Personally I do not trust for a second self-reports anyways. They are bound to be wrong.
If we talk about my whole team output, I'd say the impact on code production is like 80-100%, but the impact in velocity is between 10% and -25%. So many bug in production, security holes, so many poor models definition making it to production DB only for me and the other true senior to have to fix it.
We are seniors, we read your PRs and try our best to do it thoroughly, but with AI multiplying your code output, and writing quite convincing solutions, it's way harder, so please: if an AI have written the code in your PR, verify the tests are not superficial, verify everything works, think for yourself about what the model is used for and if it can be improved before release. Re-verify the tests (especially if the AI had issues writing/passing them). And do it once more. Please (hopefully one of my coworkers will read this).
For example, writing UI components maybe easier on some language than writing abstract algorithms, writing standardized solutions (i.e. text-book algorithms, features, etc) is easier than writing customized algorithms, etc.
Also, writing code can be very fast if you don't unit test it, especially for CURD apps. In fact most of my coding time was spent on writing unit tests.
I really hoped AI could write those tests for me to lock the specs of the design completely down. But currently it's the opposite, I have to write test for AI generated code. So, my over all experience can be described as the tyranny of reading other people's code times 10.
It made me 2x slower, because with Claude's hallucinations I waste more time chasing dead ends than I gain from it in productivity.
[flagged]
They could just be bad at prompting (remarkably common amongst engineers who don’t manage humans well),
they could be using a “tired” free account (these free accounts are so widely variable in effort it’s actually shocking).