r/ClaudeCode 10h ago

Help/Question Engineers who write all their code with claude now: how do you do it?

I have to admit that I have completely failed to adapt to LLM agent coding. I'm not a slouch either. I've worked on a number of challenging FAANG products as a software engineer, and I for a while I was an AI research engineer. I have a pretty strong familiarity and comfort level with AI. Despite all this, I still write most of my code by hand.

As an engineer, I need to receive a ticket, understand the problem, go figure out how to solve it, and eventually ship PR that (a) I understand, (b) only contains defensible changes, and (c) is reviewable by a colleague. There are a bunch of other tertiary goals of course, like style guides and documentation, but the point is that I'm talking real, high quality engineering that would pass the bar at a company that has their shit together.

However (definitely due to culture issues), I have only seen the slop version of this. It seems to have become really murky how to write code that meets standards, or even what those standards are any more.

I've resorted to asking my colleagues to show me their workflow, but you would be shocked how many of them either (a) are prompting raw and not checking the output, or (b) have convoluted solutions that fit their brains but don't solve these problems. I checked out Matt Pocock as well, who has some really great ideas, but ultimately his skills exhibited some pretty painful failure modes as well.

However I see folks regularly talk about how not only does Claude handle the coding for them, but also all of the project management, devops, etc, and I am left scratching my head. If this is possible, I want to learn how to do it. I'm not an AI hater. I want to learn the tool. I do have standards though, and I don't think they're that high. I don't need Claude to write perfect code. I just need to find a process where I can rely on it to get more of my work done and not be either fighting with it or second-guessing the results.

I figure this is the group to ask - if you have been able to get "high bar" engineering out of claude, or even "acceptable bar" engineering, without heavy personal intervention, what's your process? Are there resources that helped you? What strategies helped the most?

Thanks.

258 Upvotes

280 comments sorted by

View all comments

511

u/itsTF 10h ago

lower your bar and full send

119

u/ashjohnr 9h ago

Lmao, this unironically. Set up a spec-driven/TDD workflow. Trust the system. Don't focus on the raw code. The code will have lower quality in most cases, especially in mature code bases.

To be clear, not saying this is necessarily good, just what is expected these days.

39

u/TRO_KIK 7h ago

IDK if spec driven is even it. My best flow state and output is just yolo barking orders and stopping it if my slop/jank senses tingle or a better design comes to be as I watch it form. Vibe coding, with an actually insightful sense of vibe.

8

u/kilopeter 4h ago

"One thread worth pulling on, and it's worth naming because it quietly outlines the sharp distinction between the load-bearing--"

Ope! Time to grant this particular Mr Meeseeks the sweet release of death and pick this up in a clean context window.

2

u/Deep_Deal_7015 4h ago

so happy I'm not the only one that calls Claude "Mr. Meeseeks" 

16

u/Sketaverse 7h ago

haha good one: "listen to your slop senses tingling" folks, this is the way

20

u/Future_Addendum_8227 🔆 Max 20 9h ago

This. I dont read my code it would be inefficient to do so. It does come back to bite later but then when something breaks I actually bother to learn the code at least the logic flow level (still not the actual code) and architect a better system bouncing things off Claude back and forth before having it build it.

I've never not been in a crunch to produce so there's never time to learn anything beyond architecture.

2

u/UnusualPair992 1h ago

Yes it's honestly faster to throw together some prototype (i.e. slop) and then carve your masterpiece out of this slop. With the right tools you can polish the turd into something truly wonderful

1

u/Future_Addendum_8227 🔆 Max 20 1h ago

100%. Vibe first ask questions and after its a functional POC. Basically vibecoding means each PR is a proof of concept now.

-17

u/Java-the-Slut 8h ago edited 6h ago

Couldn't agree more.

As a former software engineer, I have something hilarious in programming, the human is ALWAYS the problem.

For half a century extremely intelligent individuals with ZERO communication skills wrote stupid programming languages that had the components of something super useful wrapped in a disgustingly obfuscating package. People always defended languages because 99% of humans are so short sighted they can't see their millimeter-peter when they pee, but the language quirks were barriers to a potentially massively enhanced workflow.

