alt Hacker NewsOriginally my workflow was:
- Think about requirement
- Spend 0-360 minutes looking through the code
- Start writing code
- Realize I didn't think about it quite enough and fix the design
- Finish writing code
- Write unit tests
- Submit MR
- Fix MR feedback
Until recently no LLM was able to properly disrupt that, however the release of Opus 4.5 changed that.
Now my workflow is:
- Throw as much context into Opus as possible about what I want in plan mode
- Spend 0-60 minutes refining the plan
- Have Opus do the implementation
- Review all the code and nitpick small things
- Submit MR
- Implement MR feedback
Odd 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?