Theo Jungeblut 4.54
Over the lifetime of a product, maintaining the product is actually one - if not the most - expensive area(s) of the overall product costs. Writing clean code can significantly lower these costs. However, writing clean code also makes you more efficient during the initial development time and results in more stable code.
Dependency Injection is a design pattern with the potential to write cleaner code. We will dive into the basics of Inversion of Control (IOC) and Dependency Injection (DI) to review different ways of achieving decoupling, using and exploring both: Best Practices, Design and Anti Patterns.
This presentation requires knowledge and understanding of basics like DRY, SoC, SRP, SOLID etc. which are building the base for decoupled architecture. However, we will start at the basics of DI and will work towards intermediate and advanced scenarios depending on the participating group.
This presentation is based on C# and Visual Studio 2010. However, the demonstrated patterns and practice can be applied to every other programming language too.
Get the basics first: Bay.NET San Francisco User Group, January 16th: Clean Code - Design Patterns & Best Practices
Introduction to the required basic principles and design patterns building the foundation for the Clean Code - Dependency Injection
Beginner/Intermediate (Dependency Injection / Design Patterns & Best Practices)