Test Driven Development is a tried and proven method of software development that helps you validate your work as you code. Previously I’ve talked about the benefits of TDD, and why it is successful. I could continue with an Intro to TDD, but I’ve found other sources that do a great job already of explaining the process. Instead, today I’d like to focus on best practices which lend themselves well to TDD, and if you aren’t following them already, they could make you a better programmer!

Test-Driven Development (TDD) has been around a while; you may have heard of it. If you’re new to the idea, I’m going to try to sell you on it. If you’re familiar with it, I’m going to make the argument that it’s the best way to approach new projects. And if you know it and hate it, I’m going to try and change your mind, if you give me the chance.

In the modern age, software solutions can span across many platforms. One monster solution alone could contain a range of web projects, web services, desktop applications and mobile applications. If you’ve ever written a class library for .Net Framework and later had to target Mono to use it with iOS, you might want to save yourself from the trouble in the future. You might also be one of the lucky few who have worked with PCLs (Portable Class Libraries) and had the pleasure of dealing with those cumbersome PCL profiles. Well no more! PCL is dead, and long live the new King: .Net Standard!