Wth is "Fixing memory leaks using pointers"?
Programmer Humor
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
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.
Stackoverflow is for senior devs to clown on junior devs. It's the inverse of helping juniors.
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'
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 still want to get into coding the OG manual way (because I enjoy pain and disappointment apparently) but now it seems like a waste of time since vibe coders and 13 year olds already are lightyears ahead of me. Also I have no reason to learn it, all apps are already built xD
all apps are already built
Couldn't be further from the truth. You also have to consider competition.
I'm in the same boat. I used to be an amateur front and back end web developer. Almost made a text based RPG in middle school. I had to stop when shit got crazy in high school and college, but I don't feel like any programming is worth my time right now. I'm focusing on gardening and maybe some cooking. You know, human activities that we can still enjoy.