Remember your first time wrestling with Dependency Injection (DI) or Inversion Of Control (IoC)?

by May 6, 2024

Remember your first time wrestling with Dependency Injection (DI) or Inversion Of Control (IoC)?

I do. And it was like trying to decode a foreign language.

When Castle Windsor and other similar projects were starting to take the limelight, I won’t deny it – I was utterly lost.

The buzz was loud, but the ‘why’ was a faint whisper, barely audible.

My static helper classes were my safety blanket, protecting me from the uncertainty of the unfamiliar.

I was unknowingly burying the initialization of my dependencies deep into the labyrinth of my code.

Writing tests? A nightmare when you don’t have control over your dependencies.

Today, DI and IoC are as familiar to me as the back of my hand.

Yet, I won’t ever forget the steep learning curve. That first taste of confusion. The struggle of wrapping my head around a complex idea.

Why? Because it makes me appreciate the journey of others.

So, remember – everyone is dealing with their own version of DI and IoC. Let’s be patient, supportive, and remember where we started.

Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Backlog: The Black Hole of ideas

Backlog: The Black Hole of ideas Is your backlog turning into an ever-expanding universe of forgotten dreams? We all know that mix—a jumble of big ideas and tiny tasks waiting for their day in the sun. Some items linger for years. Why do backlogs grow? Because we...

read more

The Trade-off Between Budgets and Quality ⚖️

The Trade-off Between Budgets and Quality ⚖️ In my previous post, I talked about shifting from Estimates to Budgets for feature development 💡. Let's dive deeper. Using a Budget instead of an Estimate introduces a trade-off: Scope and Quality adjust to fit the time...

read more

Budgets instead of Estimates

Budgets instead of Estimates Estimating a feature is difficult and is often a guess (or even a lie). An Estimate is for a fixed scope. So, you need to think deeply how to implement the feature, before giving an Estimate. The business can then use the Estimate to...

read more