| ▲ | gste an hour ago | ||||||||||||||||
I think this is outdated. If you follow spec-driven development, get the model to do all the planning work upfront, review and iterate the plan, write clear markdown file documentation on the abstractions and patterns you want to follow, then you have every opportunity to tell the model how you want it to write the code. If you use Opus or Fable 5 it will then write the code better and faster than you will. | |||||||||||||||||
| ▲ | eikenberry an hour ago | parent | next [-] | ||||||||||||||||
IMO "get the model to do all the planning work upfront, review and iterate the plan" is backwards. It works better if you do an initial plan yourself and then have the AI review it (and iterate as necessary). Makes you think about the design for a bit so you can have a semblance of a mental model. | |||||||||||||||||
| |||||||||||||||||
| ▲ | theptip 41 minutes ago | parent | prev | next [-] | ||||||||||||||||
Agreed, all of the staff/principal engineers I work with are ~99%+ AI generated code, and increasing business value delivered as a result. This is on planet scale infra not CRUD apps. (And yes, you do need to carefully review the output and give steers/corrections. It’s still faster.) At this point if you can’t get the agent to write good code then either I) you are in a very specific niche (like Karpathy trying to write NanoGPT) that is extremely out-of-distribution, or II) skill issue, you need to learn how to prompt better. It’s fine to have a skill gap! Just don’t delude yourself that the tools are bad and everyone claiming they are good is wrong. | |||||||||||||||||
| |||||||||||||||||
| ▲ | whatevaa an hour ago | parent | prev | next [-] | ||||||||||||||||
Sure. But try it on a project on non-trivial size and then tell us the cost of it. LLMS are billed per token. | |||||||||||||||||
| ▲ | written-beyond an hour ago | parent | prev [-] | ||||||||||||||||
Depends on how long that planning/review cycle takes. | |||||||||||||||||