this post was submitted on 01 May 2026
28 points (96.7% liked)

Technology

84257 readers
4038 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
28
Agentic Coding is Burning Me Out | Sid's Blog (0xsid.com)
submitted 1 hour ago by lemmydividebyzero@reddthat.com to c/technology@lemmy.world
10 comments fedilink hide all child comments
top 10 comments
sorted by: hot top controversial new old
[–] TheDarkQuark@lemmy.world 11 points 1 hour ago (4 children)

I never understood vibe coding (or ✨Agentic Coding✨) tbh.

May be I am too stupid, but I think as I code and code as I think. I do not usually formulate a plan before I start coding. I am categorizing architecture as code btw because, for me, architecture involves pseudo-code to some degree .

Even in college, I could never just understand lectures. I needed to write down the formulas and work out the derivations myself to grasp them. I know there are people who understand things right away, but I am not one of them.

So, now, when I see senior developers (which I am not) vibe code green field projects, I am just astounded as to how they manage the architecture + understanding + optimization + maintenance context.

[–] FlordaMan@lemmy.world 8 points 58 minutes ago

For very specific projects I get it. If I want a tool that does X and X is easily verifiable, and I don’t want to learn anything from coding it, then AI might do it very well.

[–] Deestan@lemmy.world 2 points 17 minutes ago* (last edited 7 minutes ago)

I am just astounded as to how they manage the architecture + understanding + optimization + maintenance context.

They don't. They fuck it the shit up. While AI huffers will not hesitate to tell me that actually a hypothetical blabla bla blabla, I have yet to see an agentic coder make something that holds up to reality, safety, reliability, or maintenance.

[–] lIlIlIlIlIlIl@lemmy.world 6 points 57 minutes ago (1 children)

I do not usually formulate a plan before I start coding

Oh noooo

[–] etchinghillside@reddthat.com 1 points 38 minutes ago (1 children)

It’s all vibes mannnn.

[–] errer@lemmy.world 3 points 27 minutes ago

He was vibin’ before it was cool

[–] dhork@lemmy.world 2 points 41 minutes ago* (last edited 40 minutes ago)

So, now, when I see senior developers (which I am not) vibe code green field projects, I am just astounded as to how they manage the architecture + understanding + optimization + maintenance context.

My experience is, they're not. Like the article says they are just focused on MOAR and not on the quality of the output. It may take years for the unmaintainable code to cause problems, and they may have already been laid off by the time that happens, anyway .

I don't write much code anymore, but when I did, there was a fair amount of embedded code, where fixing a bug is more costly than just pushing out a build to a production server. I actively sought out automation back then, but the purpose of the automation was to help cover edge cases and better test the embedded code for flaws that traced through multiple layers of code.

Whenever I start a new software project, it usually starts with a short period of experimentation when I try out several things. Then, I coalesce on an architecture in my head (and eventually document it), and once I do that I can add more structure to the code.

Given the state of the AI tools today, I can see myself using them to accelerate all the little fiddly parts of this (especially if I can give it a coding standard and have it stick to it). But I wouldn't trust it more than that. I would always keep the archictecture separate, because I don't trust the AI tools to change it on me for no good reason.

[–] errer@lemmy.world 2 points 19 minutes ago (1 children)

I do a lot of “disconnected coding,” think scripts that do a long and complicated calculation, triggered manually by a few users, and aren’t online services. In these cases vibe coding is pretty great: if something doesn’t work the first time, I can iterate easily till it does. Very few consequences in getting it wrong other than time. My hand is also very firmly on the wheel and I have a lot of time to think about changes to fix issues or make things better.

Now for an online service with very specific requirements on how it handles inputs and produces outputs, at scale, with security issues, and millions of people using it…yeah I’d be pulling my hair out too if I had to vibe code all that.

[–] corsicanguppy@lemmy.ca 1 points 1 minute ago

till

Cha-ching!

[–] MalReynolds@slrpnk.net 2 points 29 minutes ago* (last edited 26 minutes ago)

Devs are reverse centaurs now.

Lines of code was never a good metric, but it looks like productivity to the C-suite. This will bite them (and everyone who uses the code) in the ass. After some spectacular fails it will be judgement that a Dev is most prized for, meanwhile, this.

Still, eight to ten productive hours a day in any sustained fashion is bullshit, more like 3-4 with a bunch of meetings, learning, deciphering etc. filling out the day.