Sounds like an acceptance test to me!
True. I guess I should actually try it out :)
Readit Newsafro88 commented on How to build a coding agent ghuntley.com/agent/... · Posted by u/ghuntley
A feature is just an issue. The issue is that the feature isn't complete yet.
> 2. Create a script to reproduce the issue
Surely that would send it a bit off the rails to implement a feature?
> 1. Analyze the codebase by finding and reading relevant files
2. Create a script to reproduce the issue
3. Edit the source code to resolve the issue
4. Verify your fix works by running your script again
5. Test edge cases to ensure your fix is robust
This prompt snippet from your instance template is quite useful. I use something like this for getting out of debug loops:
> Analyse the codebase and brainstorm a list of potential root causes for the issue, and rank them from most likely to least likely.
Then create scripts or add debug logging to confirm whether your hypothesis is correct. Rule out root causes from most likely to least by executing your scripts and observing the output in order of likelihood.
Does this mean it's only useful for issue fixes?
afro88 commented on Turning Claude Code into my best design partner betweentheprompts.com/des... · Posted by u/scastiel
This is the key to getting decent feature work out of Claude Code. I've had good success recently using GPT-5 High (in Cursor) to write the plan, then take that to Claude Code to implement.
You can get an extra 15-20% out of it if you also document the parts of the codebase you expect to change first. Let the plan model document how it works, architecture and patterns. Then plan your feature with this in the context. You'll get better code out of it.
Also, make sure you review, revise and/or hand edit the docs and plans too. That pays significant dividends down the line.
afro88 commented on Show HN: Project management system for Claude Code github.com/automazeio/ccp... · Posted by u/aroussi
As someone who can program and used vibe coding, when they use vibe coding and don't look at the output, how do they ensure errors don't compound?
I'll give you that - you can't vibe code, not look at the output, and push to main of a production codebase. Same as writing code normally.
But you can vibe code and auto-edit your way to a good PR. But you're reviewing the code being output when the agent finishes each task. Maybe that's not pure vibe coding?
afro88 commented on Show HN: Project management system for Claude Code github.com/automazeio/ccp... · Posted by u/aroussi
afro88 commented on A guide to Gen AI / LLM vibecoding for expert programmers stochasticlifestyle.com/a... · Posted by u/ChrisRackauckas
> The moment you see it go off the rails, just throw it out. That problem is too hard for Claude, it’s for you now.
Or, any of:
- the problem was too big in scope and needed a stepped plan to refer to and execute step by step
- your instructions weren't clear enough
- the context you provided was missing something crucial it couldn't find agentically, or build knowledge of (in which case, document that part of the codebase first)
- your rules/AGENTS.md/CLAUDE.md needs some additions or tweaking
- you may need a more powerful model to plan implementation first
Just throwing away and moving on is often the wrong choice and you'll get better at using these tools slower. If you're still within the "time it would have taken me to do it myself" window, think about what caused it to go off the rails or fail spectacularly and try giving it another go (not following up, throw away current results and chat and try again with the above in mind)
afro88 commented on A guide to Gen AI / LLM vibecoding for expert programmers stochasticlifestyle.com/a... · Posted by u/ChrisRackauckas
I think I enjoy programming. Vibe coding removes most of the parts that I like. It already looks like hell. I'm probably a minority, but I don't think I'm alone in this.
Do you enjoy the work you had to put in for every single PR? I'm not trying to make a "surely there's 1" annoying argument, but a "surely there's 5-10%".
For me, that's:
- working in legacy parts of the codebase
- anything that requires boilerplate that can't be code genned
- actually writing the code of unit tests (the fun part is making code testable, and coming up with what to test)
- fixing lint issues that can't be auto fixed yet
- removing old feature toggles
- building a temporary test harness
The list goes on. That's not hell. That's getting someone else on the team to do all the stuff you don't enjoy, without ruining someones day.
afro88 commented on Show HN: Project management system for Claude Code github.com/automazeio/ccp... · Posted by u/aroussi
No, this is where this discussion is, since the top comment. Please go elsewhere for straw men.
No one mentioned anything about "people who can't program at all" until your comment. Up until then the discussion was about using LLMs for production ready code. It's a given that people working on production systems know how to program.
afro88 commented on Show HN: Project management system for Claude Code github.com/automazeio/ccp... · Posted by u/aroussi
I don't trust Armin for that, he's too good a developer for vibe coding. The question is whether someone who can't program at all can make something that works well with LLMs, not whether Armin can.
> The question is whether someone who can't program at all can make something that works well with LLMs
Is that where the goalposts are now?