This is the right way to look at things now. It might not always have the right track record, but AI built coding is more likely to have all the right permissions in place by default, most likely to copy existing patterns in your codebase, most likely to use the highest performance patterns and on top of all that, the spec will match what was asked of it.

▲

codemog 6 hours ago | parent | next [-]

What magical AI are you using? That’s not my experience at all.

	▲	loeg 6 hours ago \| parent \| next [-]
		Claude with the 4.7 model is getting pretty good.
	▲	sterlind 6 hours ago \| parent \| prev [-]
		there is a significant learning curve to using AI well. learning to stay skeptical and keep your brain on, developing an intuition of how much free reign to give it, writing ironclad specs and design docs and keeping them updated, making work easy to inspect, the tone you use talking to it, using one agent to critique another's work, etc. basically, AI will produce slop if left unattended. but it's not really its fault.. it's a process failing, like not supervising the interns. using AI the Right Way(tm) is a mental workout, quite a bit slower, but extremely rewarding (ime.)

▲

crooked-v 6 hours ago | parent | prev [-]

I can't even get LLMs to reliably use tool calls instead of bash, let alone follow existing patterns in a codebase.

	▲	echelon 2 hours ago \| parent [-]
		What do your prompts look like? Mine are pretty robust and articulate. I tend to write very lengthy instructions and include snippets of code, file paths, struct names, etc.