Good Fucking Programming Advice

TDD is no replacement for putting your fucking brain to work.

This page was inspired by Good Fucking Design Advice. Hat’s off, guys.

Check out Good Fucking Programming Advice on Twitter or Facebook, too.

You can do without TDD. You can go faster without TDD. You’re a fucking genius. I can use any help I can get to write better software.

It’s easy to write crappy code in every fucking language.

Learn about a software development methodology by fucking following it instead of waxing about it.

Don’t return from the fucking middle of nowhere. Use one exit for your methods. Everything else will set you up for disaster later.

How do you expect to do design if you don’t sweat the fucking basics like class/method/variable naming or decompositon of methods?

You can always take smaller steps, you just have to fucking do it instead of messing around.

If you’re a software developer and don’t have at least one side project you’re fucking dead in the water.

You learn by following the rules first, then bending them, not the other way round.