By all means, if my goal is actually crafting anything.

Usually it isn't, though - I just want to pump out code changes ASAP (but not sooner).

Even then I’ve mostly given up. I’ve seen LLMs change from snake case to camel case for a single method and leave the rest untouched. I’ve seen them completely fabricate APIs to non existent libraries. I’ve seen them get mathematical formulae completely wrong. I’ve seen it make entire methods for things that are builtins of a library I’m already using.

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.

▲

gardnr 6 days ago | parent [-]

This changed my experience significantly:

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.

▲

jennyholzer 5 days ago | parent [-]

it's a lot faster and a lot easier and it gives you a much better understanding of the problem if you just think about the changes you want to make and write them yourself.

why are you looking for a shortcut? just do the work.

	▲	gardnr 5 days ago \| parent [-]
		I feel like it’s my job to understand new tools and keep abreast of the way things are changing in my industry. 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.