Good Fucking Programming Advice

You make shitty software, and you fucking know it. Make sure it will be less shitty today (inspired by @davewiner – http://bit.ly/alijF0)

Avoid those fucking abbreviations when choosing names for your methods. Vowels are a dime a dozen.

Use the fucking compiler to get feedback. You need all the help you can get.

Avoid those fucking comments. They get stale anyway.

Start working on code katas instead of gaming on your fucking PS3 to improve your lacking skills – http://osherove.com/tdd-kata-1/

Don’t use fucking abbreviations for your method or variable names. Keystrokes are a dime a dozen. Vowels, too.

If you can’t get your fucking test to pass, maybe you are fucking around with the wrong test? #tdd (Inspired by http://bit.ly/bOv2kC)

If you’ve never done it, start to write a fucking compiler. The basics are way easier than you think. Start here – http://bit.ly/adqQeu

More often than not, it’s your fucking fault, not your compiler’s.

It’s not the programming language which is determining the crappiness of your code, it’s your apparent lack of skills.