Echo JS 0.11.0

<~>
tracker1 9 days ago. link 1 point
Keeping this since it's specific to a node-based workflow, even though there's not really JS content.

I would suggest that you &NEED& to spend a fair amount of time in planning in order to get what you expect... I've been using Claude Code with Opus as I personally find whatever Github Copilot uses by default to be annoying by comparison.

That said, the results don't exactly surprise me, as a lot was left indeterminant or otherwise unspecified... if you've ever worked with an overseas or otherwise disconnected development team, you will see similar results, but you're waiting until the next business day to continue, where AI is generally minutes away.

I've been able to achieve what I consider amazing results from AI, so long as I spend the time in clarification and enter with an understanding of the likely "miss" points that could happen from anyone.  I have a project I'm about to release that I literally spent just a day with an AI agent, and have a couple hours to go, that would have taken me at least a month of full time work.

I will say that I feel it's important to have a skill level to be able to do it yourself to get the best results.  You need to know/understand what is being produced to best understand what is wrong, where and how it is wrong and how to refine the results.

Replies