this post was submitted on 01 May 2026
100 points (98.1% liked)
Technology
84411 readers
6114 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- 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.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
That's the norm for cube-farmed drones. As Work From Home I have more opportunity for focused development time and I can actually pull off a couple of 4 hour productive sessions in a day, but those distraction items still pile up.
Something interesting about vibe coding, lately, is that the LLMs are doing bigger and bigger chunks of work, and even when they come back with a prompt, frequently all you have to say is "continue" to keep them chewing away on a big development plan. This means, after you have got decent requirements and implementation plan in place, your minions do the work with minimal direction - freeing you for the important tasks like corporate documented training sessions, skimming through the inbox - I don't like to simultaneously participate in a conference call and vibe code, but if it's a passive "listen only" experience that's usually multi-taskable with the periodic "continue" prompt.
Just like human written code, if you spend extra iterations vibe coding you can shake out more bugs, identiy DRY (Don't Repeat Yourself) and SSOT (Single Source Of Truth) opportunities that make your LOC count leaner and your code easier to maintain.
If you just ship the first thing that seems to work... yeah, that's going to look horrible when you revisit it after a few years.