Refreshing to see an honest and balanced take on AI coding. This is what real AI-assisted coding looks like once you get past the initial wow factor of having the AI write code that executes and does what you asked. This experience is familiar to every serious software engineer who has used AI code gen and then reviewed the output: > But when I reviewed the codebase in detail in late January, the downside was obvious…
For me it’s just a matter of “does this actually save me time at all?” If it generates the slop version in a week but it takes me 3 more weeks to clean it up, could I have I just done it right the first time myself in 4 weeks instead? How much money have I wasted in tokens?
2. Make it pretty
3. Make it fast.
If you have something that's pretty and fast but doesn't work, is that useful?
But if you have something that works, but is ugly and slow - you can still use it and fix it while you dogfood it. Maybe figure out other ways to improve it beyond making the code look pretty.