But I’ve come full circle and have gone back to hand coding after a couple years of fighting LLMs. I’m tired of coaxing their style and fixing their bugs - some of which are just really dumb and some are devious.
Artisanal hand craft for me!
But I’ve come full circle and have gone back to hand coding after a couple years of fighting LLMs. I’m tired of coaxing their style and fixing their bugs - some of which are just really dumb and some are devious.
Artisanal hand craft for me!
It’s just not worth it anymore for anything that is part of an actual product.
Occasionally I will still churn out little scripts or methods from scratch that are low risk - but anything that gets to prod is pretty much hand coded again.
https://github.com/BeehiveInnovations/zen-mcp-server/blob/ma...
It basically uses multiple different LLMs from different providers to debate a change or code review. Opus 4.1, Gemini 2.5 Pro, and GPT-5 all have a go at it before it writes out plans or makes changes.
along with improving my skills in vim, this approach has made me significantly more productive and has made my code much simpler compared to when i was using LLM code generation tools.
there is no shortcut around hard work.
there is no shortcut to thoroughly interrogating the constraints of the software problem at hand.
developers who rely on LLM code generation are poor coworkers because they don't understand what they've written and why they've written it.
why are you looking for a shortcut? just do the work.
It is faster, right now, to just write it myself; at least for most things. I definitely want to understand when and how that might change.
Judging from the downvotes, not everybody shares that curiosity.