←back to thread

Ask HN: How do you get comfortable with shipping code you haven't reviewed?

7 points fnimick | 1 comments | 15 Dec 25 15:01 UTC | HN request time: 0.192s | source

This is the advice I've gotten on how to adapt to AI driven development at breakneck speed - to the point of having AI tooling write and ship projects in languages the 'operator' doesn't even know. How do you get confidence in a workflow where e.g. a team of agents does development, another team of agents does code review and testing, and then it is shipped without a human ever verifying the implementation?

I hear stories of startup devs deploying 10-30k+ lines of code per day and that a single dev should now be able to build complete products that would ordinarily take engineer-years in under a month. Is this realistic? How do you learn to operate like this?

Show context
Sevii ◴[15 Dec 25 15:30 UTC] No.46275745[source]▶
You get confidence in things by doing them. If you don't have experience doing something, you aren't going to be confident at it. Try vibe coding a few small projects. See how it works out. Try different ways of structuring your instructions to the 'agents'.
replies(1): >>46275803 #
fnimick ◴[15 Dec 25 15:34 UTC] No.46275803[source]▶
Are there public examples of "good instruction" and an iteration process? I have tried and have not been very successful at getting Claude Code to generate correct code for medium sized projects or features.
replies(2): >>46278447 #>>46278693 #
1. Jeremy1026 ◴[15 Dec 25 18:55 UTC] No.46278693[source]▶
I had Claude write a piano webapp (https://webpiano.jcurcioconsulting.com) as a "let's see how this thing works" project. I was pleasantly surprised by the ease of it.

I actually just put together a write up showing my prompts and explaining what was generated after each, if you're interested at all https://jcurcioconsulting.com/posts/how-i-used-claude-code-t...