Of 'Commit logs from last night' and GitHub shenanigans

A case for the 'GitHub will get you hired' brigade.

So there you are, at your most devastating hour as a programmer. You're writing code, most of it probably spaghetti code. You're struggling. You probably don't know the concept of what you're doing. You become so paranoid, you want to smash your computer screen using your fist or maybe hurl the machine outside a window. The element of being ballistic! Heh?!

So what goes when all decides to work? You opt for profane version control practices in the name of version control. Being the bedraggled hacker that you are, you compose this commit message that speaks levels about your frustration in the build-up to getting things right in the software you were building. Below is a day in the life of paranoid dev who just got 'stuff working'.

git commit -a -m "Made shit work"

git commit -a -m "Added a bunch of semi colons that were missing for some balls weird reason."

My two cents on the element of obscenity would be: while it maybe 'normal' to use a little obscene language, there's nothing cool or enlightening about it. Any site built around it is at best noisy, but more like puking all over the screen. Additionally, it's baffling by this admiration of commit messages that do nothing to explain the code committed.

Ideally:Real hackers pivot two hours before their demo.