The "shut up and get back to work" coding style guide

So you’re starting a new website, and you open the first CSS file. What style do
you use? Well, you hate indenting with spaces passionately. You know tabs are
right because they’re literally made for this, and they’re only one byte, and
these god damn spaces people with their bloody spacebars…

Shut up and use spaces. That’s how CSS is written1. And you, mister web
programmer, coming out of your shell and dipping your toes into the world of
Real Programming, writing your first Golang program: use tabs, jerk. There’s
only one principle that matters in coding style: don’t rock the boat. Just do
whatever the most common thing is in the language you’re working in. Write your
commit messages the same way as everyone else, too. Then shut up and get back to
work. This hill isn’t worth dying on.

If you’re working on someone else’s project, this goes double. Don’t get snippy
about their coding style. Just follow their style guide, and if there isn’t one,
just make your code look like the code around it. It’s none of your goddamn
business how they choose to style their code.

Shut up and get back to work.

Ranting aside, seriously - which style guide you use doesn’t matter nearly as
much as using one. Just pick the one which is most popular or which is already
in use by your peers and roll with it.

There’s a lot of stupid crap which ends up in style guides, but this is by far
the worst. Look at all that wasted whitespace! There’s no room to write your
parameters on the right, and you end up with 3 lines where you could have two.
And you have to mix spaces and tabs! God dammit! This is how you should do it:

Note the extra indent to distinguish the parameters from the body and the
missing garish hellscape of whitespace. If you do this in your codebase, I’m not
going to argue with you about it, but I am going to have to talk to my therapist
about it.

For the record, tabs are objectively better. Does that mean I’m going to write my JavaScript with tabs? Hell no! ↩

Articles from blogs I follow around the net

This post gives an overview of the recent updates to the Writing an OS in Rust blog and the used libraries and tools.
I was very busy with finishing my master's thesis, so I didn't have any to implement any notable changes myself. Thanks to contrib…

This is an archive of a series of comp.arch USENET posts by John Mashey in the early to mid 90s, on the defnition of reduced instruction set computer (RISC). Contrary to popular belief, RISC isn't about the number of instructions! This is archived her…