NASA pilot Victor Glover CLAPS back after being asked what it means to be the first black man to visit the moon: “It’s the story of humanity, not black history, not women’s history, but that it becomes human history.”
“I also HOPE we are pushing the other direction that one day we don’t have to talk about these first. That one day, this is just—and listen to this—that this is the human history.”
it's very good news for Windows power users that Scott is involved in the Windows 11 improvement effort. Microsoft is planning to ship these improvements every month throughout 2026
This is the same man who came to Chelsea three years ago with a 100-page PDF and a PowerPoint presentation outlining his style and plans for the club, but was rejected in favor of Poch.
Clearlake is a big disaster.
Some developers think Tasks create threads.
They don’t.
In .NET, work is executed by the ThreadPool, a shared pool of worker threads reused across the entire application.
Here’s the mental model that helps explain it.
When a request arrives in your https://t.co/TYRozGX8dY Core app:
1️⃣ The work is placed into a task queue
2️⃣ A ThreadPool worker thread picks up the task
3️⃣ The thread executes the work
4️⃣ When the task finishes, the thread returns to the pool
Then it immediately picks up another task.
Threads are reused constantly.
That’s what makes the ThreadPool efficient.
But here’s where things go wrong.
If your code does blocking work, those threads can’t return to the pool.
Examples:
• .Result
• .Wait()
• synchronous database calls
• blocking HTTP calls
Now the thread stays stuck.
Under load, this creates a chain reaction:
Requests arrive
↓
Tasks enter the queue
↓
Threads are blocked
↓
The queue grows
↓
Latency spikes
This is called ThreadPool starvation.
Your server isn’t slow because .NET is slow.
It’s slow because all worker threads are busy waiting.
The key takeaway:
Tasks are not threads.
Threads execute tasks.
And when they’re done, they go back to the ThreadPool to execute the next one.
Unless you block them.
Curious: What’s the most common ThreadPool killer you’ve seen in production?
__
📌 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.