An international speaker, Microsoft MVP, MCSD, CSM, and CSP, and a passionate member of the developer community, Phil Japikse has been working with .Net since the first betas, developing software for over 20 years, and heavily involved in the agile community since 2005. Phil works as the Patterns and Practices Evangelist for Telerik (www.telerik.com), and serves as the Lead Director for the Cincinnati .Net User's Group and the Cincinnati Software Architect Group Phil is also the founder and president of Agile Conferences, Inc., a non-profit dedicated to advancing agile in all aspects of software development. In his spare time, Phil works part-time as a Firefighter/Paramedic, serves as Cub Master for his sons' Cub Scout Pack, and volunteers for the National Ski Patrol. You can follow Phil on twitter via www.twitter.com/skimedic and read his blog at www.skimedic.com/blog.
Long a staple of the Agile community, unit testing is becoming more and more popular. While there is a lot of content on how to unit, the question of why unit test isn't always addressed. There are very real, tangible benefits from unit testing - it's more than just "writing more code".
Even though Unit Testing is becoming much more popular with developers, I still hear from people asking what Unit Testing means. In this article, we start at the top and cover the fundamental building blocks of Unit Testing.
Over the past few years there has been an evolutionary shift in the world of software development. In this article we will discuss software engineering, how it has changed to keep up with the world of weekly software updates, and what the future holds for software engineers.
