- cross-posted to:
- programmerhumor@lemmy.ml
- cross-posted to:
- programmerhumor@lemmy.ml
Wth is “Fixing memory leaks using pointers”?
Bottom right has always happened, just create bugs yourself and then fix them to keep your job
It’s easy, just use @media and padding to the left side of the div to put it in the centre for each screen size.
div { margin: auto; }
I once had a junior calling me in a panic because he didn’t know how to quit nano. NANO!
Do you remember the “press any key to exit”? Someone asked where is the “any” key.
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.
I had an intermediate not understand how to read a pipe-delimited text file.
Read as in, with their eyes? Or how to ingest it into some other app/script? Cos I’m vaguely aware that awk can be used in some way for this, but wouldn’t have a clue how.
awk is practically made for record processing, within the shell you can set
$IFS. The reason so many ancient UNIX file formats use:as separator is because that’s the default setting of$IFS.It’s all a huge PITA, though. I mean there’s a reason why people started using perl instead. Nushell is great for that kind of stuff, even more so if you have random json or such lying around it loads just as easily. “Everything is a string” was a mistake.
The former.
That deserves a “do you know how to read?”, because the exit command is on the lower part of the screen for nano
To be fair, they show up as “^X” or whatever, and typing [Shift]+[6] followed by the [X]-key doesn’t do the trick.
Nano… Like… The one that has all the keybinds permanently shown at the bottom of the screen?
Onscreen instructions unclear, pressed Shift+6+X. Still stuck in Nano.
Burnt into the old LCD screen.
And your retinas.
Yeah, that one…
Nano nano!
drinks water with finger
Ork humor. Love it.
I have never Googled “how to center div 2025” because the last time I had to center a div was in 2024. I’ve never asked ChatGPT to fix a syntax error because I use Copilot. Exiting Vim is basically the only thing I know how to do in Vim, but I can do it. And my bug fixin’ is generally one-for-one.
On the flip side, I can write some code without StackOverflow and AI. Writing a game in Assembly, these days, is for a specific kind of hobbyist or absolute fools. Languages using pointers are mostly for specific types of application and completely irrelevant for most programmers these days – and the overwhelming bulk of us are better for it. And writing code by hand is an incredible talent and skill, but again, essentially useless these days.
I’ve never asked ChatGPT to fix a syntax error because I use Copilot
If you are going to be this pedantic, I’ll have you know Copilot is a ChatGPT model in a Microsoft skin.
80s programmers hated Unix, btw. Look up Unix Haters Handbook, it’s a free and funny read
I prefer the MIT link, it’s faster 😁
A lot of it was fair criticism at the time. Linux fixed some of what was wrong. Having a good
sudoconfig 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.)
Good thing GNU’s not Unix
They also hated their local sysadmin. BOFH still holds up in a few key ways.
Thanks. I didn’t know there was a real band called “The Pipi Pickers” and I might have lived on happily without that knowledge.
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
Unix does so many stupid things and we’re still stuck with some of them. Especially the terminal section still applies today.
People have been hm unable to quit vim since before I was born.
deleted by creator
May the :helpgrep be ever on their side
I swore up & down that I’d learn at least two ways of exiting VIM. I even went through basic training to learn all the shortcuts, but it interfered with my regular workflow, so I dropped it “for a bit”. It’s been a year and I can’t remember a damn thing.
Yeah OK, but back then, an office suite was like 500 LOC.
I’m 2 from the top, 3 from the bottom.
my friend there are only 2 rows
I read that as he created a game in assembly, and can’t quit vim. Whether technically or sexually is up to OP to say. And what’s the game?
Oh no, I was never a programmer in the past.
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!”
I once had an intern attempt to install sudo using NPM and when that didn’t work he asked ChatGPT “Why can’t I install sudo from NPM?” while I’m trying to explain it to him.
He was smart, but somehow knew very little about commercial computers despite being on the verge of getting his master’s in computer science.
“Wait why can’t I install windows iso from vscode extension store?”
Similar energy:

deleted by creator
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.
CSS is amazing, if you know how to use it 😉
Everybody complaining about css like “but it doesn’t do what I want if to do without me investing a minute into why”.
Ironically, it’s oh so often the RTFM crowd.
Stackoverflow: exists solely from the urge of developers to help developers, and since ExpertsExchange was paid dogshit.
This meme: pisses on its whole purpose.
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.
I’ve never understood why people are so intimidated by tar
The
I almost never create a tarball, so I have to look up the syntax for that. Which is as simple as
man tar. But as far as extracting it almost couldn’t be easier,tar xf <tarball>and call it a day. Or if you want to list the contents without extracting,tar tf <tarball>. Unless you’re using an ancient version of tar, it will detect and handle whatever compression format you’re using without you having to remember if you needzorJor whatever.
I got tired of looking up the options for each possible combination of archiving + compression, so today I have a “magic” bash function that can extract almost any format.
Then for compressing, I only use
zip, which doesn’t need any args other than the archive name and the thing you’re compressing. It needs-rwhen recursing on dirs, but unlike “eXtract” and “Ze”, that’s a good mnemonic.tar -eXtract Ze Vucking File
Thanks! This will definitely help me to remember it from now on.
Me 6 months from now:
tar -EZVF
deleted by creator
Nobody wants to deliberately use the wrong compression type when extracting, so modern tar will figure out the compression itself if you just point it at a file. So
tar -xf filenameworks on almost anything. You don’t need to remember which flag to use on a.tar.bz2file and which one for a.tar.xzfile.That doesn’t give me a memorable mnemonic though.
tar -eXtract File
yeah, but then how am I supposed to remember “tar” ? :P
Tape ARchive -eXtract File
It is sticky and pretty much ruins clothes.
One reason is that tar supports both traditional style args “tar tf <filename.tar>” and unix-style args “tar -tf <filename.tar>” but there are subtle differences in how they work.
Literally the only time I’ve ever run into that is when I was trying to manipulate the path it extracted to. In 99% of cases I’m doing tf, xf, or cf plus flags for the compression type, etc, and those differences are irrelevant.
I used something recently where it wasn’t possible to use the traditional-style args. I think it was a “diff”, which meant I needed a “-f”. It wasn’t a big deal, but, occasionally it does happen.
I’m not saying it doesn’t happen. This thread started because I said I’ve never understood why people talk like tar is some indecipherable black magic. Common tasks are easy and there’s a man page for everything else.
tar --help
(joke)
YOU FOOL! THE ACTUAL COMMAND WAStar -?That dash looks an awful lot like an em-dash
Normal:
-Em:
–






















