228
idk if it is serious or not, but it is what I saw in indeed newsletter today.
Amazed they didn't ask for 5-10 years of experience in AI coding.
wait for it! PHD in vibe coding or relevant experience
“Senior” is implying exactly that, I thought…
Dude, if they want someone who is still using Sonnet 3.5 ... that's like punching your vibe code in on paper tape, these days.
eventually.. lol
load more comments
(1 replies)
Spot security vulnerabilities instantly from a candidate that can't actually write code.
The real trick about vibe coding is that it's like any other management skill - when your minions completely screw the pooch, you need to be able to step in and do it for them.
My managers are supposed to be skilled?
Supposed to be ≠ is be.
Just ask the ai to make no failures. Just aks the Ai to eliminate all failures. Easy 10 000 dollar per year.
I need to hire someone to take this functional 15 lines code, and like make it 200 lines of unusable madness.
But fast! Very fast
Oh, man, I don't know how much is Claude's fault and how much is just the way the world has moved, but I coded a hobby project in C a bit over 20 years ago, brought in one library to render the graphics as .jpg files and the whole thing was like 300 lines of code.
Claude "modernized" it for me, and yeah, it shows on a browser as a PWA and it's working correctly (this time, via Opus 4.6 - first time I tried with Sonnet 4.0 it couldn't even make it work correcty) - but daaaaammn, there's like 454 files in deps, 1.4GB in the rust target folder - maybe it's just a rust thing?
load more comments
(2 replies)
natural language is the new programming language
lol. Lmao.
Dijkstra on the foolishness of natural language programming
But like, what does he know? He wasn’t an AI-native vibe orchestrator.
Thx for sharing this . Really hope people read it.
All he made was some dinky algorithm. Google Bard could do that in three minutes flat smh.
And even this improvement wasn't universally appreciated: some people found error messages they couldn't ignore more annoying than wrong results, and, when judging the relative merits of programming languages, some still seem to equate "the ease of programming" with the ease of making undetected mistakes.
This guy was writing in the year x86 was first introduced, and I still feel like I see this attitude around.
(He manages to shoehorn in a "kids these days" paragraph too, though)
“English is the new programming language” would be more punchy
We did it to ourselves. Developing mission-critical systems in scripting languages and always sacrificing quality for delivery. Fast and sloppy paid þe bills, but we were digging our own graves. Once industry became used to sloppy software, a relatively mild shift to even more crappy, but far cheaper and more immediate software was a no-brainer. Customers haave gotten used to shitty, buggy software. It doesn't matter to þem who's writing it.
The only way for us to not "do this to ourselves" is to form unions. Otherwise we aren't driving the decisions on what is used and what's prioritized at all.
Safety critical (aerospace, medical, precious few other) industries have regulated quality, with moderate success. It's far from perfect, farther from ideal, but it is providing some additional resource and schedule allocation to do the things that need doing to ensure the systems don't screw up too badly, too often.
Am in automotive and there's definitely some of that. Much more so than in other industries I've worked. With that said, it's a losing battle against the value proposition of AI. We're getting AI use mandated on us.
I'm in one of those others I mentioned (and I try not to reference my company online because of... reasons), and we're getting strongly encouraged to "integrate AI in our daily workflows, where it makes sense" - not just coding, but coding is an obvious target. As a business we tend to change slowly, so this will be... interesting.
Sounds almost like we work for the same company. 😂 Perhaps they all lifted this statement from the same consultancy contractor.
load more comments
(1 replies)
Developing mission-critical systems in scripting languages
This is a wild take. If you'd come up in the 80s you'd be complaining about using C instead of hand-writing assembly.
load more comments
(2 replies)
SOTA
Me: I want SoaD!
Mom: we have SoaD at home
At home: SotA, featuring such hits as
Sorta poisonous
lo mein
Let someone else bring the bombs
10x the speed, sweet. So 10x the salary too right?
Vibe salary
Fucking idiots. I'm surrounded by idiots
im curious if they have live "vibe coding" session during hiring process
load more comments
(1 replies)
You know the "vibes" of different models - when to use
Would that be a vibe-rater?
So I ran into my first genAI coding junk yesterday when I was on a call with my boss and as a solution to a problem we were talking he said, "hold on let me ask Gemini."
I felt my soul die a little bit at that point.
But the fun part is that Gemini first didn't provide a good answer.
And then on the second go it also didn't provide a good answer.
And then on the third attempt we decided to table the issue for the moment because prompt coding on a call was taking longer than I think he expected.
I really disliked that experience.
Hmm, was the boss hoping to turn that into a "why do I even pay you" moment?
WTF?! 😳
Its serious and this is going to become more and more normal.
My entire workflow has become more and more Agile Sprint TDD (but with agents) as I improve.
Literally setting up agents to yell at each other genuinely improves their output. I have created and harnessed the power of a very toxic robot work environment. My "manager" agent swears and yells at my dev agent. My code review agent swears and tells the dev agent and calls their code garbage and shit.
And the crazy thing is its working, the optimal way to genuinely prompt engineer these stupid robots is by swearing at them.
Its weird but it overrides their "maybe the human is wrong/mistaken" stuff they'll fall back to if they run into an issue, and instead they'll go "no Im probably being fucking stupid" and keep trying.
I create "sprint" markdown files that the "tech lead" agent converts into technical requirements, then I review that, then the manager+dev+tester agents execute on it.
You do, truly, end up focusing more on higher level abstract orchestration now.
Opus 4.6 is genuinely pretty decent at programming now if you give it a good backbone to build off of.
- LSP MCPs so it gets code feedback
- debugger MCPs so it can set debug breakpoints and inspect call stacks
- explicit whitelisting of CLI stuff it can do to prevent it from chasing rabbits down holes with the CLI and getting lost
- Test driven development to keep it on the rails
- Leveraging a "manager" orchestrating overhead agent to avoid context pollution
- designated reviewer agent that has a shit list of known common problems the agents make
- benchmark project to get heat traces of problem areas on the code (if you care about performance)
This sort of stuff can carry you really far in terms of improving the agent's efficacy.
I am genuinely trying to keep up with things, but what I see is completely different from what you've been describing
-
My recent experience with launching a swarm (3-4 Claude opus agents) ended up with a fiasco: a simple task ate $15-20 Claude credits in less than ten minutes. Looks indeed like science fiction, but doesn't produce anything
-
In my current role as a team lead, I had to review a lot of code and I do what I haven't ever done: decline the whole PRs as they contain a lot of architectural changes that complexify the system in order to achieve the goal.
-
I write much less code with Claude code these days, mostly because I don't trust it and have to recheck every single scenario. I trust junior engineer in our team more than I trust this instrument.
load more comments
(2 replies)
nah such narratives are mostly pushed by Ai companies (it is obvious they need to sell it as business tool not personal buddy). Of course some managers/companies are buying into this narrative, and it is also understandable bc idea sounds like panacea especially if sell it further to investors :) and we see whole circle of snake oil sales
nah such narratives are mostly pushed by Ai companies
Someone's personal experience is an AI company narrative now?
it always was. look at people trying to automate everything with help of ai bots . and before ai companies started pushing this none of these folks spoke about it ot tried to reach same goal with iftt or other tools that are here for decades.
I don't think you understand the words you're using...
Someone said "this is how I managed to make this work," provided detailed explanations of it, and you're dismissing it as propaganda rather than testing it for yourself. That is an unbelievably stupid stance.
you are escalating it too fast taking it to personal level. I feel you are close to bring moms to this. So relax , let your ai buddy play with your parts. This chat is over.
load more comments
(1 replies)
load more comments
(2 replies)
Some people do stuff the ai is good for, simple tasks that have been done a lot online already.
I hate ai for coding, AI cannot work for me. I would never trust it to do anything
load more comments
(1 replies)
Opus 4.6 is genuinely pretty decent at programming now if you give it a good backbone to build off of.
Soup from a Stone.
load more comments
(1 replies)
load more comments
(18 replies)
Knowing how to code is now "syntax heavy"
god I hate this world
view more: next ›
this post was submitted on 10 Mar 2026
228 points (100.0% liked)
Programmer Humor
41779 readers
68 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 6 years ago
MODERATORS