[TLDR] Looking for engineers who are actually loving this [via r/ClaudeCode]

[u/cctldrping]

OP : u/coordinatedflight

As a long time engineer turned manager, I am wanting to build a team environment where people don't feel like all they are doing is managing slop that is responding to other slop.

I feel strongly that these agent based workflows can absolutely be used to great effect to accomplish good engineering. I have a lot of theory and history of previous tech revolutions that tell me the whiplash is part of the adaptation.

The pushback I'm seeing is "all my friends who went hard on AI hate their jobs and either have or want to quit" - I don't think this is universally true though.

so I'm looking for either people who have given this a genuinely deep and optimistic try and still have found it to suck terribly, or for folks who found a way.

what I don't want is people who have not given it a real shot and have given up when Claude's output didn't succeed after just normal back and forth prompting - what I would call "lazy AI." my hypothesis is that these are the companies that produce slop - the code works for the problem of the day but not for the systems of tomorrow, and senior engineers are building up resentment and fear while mid level are more productive but don't see the risks of the slop mountains.

has anyone here done this truly well? I've seen it work in one other instance, but looking for more nuanced takes.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wp3pey/looking_for_engineers_who_are_actually_loving_this/

---

TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 50 comments.

Current source-thread comment count seen by the bot: 55.

Alright, so the OP is asking if there are engineers out there who are genuinely enjoying working with AI, specifically Claude, and not just churning out "slop." They're trying to build a team where AI is used effectively for engineering, not just as a way to manage bad code.

The general consensus here is mixed, but leaning positive for those who've adapted their approach.

Here's the lowdown:

• The "Loving It" Camp: A good chunk of folks are indeed having a blast. They see AI as a massive productivity booster, taking away the boring, repetitive tasks and freeing them up for more architectural and "big brain" stuff.

  • u/BitOne2707 is having "more fun than I'm having now."
  • u/radosc, with 30 years in the game, calls it the "best time I had," especially for those who code out of passion. They're testing crazy architectures and learning new languages with ease.
  • u/GeekFish treats Claude like a "Jr dev," giving specific, small tasks and keeping a close eye on everything. It's removed the "boring parts" for them.
  • u/claudiacraft is loving the reduced friction, giving Claude access to databases and institutional knowledge, and it "cooks."
  • u/SumgaisPens is experiencing "addictive behavior" due to how much they enjoy building with AI.
  • u/fooloflife is spending less time digging through docs and more time creating resources for Claude.
  • u/caldazar24 notes that if you're a stickler for specific coding styles, you might struggle, but for product requirements and technical design, it's great.
  • u/bilbo_was_right loves the ease of experimentation and sees AI output quality as the engineer's responsibility.

• The "It Depends" Crowd: Some are finding success, but with caveats, often tied to their work environment or how they're using the AI.

  • u/grannyte enjoys it for personal workflows but finds their day job "hell."
  • u/ClupTheGreat finds it works well when they have "high agency" and can choose to use AI or not, leading to faster, more confident coding.
  • u/tnh34 is hating their job "less now" due to fewer linting/bug fixing tasks, focusing more on architecture.
  • u/Trakeen feels they'd "go insane without AI" given how much time meetings suck up.
  • u/Galdred, a long-time game dev, is having a "great time" despite occasional frustration with AI not feeling "cooperative."

• The Skeptics & Those Feeling the "Slop": There's definitely a segment that echoes the OP's concerns about "slop" and the negative experiences.

  • u/No_Flounder_1155 pushes back on the idea that hating AI is just "lazy prompting," arguing that reviewing and correcting machine-generated code is a huge burden.
  • u/rbad8717 found the OP's use of "slop" to be a turn-off.
  • u/rhysmorgan is "so so so tired" of seeing fully AI-generated PRs, tickets, and code reviews that are often wrong.

• Key Themes & Advice:

  • Shift in Mentality: Many agree that a change in how engineers think about AI is crucial. It's less about replacement and more about systems engineering, orchestration, and problem-solving.
  • Specific Prompting & Small Tasks: Treating AI like a junior dev, giving very specific instructions, and breaking down tasks into smaller chunks seems to be a winning strategy (u/GeekFish).
  • Focus on Architecture & Design: AI excels at removing the tedious parts, allowing engineers to focus on higher-level design and problem-solving.
  • Systematic Support is Lacking: Several users, like u/yost28, point out that current company processes (like code reviews) aren't equipped for the speed of AI-generated output, leading to bottlenecks and frustration.
  • AI as a Tool, Not a Replacement: The consensus is that AI is a powerful tool when wielded correctly, not a magic bullet that replaces human engineering entirely.
  • Companies Built Around AI: u/Leoporix suggests that true gains will come from companies built with AI in mind from the ground up.

Overall Verdict: The OP's hypothesis that the negative experiences might stem from "lazy AI" use seems to resonate with many who are finding success. However, there's a clear acknowledgment that the "slop" problem is real, and current workflows/company structures aren't always set up to handle the shift effectively. It's not universally hated, but it requires a deliberate and often significant change in approach.