alt Hacker NewsOdd how you add the time for the requirement analysis but none for the coding.
Then you tell us you leave 83% of the analysis —and the coding— to a code chatbot.
Are you actually more productive or are you going to find out down the line the chatbot missed some requirements and made APIs up to fill up a downstream document and now you better support them by yesterday?
In ye olden days, people doing this would scream at the junior developers. Are you going to scream at your screen?
To be honest, I didn't think too hard about it. I just fired and submitted with the time estimates in there kind of randomly.
You are clearly a naysayer. I get it. I was one too for a long time. Then I found a workflow and a model that was clearly delivering results and that's what I use now.
It's only a matter of time before it happens to everyone, even you. Once you have the aha moment where it works for you, you'll stop asking everyone whether they really know if it's better.
The LLM-based workflow above produces good code at a speed at least as fast as my previous workflow and typically many, many, many times faster with the code produced often using designs I would have never thought of before being able to bounce ideas off an LLM first. The biggest difference, besides the time obviously, is that the energy I need to spend is in very different places between the two.
Before it was thinking about what I needed to do and writing the code.
Now it's thinking about what I need to do and reviewing the code.