- Life is too short to waste time planning how to code well. Just write code; the best you can. (And learn how to improve it.)
- Life is too short to waste time writing tests before any single stupid method.
- Life is too short for not testing any relevant code you may have.
- Life is too short for mocking the HTTP context in order to test controllers–use worker services and don’t test controllers.
- Life is too short to make sense of Objective C. Go with MonoTouch for any iOS development.
- Life is too short to convince people that Responsive Web Design alone is useful only in simple portals and demos.
- Life is too short to learn how to write good JavaScript code.
- Life is too short to code HTML5 via Modernizr: make a choice!
- Life is too short: give us another Windows!
- Life is too short to write asynchronous code in C#.
- Life is too short for not using async in C# (cit. Ross Dargan)
- Life is too short to wait on a background thread.
- Life is too short to deal with Apple or wait for Windows Phone: just pick up Android and use IntelliJ!
- Life is too short to explain why an anemic domain model (EF-like) is poor: just don’t use it.
- Life is too short to parse user agent strings yourself.
Two cents of software value 
Think 10 needs to go now with the async keyword! Life is too short not to use it 🙂
Hey Ross,
with async is better but I’m an old-fashioned guy and regret the old good times of plain sync code 😀
Nice list. Sensible. I especially like the pragmatic instead of dogmatic approach to unit testing. Laughed at #5. Cried at #13 (Windows Phone) – though deep down I know you’re right! As for #14 – no idea what it means, but looks like a good topic for more reading.
#5 – Objective C – I remember that at University, it was more painful than having my wisdom teeth taken out… That syntax is rather bizarre and more suited to a class creator meta-tool than an actual programming language.