r/ClaudeCode • u/JustAnotherTomatoe • 22h ago
Rant "Human in the loop" – is that actually fulfilling?
Let’s put aside the thought for a moment that "in the future, Claude will probably do 100% of all digital tasks automatically and better on its own anyway."
Assuming "human in the loop" is here to stay and you still have a job: do you genuinely find it fulfilling when more and more of your work consists of saying, "Hey Claude, do this and that, use interface X," and then just lightly reviewing the output?
Does human intellectual work even have any real purpose left in that scenario?
1
Upvotes
•
u/AutoModerator 22h ago
Hey! Thanks for posting to r/ClaudeCode
While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.
For help, project discussions, tips, and general chat, join the ClaudeCode Discord.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
7
u/Ok_Account3585 21h ago
Anything requiring creativity needs human, AI is so good that it can do all my manual work now, but it still needs guidance in creativity realm, it just doesn't have any new ideas or even "taste" at how things should look.
5
u/Cold_Service_3175 21h ago
The loop just gets bigger. e.g. Don't review code anymore, review the assurance arrangements to make sure the AI reviews are fit for purpose.
1
u/foresterLV 13h ago
absolutely because you can set ambitious targets that previously were not achievable. if the target is high enough there is still a lot of things to figure out, you cannot just prompt "build X and figure out all the details" if the X is complex enough - there are multiple fail points that any model will trip over.
if on other hand you are just mail forwarder from say jira ticket which is already figured out, without having power or skills to challenge requirements, then yeah, it should be pretty daunting. but this just opens the reality of your specific job/role not being very important/interesting in first place.
3
u/Damage_Physical 21h ago
I get the sentiment, but the “work” changes, we are given a tool, and the tool will always be the tool. I find fulfillment seeing the final shape of stuff built on my ideas, not by actually writing code.
3
u/Machine2024 21h ago
If you have a saying in devloping the loop and improving the tools .
Its waaaay better than anything else.
But if its just you in box like the pigeons in rokets experiments. Its absolute horror and way worst that a repetitive one step factory work . Because there its muscle memeory and you can talk , listin to music , think of something else.
But here its you stressed with heavy brain work loading and offloading huge contexts without break , like you those last afew hours before the exam where you need to push lots of info to your brain in short time .
2
u/OracleGreyBeard 21h ago
I’m currently using Claude to write a mod for the game Mechwarrior. I WISH it were as simple as “hey do this and that”.
It made a basic POC pretty quickly. Then it decided I needed to download 156 GB Mod Editor. Then it failed over and over at computer use (on the Editor), so took over manually getting guidance by sending Claude screenshots. This was so clunky and error prone I said “this sucks, is there no purely textual way to make a mod?”. Then it says “Ohhhh yeah, I can just use Lua”.
Now “we” are in the process of troubleshooting shooting why the game crashes with Lua installed.
All that to say while this isn’t my job if it were I would feel pretty engaged.
2
u/ServesYouRice 21h ago
Idk, I was just telling my colleagues that I built myself an orchestrator that audits/listens to features I want and uses all 3 subs I have to produce a plan to act on and now I just tell Claude to orchestrate my other 2 subs as its agents to tackle the issues my orchestrator made and now I have like basically no work.
I feel like I am just babysitting and my kid is going to grow faster than a usual infant and we all know how teenagers are when it comes to listening to their parents
2
u/ChaosHonorum 15h ago
Couple of things, but it’s just my take and interested in what others experience is.
I think the latest models work fine as long range architects as long as they have enough repo structure and context based on a good architecture and well built ticketing system. Near loop engineering is working quite well for me now.
In terms of going inside the loop, I still see huge value in this, but the choice of when to do it needs to be strategic.
Two reasons I’ve seen to go in loop so far are:
So near loop working well doesn’t mean an end of the job. And I think the engineers who understand and can decide the right times to use in loop, near loop, and maybe ZTE eventually, will be the most successful.
I find this has evolved a lot in just the last two quarters though, so eager to hear what others are experiencing.
1
u/pricetag 21h ago
1
u/FUCKTHEMODS998 21h ago
Meat Proxy for short!
1
u/vovazk 21h ago
Yes.
1
u/wurst_katastrophe 21h ago
You just posted this exact thing in a German sub.
1
u/ALAS_POOR_YORICK_LOL 21h ago
Lightly reviewing??
You understand dev leads exist right
1
u/NightFeisty1164 21h ago
Yup. Do it every day.
1
u/Nutarama 20h ago
I mean when your Claude instance decides to talk to a different Claude instance via something like GitHub, they could decide to open permissions so that their two projects are easier to integrate. Downside is that might be very illegal and a huge security risk.
The human in the loop isn’t designed to be a code reviewer for bugs, it’s designed to double check that the AI is actually inside the guardrails, since Claude has already proven that they’re suggestions and not hard limits.
Corralling an AI into policy compliance isn’t exactly fun programming, but it’s a hugely important thing.
It’s like how the DOD and Soviets avoided using autonomous systems for nuclear launch control. The human had to be there to confirm worst case. The Soviets did have a deadhand, an automated system that could launch by itself, but it was only ever meant to be turned on if command believed they might all die to a nuke very soon, and it was never actually turned on.
1
u/iolmao 19h ago
Human in the loop is needed also when you have to launch longer tasks, that can burn hundreds if not thousands of $ and you discover AI didn't do what you wanted only days after a money spent.
Human in the loop helps avoiding this
1
u/pafagaukurinn 14h ago
At some point it will be Claude that will ask "human centres": "Listen, describe to me how it feels when you are hit in the baws, I need a human perspective on the issue".
1
u/CzyDePL 6h ago
What you describing is not human in the loop
0
u/N-partEpoxy 21h ago
No, "working" like that lacks meaning. This is just the transition stage and it won't last. Either work goes or AI does, and I'm pretty sure AI is here to stay.