John Sonmez

John Sonmez (in on twitter) is a Pluralsight author of over 25 courses spanning a wide range of topics from mobile development to IoC containers. He is a frequent guest on podcasts such as DotNetRocks and Hanselminutes. John has created applications for iOS, Android and Windows Phone 7 using native tools, HTML5, and just about every cross platform solution available today. He has a passion for Agile development and is engaged in a personal crusade to make the complex simple. You can find him online on twitter @jsonmez and furthering his cause of demystifying the mysterious at http://simpleprogrammer.com.

John has 2 sessions at Warm Crocodile

Introduction to MonoTouch, Level: E
Are you interested in creating cross platform apps for iOS, Android and Window Phones? Don't want to learn Java, Objective-C and a whole new set of libraries? Perhaps you are just curious what these Mono tools are and why everyone is raving about them? In this session John Sonmez will show you the basics of the Mono tools for mobile development. We'll take a brief look at each one of these technologies and learn how each technology can be used to help you develop cross platform mobile applications. We won't be able to go into depth in any of these subjects, but by the end of this session you should have a good idea of what each of these technologies is and the basics for getting started using them.

 

Unit Testing Inferno: The 4 Levels of Unit Testing Hell, Level: C
Ever wonder why unit testing is sometimes so hard and other times it seems really easy? Ever wonder why unit testing seems so clean in code Katas, but so difficult in the real world? In this session John Sonmez addresses these questions and more as he shows you what he has labeled the 4 levels of unit testing. We will discuss what exactly makes unit testing difficult and how to make it much easier by applying a few patterns that help make difficult (level 4) unit tests become easier level 1 and level 2 unit tests. You should walk away from this session with a good understanding of what makes it hard to unit test a piece of code and some way that you can make it easier.