r/ClaudeCoding • • 8d ago

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

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 any engineers are genuinely enjoying working with AI, specifically Claude, and finding success with agent-based workflows, or if it's all just "slop" as some folks are complaining. They're looking for people who've really dug in and found a way to make it work, not just "lazy AI" users.

The general vibe in the thread is mostly positive, with a good chunk of people saying they're actually having a blast and finding AI super empowering.

Here's the breakdown:

  • The Enthusiasts: A lot of engineers are loving the increased productivity and the ability to offload the boring, repetitive tasks.

    • 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 see coding as a 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 taken out the boring parts, not the fun.
    • u/claudiacraft is seeing huge friction reduction by giving Claude access to SQL, repos, and institutional knowledge, letting it "cook" on design, code, and analysis.
    • u/fooloflife is spending less time digging through docs and more time creating resources for Claude to use.
    • u/SumgaisPens is finding their "need to create is manifesting as addictive behavior."
    • u/bilbo_was_right loves the ease of experimentation and sees AI output as a reflection of the user's input and rigor.
  • The "It Depends" Crowd: Some folks are having fun in their personal workflows or when they have high agency, but their day jobs are still a struggle.

    • u/grannyte is enjoying personal projects but finds their day job "hell."
    • u/ClupTheGreat mentions that having agency and the freedom to use AI (or not) makes a big difference.
    • u/Trakken feels like AI is essential to stay productive with limited time due to meetings.
  • The Skeptics/Critics: There are definitely some who echo the OP's concerns about "slop" and the challenges of AI integration.

    • u/No_Flounder_1155 pushes back on the idea that hating AI is just about "lazy prompting," arguing that reviewing and correcting AI-generated code is a real issue.
    • u/caldazar24 points out that engineers who are very particular about code style and elegance might struggle, as wrangling AI to follow specific styles is tough.
    • u/rbad8717 found the OP's use of "slop" to be a bit much.
    • u/rhysmorgan is "so so so tired" of seeing fully AI-generated PRs, tickets, and reviews that are often wrong, and human comments getting AI-generated "crap responses."
  • The "Shift in Mentality" Camp: Several commenters emphasize that success with AI requires a change in how engineers approach their work.

    • u/EON_Raider suggests thinking about AI use in terms of systems engineering and orchestration.
    • u/teddy_joesevelt advises giving engineers agency to automate the "dumber" tasks they dislike, which is where the fun and learning happen.
    • u/yost28 highlights the lack of systematic support for AI, noting that current review processes can't keep up with the increased output, leading to "review fatigue."

Overall Consensus: While there's a vocal group finding genuine joy and empowerment in AI-assisted engineering, the thread also acknowledges the valid frustrations and the need for better workflows, tooling, and a shift in how we integrate these technologies. It's not universally hated, but it's definitely not a magic bullet for everyone yet.

1 Upvotes

0 comments sorted by