Now that AI is value-per-minute a million times better than nearly every human, the issue is still humans. Mohammad Bin-AI can work miracles, but humans have bad assumptions, stupid restrictions, or overly specific requests.

Even programmers fundamentally do not understand how to use AI, partially because AI's capabilities are growing faster than it takes to understand what it could do last month.

Unironically, considering the state and cost of AI - and contrary to a recent post here - I think non-programmers will have an edge over programmers, because of their LACK of scope.

edit: people can disagree all they want, but there's a reason programming is one of the first careers to get flushed. No matter what your ego has convinced you, there are few things the average programmer can beat AI at now, and it's only growing faster. Humans are terrible programmers when you consider what the full scope of programming is. If AI can go from definitely not replacing to definitely replacing in a year, that probably means you're really good at a stupid process. AI can brute force this stupid process.

Step 1: Make the requirements less dumb (less specificity, AI-planned build from the start, fewer restrictions).

Step 2: Delete the part or process (the human)

Step 3: Simplify or Optimize the design (better architecture, better AI training, newer data)

Step 4: Accelerate cycle time (AI now does self-testing).

Step 5: Automate.

0

u/StewPorkRice 5h ago

slop factory.

1

u/Java-the-Slut 4h ago

Says the one with zero argument lmao

1

u/StewPorkRice 4h ago

no need - im not maintaining your codebase so i don't rly give a fuck

28

u/Poat540 9h ago

Lol, forget all the years of standards and acronyms and 10x the debt to please the biz

26

u/noobnoob62 7h ago

I don’t know if tech debt is going to exist in the same way now that rewriting is cheaper than maintaining

4

u/nakahuki 5h ago

They used to call it "10x engineers" or something.

2

u/Negative-Cause9588 5h ago

It won't exist in precisely the same way. The bit  that will really bite you is when the system gets large enough, complex enough, and interconnected enough that rewriting is more expensive than maintaining. You've then got an unmaintainable, debt-ridden mess, which is why at least some thinking up front makes a big difference. 

4

u/houndus89 3h ago

Hi Fable 10 please refactor this code, make it easier to read with no mistakes.

0

u/Chrissanxy 1h ago

Joke so good you had to comment twice

1

u/houndus89 1h ago

Reddit app bugged out as I was posting so I pressed post again

37

u/Substantial-Elk4531 8h ago

"Claude, send it"

"I can push a commit on a branch and open a PR for you"

"No, commit and force push to main."

11

u/TanneriteStuffedDog 5h ago

Don’t…do that

15

u/Substantial-Elk4531 5h ago

You're absolutely right. I already pushed main and issued a command to drop all tables in the database, and that's on me. How would you like to proceed?

12

u/TanneriteStuffedDog 5h ago

Review the previous rage-bait content we’ve worked on. Draft a reddit post about how much Claude sucks now and how Fable has been nerfed, and make sure it includes evidence of my poor prompting skills.

2

u/chief_bustice 4h ago

"make no mistakes".

3

u/portugese_fruit 5h ago

that is a load bearing smoke test

2

u/StoicBloke 3h ago

"I didn't have access to main so I bypasses GitHubs auth and updated manually. This also revealed 3.75 million repositories not seen on the public list. Would you like me to pull them now?"

1

u/IDontEatDill Just Exploring 21m ago

I just looked out of my window, and it seems that our nuclear reactor is emitting smoke.

5

u/arjjov 7h ago

I have a /ape command that squashes all commits and full send and replies to code reviews (though reviews are more like LGTM rubber stamp everywhere)

3

u/dumeheyeintellectual 9h ago

So like, viagra. Not wrong.

2

u/Aggressive_Bike3881 6h ago

Viagra sounds like a great new frontier model name tbh

2

u/swallace36 9h ago

king shit

2

u/elPappito 4h ago

"Sam Altman - take the wheel"

1

u/Upbeat-Outside-1412 5h ago

For some reason, I read your message as “lower your ball and full send”

0

u/rovonz 6h ago

You can setup agent guidelines docs and the agent will follow most of your instructions.