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.
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
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...
But you dont what the code of the assembly-style centered div in your codebase. Because nobody will be able to read it and understand what it even does. There are abstraction specific ways to solve problems and the right way to do something in assembly is not the right way to do it in CSS.
Agreed, in my limited experience with both CSS is like the conceptual opposite of assembly. When I do web design I tell it what I want to look like but can't see how it's getting there because that's done for me. Assembly is the lowest level of abstraction we've got and it took me ages to write a little program for class that returns an argument in it (Jasmin VM) and then get GCC to compile it.
I would say that CSS is like doing an incantation that magically makes the site look good if you do it right, and assembly is like building something by hand.
Can't exit Vim
Ah yes, the legendary filter
I first tried vi in the early 90s, before I had easy access to online resources. I had to open a new shell and kill the vi process to exit it. Next time I dialed into my usual BBS I asked how to exit that thing. But since then I've liked it, because vi has been on every system I ever ssh'ed into.
You quit it just like you quit ed
or ex
, just that you have to enter the prompt (:
) yourself as vi
is not by default in prompt mode. And you should know ed
, ed
is the standard editor.
I use Helix btw.
I can exit Vim, it just feels like trying to rip out the dashboard and the interiors from a family car because race cars also lack them. Kate is a good speedy alternative to VSCode, not to mention it also does not have Microsoft's greedy hands on it.
I don't get your analogy, but (neo)vim is a full featured IDE if you configure it to be one
Out of the box, Vim's default configuration is very basic as it's trying to emulate vi as close as possible. It like if you want things like headlights or a heater or a tachometer in your family car, you got to create a vimrc and turn those features on. That was my experience when I first started using Vim - I spent a lot of time messing around creating a vimrc until I got things the way I wanted.
One of the big changes with Neovim is their default settings are a lot more like what you would expect in a modern text editor.
Yeah that's a fair way to look at it
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 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?
Onscreen instructions unclear, pressed Shift+6+X. Still stuck in Nano.
Do you remember the "press any key to exit"? Someone asked where is the "any" key.
80s programmers hated Unix, btw. Look up Unix Haters Handbook, it's a free and funny read
Good thing GNU's not Unix
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
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.