13 Programming-Related Superstitions That Every Developer Should Know
You Should Be Doing These
The number 13
Avoid the number 13 in your code. In a class put a line break at the 13th line.
The padding needs to be 13 (thanks, designers!). Make it 14 in your code and if it’s noticed do a 14–1.
Never ever: Release on Friday 13th.
What type of monster prepares a release for a Friday in any case?
Use your own keyboard
Coding at the shared working space (you call it that, although it is a branch of Starbucks) you want people to know you’re an ace coder.
You’d think your gaming laptop would show that to the wider world, wouldn’t you? However, there is an even better way.
Nothing says serious coder like a Dvorak keyboard. Sure there isn’t room for the Alienware laptop, keyboard, and coffee on the round Starbucks table so you need to hold the hot coffee between your legs. A few burns? A small price to pay.
Never ever: Let anyone think you’re not the best coder in the room.
I AM the best coder in the room. With the RGB lights to prove it
