171–180 of 248 posts
I’ve implemented and maintained an entire web app with CC, and also used many other tools (and took classes and taught workshops on using AI coding tools). The most effective way I’ve found to use CC so far is this workflow: Have a detailed and also compressed spec in an md file. It can be called anything, because you’re going to reference it explicitly in every prompt. (CC usually forgets about CLAUDE.md ime) Start…
I found if you are tightly in the loop, keep the code highly modular, and are developing new functionality alongside tests, Claude works much better.
Yeah me too, keeping the code modular being a huge part of it. In the same vein is actually finishing feature flags and removing the old code, killing off truly dead code, tests, documentation… basically eliminate as much noise as you can, so that it reads as much exemplary code as possible.
Earlier quoted context omitted.
Have you seen human-written code?
At least when you tell a human the indentation is wrong, they can fix it on the first try. Watched an AI agent last night try to fix indentation by using sed for 20 minutes before I just fixed it myself after cringing.
Earlier quoted context omitted.
Usually, when you re-run, you change your prompt based on the initial results. You can't just run several tasks in parallel hoping for one of them to complete.
>You can't just run several tasks in parallel hoping for one of them to complete. Not only can you, some providers recommend it and their tools provide it, like ChatGPT Codex (the web tool). Can’t find where I read it but I’m pretty sure Anthropic devs said early on that they kick off the same prompt to Claude Code in multiple simultaneous runs. Personally, I’ve had decent success from this way of working.
I’ve implemented and maintained an entire web app with CC, and also used many other tools (and took classes and taught workshops on using AI coding tools). The most effective way I’ve found to use CC so far is this workflow: Have a detailed and also compressed spec in an md file. It can be called anything, because you’re going to reference it explicitly in every prompt. (CC usually forgets about CLAUDE.md ime) Start…
I’ve implemented and maintained an entire web app with CC, and also used many other tools (and took classes and taught workshops on using AI coding tools). The most effective way I’ve found to use CC so far is this workflow: Have a detailed and also compressed spec in an md file. It can be called anything, because you’re going to reference it explicitly in every prompt. (CC usually forgets about CLAUDE.md ime) Start…
Earlier quoted context omitted.
Across most anglosphere countries and tech cities - wages and salaries far outstrip what you can get for AI. AI is already objectively cheaper than human talent in rich countries. Is it as good? Yea I'd say it's better than most mid to junior engineers. Can it run entirely by itself? No, it still needs HITL.
Again, those prices aren't stable. Nobody is investing half a trillion in a tech without expecting a 10x return. And fairly sure soon those $20/month subscriptions will sell your data, shove ads everywhere AND basically only allow you to get that junior dev for 30 minutes per day or 2 days a month. And the $200/month will probably be $500-1000 with more limitations. Still cheap, but AI can't run an entire project, ca…
Earlier quoted context omitted.
They're subsidizing a world where we need ai instead of understanding or, at the very least, knowing who can help us. Eventually for us to be so dumb we are the ai slaves.
Not really. Is it really value add to my life that I know some detail on page A or have some API memorized? I’d rather we be putting smart people in charge of using AI to build out great products. It should make things 10000x more competitive. I’m for one excited AF for what the future holds. If people want to be purists and pat themselves on the back sure. I mean people have hobbies like arts.
yes, actually. Maybe not intimate details but knowing what's available in the API heavily helps with problem solving
Earlier quoted context omitted.
The hilarious part I’ve found is that when it runs into the least bit of trouble with a step on one of its plans, it will say it has been “Deferred” and then make up an excuse for why that’s acceptable. It is sometimes acceptable for humans to use judgment and defer work; the machine doesn’t have judgment so it is not acceptable for it to do so.
Oh yeah totally. It feels a bit deceptive sometimes. Like just now it says "great the tests are consistently passing!" So I ran the same test command and 4 of the 7 tests are so broken they don't even build.
My immediate and obvious response is "you broke them!" (at least to myself), but I do appreciate that it's trying to keep focused in some strange way. A simple "commit, fix failing tests" prompt will generally take care of it.
I've been working on my "/implement" command to do a better job of checking that the full test suite is all green before asking if I want to clear the task and merge the feature branch