Wth is "Fixing memory leaks using pointers"?
Similar energy:
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.
Okay but how do u center a div in 2025
Make your web page in GIMP, export to PNG, <img>
.
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.
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.
Same way you did it in 2024 but it's easier because the springgirdles have been replaced with rotated manglebrackets.
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 ... "
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.
I'm guessing that someone who figured out how to keep a high score box centered on screen using assembly will figure it out to do it with CSS.
The reverse, not so much...
This can be generalized to say that programming has become such a diverse profession that you will find experts in one area that know very little about others. There's simply too many things that are programmed in too many ways for anyone to know it all anymore. Hell, that was the case in the 70's and 80's too.
Love the shoutout to Margaret Hamilton
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.
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?
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.
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!"
Can't exit Vim
Ah yes, the legendary filter
the only reason people use vim is because they are stuck in there
80s programmers hated Unix, btw. Look up Unix Haters Handbook, it's a free and funny read
A lot of it was fair criticism at the time. Linux fixed some of what was wrong. Having a good sudo
config mostly resolves the problem of having one superuser account, and big, multiuser systems are a lot less common now, anyway. X's network transparency features aren't that useful in modern computing contexts, either, though I have found a few over the years.
But mostly, it's because the landscape changed from a hundred Unix vendors vs a bunch of other OSen, to now where it's Windows vs Linux vs OSX. By that comparison, the two with Unix-derived history look well thought out.
(This also implies that NextStep was the one old Unix vendor that has survived in a meaningful way. I don't think anyone would have guessed that 30 years ago.)
Unix Haters Handbook
https://en.wikipedia.org/wiki/The_UNIX-HATERS_Handbook
Didn't knew this. It has 360 pages, wow!
EDIT:
The Macintosh on which I type this has 64MB: Unix was not designed for the Mac. What kind of challenge is there when you have that much RAM?
hehe
Hey now. Searching stack overflow circia 2011 to 2018 was an Art. You had to know enough to find the correct question that wasn't deleted because a mod thought it was a duplicate of another question
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