Wth is "Fixing memory leaks using pointers"?
this post was submitted on 07 May 2025
1127 points (96.8% liked)
Programmer Humor
23127 readers
1508 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
Similar energy:
Honestly, CSS is a fucking joke and it's solely to blame for why centering something isn't always straightforward.
By the way, this picture is a crock of shit for people who aren't programmers. Anyone who is a programmer will not take it seriously because programming is so much more about helping others instead of shaming them.
Stackoverflow: exists solely from the urge of developers to help developers, and since ExpertsExchange was paid dogshit.
This meme: pisses on its whole purpose.
Nah, it's not that bad.
In 10 years with continued AI use? Yep.
I'm thankful for AI. It guarantees my job as developer will continue to exist to repair all future AI-damage.
I started with C++ and went to Java to .NET to Javascript and now to Terraform.
I know this is all a joke but there's something definitely different with the ones above and the ones below. There's a bit of satisfaction you can get sometimes when you're working with memory directly and getting faster feedback (yes, there's more math back then and it wasn't easy to look stuff up, for sure). However, there's new challenges nowadays ... there's so many layers on top of layers. I feel as though Stack Overflow and ChatGPT are so needed because the error messages and things we give are obfuscated or unclear (not always any library author's fault as there's compatibility issues, etc)
We're doing serverless stuff at my current company and none of our devs run code locally. They have to upload it using CDK or Serverless Framework to run on the cloud. We don't use SST so we can't set breakpoints but like that's a lot of crap inbetween just running your code already. Not even getting into the libraries and transpilers and stuff we use. I spent like a few weeks over Christmas to get our devs to run the code locally. Guess what? None of them use it because they're so use to uploading it. I was like, "you can put breakpoints in it! you can have nodemon and it instant reloads! nope, none of them care ... "
First learning is last learning.
Same reason we still do console.log("FUCK").
First learning is last learning.
I'll be the dumb one to ask: what do you mean? Is this that making a mistake that costs a lot is the best teacher, because you only have to mess it up once to learn it forever?
Pretty sure they mean people don't learn something again when they already learned it. Once you learn how to do something, willingness to learn it again but a different way dries up, and so you stick to bad habits as long as they 'work'
load more comments
(1 replies)
Okay but how do u center a div in 2025
Make your web page in GIMP, export to PNG, <img>.
Same way you did it in 2024 but it's easier because the springgirdles have been replaced with rotated manglebrackets.
It's not about the center, it's about the friends we made along the way.
If using plain CSS, usually it's enough to set width appropriately, and margin-left and margin-right to auto.
If using a Modern Frontend/CSS Framework, then may God have mercy on your poor soul.
(Seriously I just started a new project with TailwindCSS and I'm so confused. But not entirely desperate yet.)
So what is the point of these frameworks if they make it harder?
If you spend a lot of time on a single framework, you will transcend and become a sort of frontend diety, growing multiple extra limbs allowing you to type in CSS classes faster than any mere mortal
Until everyone moves over to the next thing and you start from 0 again. Web dev is a nightmare.
load more comments
(1 replies)
Generally I find many these frameworks will make some complicated things simple, but the cost is some things that were once simple are now complicated. They can be great if you just need the things they simplify - or in other words can stick to what they were intended for, but my favorite way of keeping things simple is to avoid using complicated and heavy frameworks.
load more comments
(1 replies)
load more comments
(8 replies)
2050: people still wondering how to center a div because html and CSS is a nightmare.
maybe the div is already where it's meant to be
Depends if you're centering the div or the things in the div. Which has probably been the main issue since CSS was invented.
load more comments
(8 replies)
My experience is that the programmers from the first row very much still exist. My theory is that the number of programmers from the first row stayed the about same or even increased slightly. There are so many more so called "programmers" overall now, however, that in relation the first row programmers are much rarer now. And to be fair, you don't need a programmer capable of programming entire games in assembly to center a div.
And vice versa, you don’t need to know how to centre a div to create a game in assembler. I’m comfortable using pointers and managing memory, but don’t ask me to do anything with web UI.
load more comments
(4 replies)
Love the shoutout to Margaret Hamilton
I can't remember some syntax unless I do it at least 100 times. I often look up stuff that I have already done before and know because of my goldfish memory.
I know someone that still uses ed for all their code editing.
I feel very confident in my understanding of random 8 bit CPUs and their support chips, but asking me to center a div is like this xkcd.
load more comments
(20 replies)
I once had a junior calling me in a panic because he didn't know how to quit nano. NANO!
Nano... Like... The one that has all the keybinds permanently shown at the bottom of the screen?
load more comments
(4 replies)
Huh? Isn't it like right there at the bottom of the screen?
I guess not knowing that ^X means Control+X could be the issue, but still...
TIL!
Can exit nano on my own, have the common sense to not call in a panic about it before at least looking it up. (Which is how I learned how to exit it: looking it up.) But was never taught about ^ meaning "Control+" until your comment, especially since nowadays people write it out as "Control+" or "CTRL+".
I might have put two and two together when dealing with everything else in nano after I learned to exit, but never really internalized the rule "^ means Control+". So thank you for your comment!
Disclaimer: I feel like I am too stupid for most of programming.dev but participate here anyways because I learn stuff from the comments.
Don't feel stupid. It's bad enough that all of IT is one giant impostor-syndrome support group. There's literally too much for any one person to know, and it's been that way for a very long time. Just give it your all, and memorize how to reliably search and look things up; take notes for the really important stuff. The rest will filter into your memory with practice.
Also: anyone that holds this kind of thing over your head is attempting to distract from how much they don't know. Most people in this industry understand and don't judge.
As for the ^ thing, I recall seeing that as far back as the 1990's. I want to say Microsoft actually popularized it, but it could easily be OS2 (IBM) or Apple. In hindsight, it's kind of wild to have a TUI (terminal user interface) hold your hand like this. Nano (and Pico) are kind of in a special category like that.
load more comments
(9 replies)
QA: "Yeah, Hi. Can you look at this defect ticket?"
Reading ticket details...
Me: "Let me guess. Is [whatshisname] responsible for this?"
QA: "Yeah."
Me: "Get him to fix it."
QA: "I tried. Like four times."
Me: Sigh "I'll take care of it."
QA: "Thank you!"
view more: next ›