Dagger 2, 2 Years Later

Dagger 2: Lessons Learned & Avoiding Team Frustration

Discover the pitfalls of implementing Dagger 2 and how to prevent developer frustration. This session dives into a real-world experience with Dagger 2, exploring initial benefits like improved testing with mock mode and enhanced white-labeling support.

However, the team encountered growing challenges and a reluctance to work with the Dagger 2 code. Matt Dupree will share the reasons behind this shift and offer valuable insights into how similar issues can be proactively avoided in your own projects.

Learn from our mistakes and gain practical strategies for a smoother dependency injection experience. We'll discuss:

• Common Dagger 2 challenges: Uncover the hidden complexities that can impact developer productivity.
• Testing with Dagger 2: Explore the limitations and potential frustrations of using mocking in a Dagger environment.
• Maintainability & Code Complexity: Understand how Dagger 2 can contribute to increased code complexity and maintenance burdens.
• Alternative Dependency Injection Approaches: Consider potential solutions and frameworks that might offer a better developer experience.
• Team Collaboration & Developer Experience: Focus on building a positive and productive development environment when using complex frameworks.

This session is perfect for developers, architects, and team leads looking to optimize their dependency injection strategies and avoid common pitfalls when using Dagger 2 or similar frameworks. Gain actionable insights to improve your team's efficiency and reduce development friction.