I think my least favorite part of Lemmy is all the posted screenshots of tweets. It just took me 3 tries to get to these comments.
What benefit do tweet screenshots serve?
this post was submitted on 11 Mar 2026
830 points (99.3% liked)
Programmer Humor
30341 readers
2051 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
I know what context they are looking at and I don't need to make a twitter account to view the relevant replies.
Come see why you're all wrong sore losers, here in a lenghty rantarticle I explain why AI is so good and is going to replace you all:
I love the https and port 80 combo. Really sells the incompetence.
That’s what makes it obvious that this person has been around the block. Or a few blocks.
Should have been brought round back.
pointing to 80 port was the salt in the wound, i presume?
With https no less
Hey thats my website! Gemini, call the police!
You rang? (My user's name in my laptop is gemini, and in my home pc, and anywhere i use my flake really), btw check out my terminal cool right?:
It doesnt look right in the tty though, i havent bothered to make it change the characters for some it can print, i use oh-my-posh btw, and fish.
So did you call the police yet?
Every breath you take starts playing on the background...
That page is filthy. You should be ashamed of yourself.
Goddammit, I clicked.
Theres too many s's in https
People who share the size of a codechange as a mark of how effective ai coding agents are truly missing the point of code changes.
Big Diff Energy
Number of lines of code written is a shitty metric to measure productivity.
In college, on the first day of orientation, someone in my class bragged that they wrote 50,000 lines of code for a game that was similar to tic tac toe, emphasizing that he "wrote a lot of code". A TA told him that it wasn't a sign that his program was decent and that it really didn't seem like it should take 50k lines of code to make something as simple as his game.
He dropped out after the first week of intro to programming.
That's nothing, I wrote the code to return if the input is even or not in 1M lines of code.
And yet I experience it so often. That or “effort points” as the metric being used to determine who all stars are.
Either as a metric just encourages gaming of the system:
- Why write one line when I can write the same thing in 20?
- Why take this one effort point task I think will take three when I can just skip it and grab these one effort points I think will take 20 minutes?
I’ve been on teams that on the surface didn’t have these metrics matter, but the top effort points achiever got bonuses on the DL.
What did you do?? You refacted the code and now it's better organized but you overall got rid of lines?
I'll set up a PMD meeting to help you out of this problem, but fair to say don't expect a raise or a bonus this year.
load more comments
(10 replies)
I'm just a hobbyist, but I'm always more proud of commits that remove stuff.
Removing shit and it still working perfectly the same is absolutely a goal everyone should have. Less code means less to maintain.
And being more performant, the perfect trio
load more comments
(1 replies)
i refactored some web code i wrote ten years ago and it's more elegant and a tenth the size with new features because of language advancements. feels great.
You reminded me of a story I recently read, where the author highlighted just how much awesome programming someone had done by describing how their hands were cramping up.
It's like estimating how well an artist paints by looking at how much paint is on their clothes, or judging how good a cook is by how many cuts and burns they have. The actions that cause those things are incidental to the process, not central, and an excessive amount points to incompetence, not hard and skillful work.
Didn’t you hear? We’re going back to KLOC for measurement of productivity.
load more comments
(1 replies)
People who've never reviewed a PR be like. Wow green number big, is good.
load more comments
(5 replies)
vibes = vibes-3
if (outage) {
fix()
}
Coding is so easy
They just forgot to include "no bugs" in the prompt.
I would love to know if this actually makes a difference though haha. I believe it might make a slight one as it could try to rethink about it depending on the model
I usually just ask it to recheck line by line for bugs with a thinking model and that’s pretty good at solving potential bugs, but they still need to be reviewed obviously. I only use open weight models though so they might be a bit inferior
Slop points aside, I found 5.4 to be pretty ass compared to 5.3 codex. Took way longer and wasted more tokens.
load more comments
(1 replies)
that's good, mandatory meetings always (ALWAYS) solve the problem! /s
You know what's funny?
I use AI to develop software. However when I'm looking for libraries to do things if I see a CLAUDE.md file I have to look and see when it was added and hold it against the library if it's early in the history.
It's like prewar steel.
I also recognize it's hypocritical.
meow
I love this sabotage. Has this worked against anyone that you know of yet?
load more comments
(1 replies)
load more comments
(2 replies)
Positive diff? Pfft, amateurs. If I ever see even a 1000 line PR I'm instantly rejecting and closing it. Learn to code, not generate bullshit.
If you write tests and add features you can easily go up to 1000, don’t know what you're talking about
load more comments
(1 replies)
I'm pretty sure the shitty Windows upgrades as of late has been vibecoded as well.
load more comments
(1 replies)
Live by the vibes, die by the vibes.
I like that this is lowkey a Polymarket Advertisement too. The internet truly is a wonderous place.
hhnhnhn polymarket
What could go wrong?
view more: next ›