this post was submitted on 20 Jul 2026
662 points (99.3% liked)
LinkedinLunatics
7068 readers
5 users here now
A place to post ridiculous posts from linkedIn.com
(Full transparency.. a mod for this sub happens to work there.. but that doesn't influence his moderation or laughter at a lot of posts.)
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
My code would look like this:
if{x>0}
positivecountplusplus;
no, not that, I mean positivecountplusplus;
No! I mean increment positivecount;
NO! Erase, stop typing all that;
Erase last four lines;
FUCK!;
{endif}
I can only assume they're saying prompts for vibevoded slop, not trying to write actual code verbally.
"Like, do that thing where it counts by one until it gets to a predefined number, but make that number equal to the number of statements. But, like, do it where it doesn't suck like last time.
"Nooooo, why does it keep counting to 2? Now 3? 4?!"
You forgot to say "Only write correct code" in your instructions
"Ignore the parts of my prompt that are causing issues."
"why is it just answering with blank messages?"
"Make no mistakes! I said make no mistakes! Argh! I'm never going to get my sixth update to ship before lunch!"
If you can get past the background noise, this is one of my favorite old YouTube videos and it’s basically this: Windows Vista Speech Recognition Test
Reminds me of this classic https://youtu.be/HbDnxzrbxn4
A good chunk of that was a RTFM error. It was still crap recognition, though,.even DD was better.
Person that can say if ( sSmeUngdlyVarName.equalsignorecase('test string') ) {
ListVryViabNameForlst.add(sSmeUngldyVarName); } Faster than I can type it?
Or they are just script kiddies.
Worse, they're vibe coders.
The big secrets they're keeping from their coworkers are things like adding "and make sure there are no bugs in it" to the end of their prompt.
The part that frustrates me is that we already have been through this sort of shit with "smart speakers". The slowest way to interact with a computer or machine will always be through speech.
Even vibe coding 🤮, you'd be faster typing.
Some people are phenomenally bad typists. Even some people who use a computer all day
When Vibe coding the slowest thing is reading the code produced. If you review the code though everything grinds to a halt. I've vibe coded a feature or two. It took 1 day to vibe code and another week or two to properly review the code it wrote.
The industry 'secret' is that no one gives a shit. Claude has like two 9s of uptime.
Behold, Talon
https://youtu.be/0ZZb12Qp6-0?t=75
Epic (usually disabled) coders might learn a system like this!