Ivan Dominis

.NET developer

[Ivan Dominis @idominis7]

@MayeMuskchat816 Most beautiful feeling in the world

[Ivan Dominis @idominis7]

@dani_ptt @CapitanBitcoin Ajde ne pizdi

[Ivan Dominis @idominis7]

@Simi_2210_ 179

[Ivan Dominis @idominis7]

@TommiPedruzzi @NavalismHQ Claude

[Stefan Đokić | .NET @TheCodeMan__]

Most developers use Dependency Injection.

Very few understand what the DI container is actually doing.

To many people, it feels like magic.
You register a few services:

builder. Services.AddScoped<IOrderService, OrderService>();
builder. Services.AddScoped<IOrderRepository, OrderRepository>();

Then suddenly this works:

public class OrdersController(IOrderService service)

No new keyword.
No wiring dependencies.

And the application runs.

So what’s actually happening?
When ASP. NET Core starts, the DI container builds a service registry.

A map that says:
IOrderService → OrderService
IOrderRepository → OrderRepository

Later, when the framework needs to create your controller, it asks the container:
“How do I build this object?”

The container looks at the constructor:
OrdersController(IOrderService service)

It sees that IOrderService is required.
So it resolves it.

But to build OrderService, it might need something else:
OrderService(IOrderRepository repo)

So the container resolves that too.

And maybe the repository needs a database context.
So the container resolves that as well.

What you end up with is something called an object graph:
Controller
↓
Service
↓
Repository
↓
DbContext

You requested one object.
The container constructed the entire dependency tree.

That’s the real job of the DI container.
Not “injecting services”.

But building object graphs safely and consistently.

Which is why DI becomes powerful when your system grows.

Because instead of every class creating its own dependencies…
The container becomes the single place responsible for object creation.

And that gives you:
• cleaner architecture
• predictable lifetimes
• easier testing
• fewer hidden dependencies

The moment this clicks, DI stops feeling like magic.
It starts feeling like infrastructure.

Curious:
What part of Dependency Injection confused you the most at first?
__

📌 Don't miss the next newsletter issue, 20,000 engineers will read it, join them: https://t.co/gI46R2Kc0c
📌 Join our Free Closed .NET Hub (1.2k members) and get access to content nobody publicly has: https://t.co/IPQwbeQ8pG

♻️ Repost to others.
📂 You can save this post for later, and you should do it.

➕ Follow me to learn #Dotnet and Architecture every day.

[Stefan Đokić | .NET @TheCodeMan__]

𝟭𝟬 years in .NET.
If I had to start again today, from zero, this is exactly what I would do.

𝟭. I would master debugging before mastering design patterns.
𝟮. I would learn how HTTP actually works.
𝟯. I would deeply understand async/await.
𝟰. I would learn how memory works in .NET (GC, allocations).
𝟱. I would build one ugly but working CRUD app.
𝟲. I would deploy something in the first 30 days.
𝟳. I would learn Git properly (rebase, squash, cherry-pick).
𝟴. I would read existing production code daily.
𝟵. I would study logging and observability early.
𝟭𝟬. I would learn how to write meaningful commit messages.
𝟭𝟭. I would focus on architecture after building real apps - not before.
𝟭𝟮. I would learn SQL seriously, not just EF Core.
𝟭𝟯. I would understand transactions and isolation levels.
𝟭𝟰. I would practice writing tests that actually fail.
𝟭𝟱. I would learn to read stack traces fluently.
𝟭𝟲. I would learn Docker basics in year one.
𝟭𝟳. I would understand dependency injection internally, not just use it.
𝟭𝟴. I would measure performance before optimizing anything.
𝟭𝟵. I would avoid microservices until I truly need them.
𝟮𝟬. I would build at least one API from scratch without templates.
𝟮𝟭. I would learn how authentication and authorization really work.
𝟮𝟮. I would understand what happens when production crashes.
𝟮𝟯. I would study real post-mortems of outages.
𝟮𝟰. I would learn how to review code properly.
𝟮𝟱. I would keep pull requests small.
𝟮𝟲. I would learn to communicate technical trade-offs clearly.
𝟮𝟳. I would avoid copying architectures from YouTube.
𝟮𝟴. I would understand threading before touching parallelism.
𝟮𝟵. I would learn to read documentation, not just tutorials.
𝟯𝟬. I would build side projects that solve real problems.
𝟯𝟭. I would learn CI/CD in year one.
𝟯𝟮. I would understand how APIs fail and design for failure.
𝟯𝟯. I would study security basics early (OWASP, input validation).
𝟯𝟰. I would seek feedback aggressively.
𝟯𝟱. I would focus on clarity over cleverness.

After 10 years, I don’t believe in “learn everything.”
I believe in mastering fundamentals deeply.

Frameworks change.
Principles don’t.
—

Join 19,000+ engineers in the .NET Newsletter. You will learn .NET and Architecture every week directly from your email: https://t.co/gI46R2Kc0c

If you're starting today, focus on depth, not hype.

♻️ Repost if this helps someone.
➕ Follow for pragmatic #dotnet insights.

[Ivan Dominis @idominis7]

@iam_smx Elon is a fuckin' legend

[Ivan Dominis @idominis7]

@karma44921039 https://t.co/zjPZ8H9Ezt

[Ivan Dominis @idominis7]

@karma44921039 Hulda Regehr Clark | Grokipedia

[Ivan Dominis @idominis7]

@alex_prompter Guide

[Ivan Dominis @idominis7]

Check out this Linktree! - https://t.co/vKY0fqDFxJ

[Ivan Dominis @idominis7]

@rryssf Agent

[Ivan Dominis @idominis7]

@clownworld Take Bill Gates with you...

[Ivan Dominis @idominis7]

@wakeupusa He forgot to lube strap-on on his wife...

[Ivan Dominis @idominis7]

@TrumpsHurricane Reverse

[Ivan Dominis @idominis7]

@WakeUpPatriott Mengele

[Ivan Dominis @idominis7]

@DOGEQEEN Adafjyvyvmsdfaspcsd

[Ivan Dominis @idominis7]

@FightWithMemes 🖕 is this racist?

[Ivan Dominis @idominis7]

@atensnut Y=4 &amp; Y=-5

[Ivan Dominis @idominis7]

@brawil86 ... Run !