Silicon Valley Code Camp : October 5th and 6th 2013
Jeremy Clark makes developers better. By drawing on over 15 years of experience in application development, he helps developers take a step up in their skillset with a focus on making complex topics approachable regardless of skill level. He is a Microsoft MVP for Visual C#, and he has authored seven courses for Pluralsight, including "C# Interfaces", a course aimed at giving developers a clear understanding of abstraction. Jeremy lives in Southern California with 2 cats and a banjo. For more information, visit www.jeremybytes.com.
There's no such thing as a write-once application. The world is constantly changing, and our code needs to change with it. We'll think in small pieces and take a look at some principles and techniques that will keep our code manageable and understandable. Think about the developer who will come after you. Now, imagine that he's a homicidal maniac who knows where you live. Examples will be in C#, but the principles apply to pretty much every programming language.
What is Dependency Injection? The answers to the question seem to cause more confusion than help. We'll take a look at what Dependency Injection (DI) is, when we should use it, and what design patterns we can use to help us implement it. Benefits range from extensibility to late binding to testability. We can implement DI with or without a container (such as Unity, Ninject, or StructureMap), but we'll see how a container can do a lot of the work for us.