Stefan Đokić | .NET

This reality hits: deadlines, new team members, rushed PRs, “we’ll fix it later.” Most #dotnet projects don’t fall apart because of bad developers. They fall apart because nobody decided how things should look when things get messy. At the beginning: ✔ clean structure ✔ good intentions ✔ “we’ll keep it tidy” Then reality hits: • deadlines • new team members • rushed PRs • “we’ll fix it later” And suddenly the codebase starts fighting back. This carousel shows the full curriculum of Pragmatic .NET Code Rules. Not as a syllabus. But as a system. A system that: - removes pointless decisions - enforces consistency automatically - keeps projects clean even when teams grow I made this course for developers who: • are tired of style debates • want predictable projects • care about long-term sanity, not quick wins Already 50+ developers joined during pre-order. And yes, you get access immediately. And yes, you get access to the community. You don’t wait. You apply. You improve your project while the course grows. 40% OFF Preorder price: $59.89 (Only 4 spots left at the price and only today) Original price is $150. 👉 Get it now here: thecodeman.net/pragmatic-dotn… Curious, what’s the one rule your current codebase is missing?

@RezaTajari70 I checked, awesome!

@TheCodeMan__ Stefan check it github.com/StefanTheCode/…

𝟭𝟬 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. It will sound like an AI, but it's true: Frameworks change. Principles don’t. — Join 20,000+ engineers in the .NET Newsletter. You will learn .NET and Architecture every week directly from your email: thecodeman.net If you're starting today, focus on depth, not hype. ♻️ Repost if this helps someone. ➕ Follow for pragmatic .NET & Architecture insights.

📌 If you want to learn how to implement this properly in real .NET projects - with analyzers, architecture rules, CI gates, and practical setups, this is exactly what I teach inside: thecodeman.net/pragmatic-dotn…

p95 went from 2270 ms to 217 ms. Throughput went from 168 RPS to 1,238 RPS. I changed exactly one line of code. Thread.Sleep(200) ➜ await Task.Delay(200, ct) That's it. Same machine. Same 400 concurrent users. Same 200 ms of "work." The reason it matters this much: Thread.Sleep parks an OS thread. The thread pool only grows at 1–2 threads per second after MinThreads is exceeded. So with 400 VUs hammering a sync endpoint, requests aren't slow because the work is slow, they're slow because they're queued waiting for a thread that doesn't exist yet. await Task.Delay returns the thread to the pool while it waits. Suddenly, 16 threads can serve 400 concurrent requests instead of 16. I built a .NET 10 lab project that reproduces this on demand and produced the numbers above on a Ryzen 7 4800H. Code + k6 scripts + step-by-step breakdown. Will share it in 2h in my Newsletter. Join 20k+ engineers and read it: thecodeman.net

@spaceMonster @mjovanovictech Exactly

@mjovanovictech @TheCodeMan__ Placeholder for future improvements - you need to plan for you 2027 bonus OMG 50x speed improvement

@mjovanovictech Will be 27x

Claude Opus 4.7 now has a 15x multiple in GitHub Copilot

15x

@moacyrrp Hahahhaa

@TheCodeMan__ I’m finally evaluating other options, tks copilot 😅

I feel like most people still use Windows Server like it’s 2016. Spin up a VM. Deploy. Done. But… That’s not where things are going anymore. Windows Server 2025 + Azure Arc is pushing everything towards: → cloud + on-prem actually working together → less “where is it hosted” and more “how is it connected” And honestly, a lot of us are not thinking that way… yet. That’s why I’ll be checking out the Windows Server Summit this year; to see how people are actually building this stuff in the real world. If you're working with APIs, services, or anything distributed, this is worth your time. 📅 May 11-13 Online 👉Save the date: fandf.co/4cOF9LC (Sponsored by Microsoft)

@AramT87 See you there then

@TheCodeMan__ This is going to be a really important Summit. I am mainly interested in Azure Arc and the latest security trends in cloud.

@pavle_dav Yes, I will be there

@TheCodeMan__ Will you attend?

A lot of you went through my .NET interview questions last month. And the feedback was always the same: “Didn’t expect it to be this deep.” So I made an update. And honestly…this version is even tougher. I added: • List problems (the patterns that show up all the time) • Tree problems (the ones people usually struggle with) • full solutions with code • everything updated to .NET 10 Because real interviews are not about: - syntax - or frameworks - or remembering APIs They’re about how you think. Can you: • reason about performance? • explain trade-offs? • recognize patterns under pressure? • break down a problem without Googling? That’s what separates mid from senior. If you want to test yourself properly: 1. Take 5 minutes. 2. Go through the questions. 3. See where you get stuck. 4. That’s your roadmap. Comment Interview, and I’ll send it to you 👇 Or grab it here: thecodeman.net/pass-your-inte…

Over 1,000 developers downloaded this in a few days. And my inbox is full. Not with “thanks”. But with messages like: → “This is the first time a roadmap actually makes sense” → “Now I finally know what to build next” → “I’ve been wasting months jumping between random tutorials” That’s exactly why I made it. Because most .NET roadmaps? They look like this: → 50 boxes → Random arrows → Zero context They don’t tell you what to build. They don’t tell you what to skip. And they definitely don’t tell you when you’re ready. So I built something different. 𝗧𝗵𝗲 𝗣𝗿𝗮𝗰𝘁𝗶𝗰𝗮𝗹 .𝗡𝗘𝗧 𝗥𝗼𝗮𝗱𝗺𝗮𝗽 𝗳𝗼𝗿 𝟮𝟬𝟮𝟲 Not a list of technologies. A step-by-step path based on how real developers actually build applications. Here’s the journey: 𝗦𝘁𝗲𝗽 𝟭 → Build your first API 𝗦𝘁𝗲𝗽 𝟮 → Add a real database 𝗦𝘁𝗲𝗽 𝟯 → Validation, error handling & logging 𝗦𝘁𝗲𝗽 𝟰 → Authentication 𝗦𝘁𝗲𝗽 𝟱 → Production-ready (Docker, CI/CD, health checks) 𝗦𝘁𝗲𝗽 𝟲 → Background jobs & messaging 𝗦𝘁𝗲𝗽 𝟕 → Scale & optimize 𝗦𝘁𝗲𝗽 𝟴 → Testing Each step builds on the previous one. Each step tells you what to learn AND what to ignore. Each step has a clear “you’re ready when” checklist. What you get: ✅ 8-step learning path (beginner → job-ready) ✅ 12-week action plan ✅ 7 portfolio projects ✅ Production-ready templates ✅ MUST vs OPTIONAL breakdown ✅ What NOT to learn (this saves months) Here’s the uncomfortable truth: Most developers spend 6 months consuming content… …and still don’t have a single real project. Or: You spend 3 months building properly → and walk into interviews with proof of work. The difference isn’t talent. It’s direction. 🔗 Get it here: thecodeman.net/dotnet-roadmap… __ 📩 Next issue goes to 20,000+ engineers → thecodeman.net Now I’m curious: If I turned this into something more hands-on… Not a course. But guided learning. Real projects. Private group. Weekly direction + feedback. 👉 Would you join something like that? Or what would you want it to include?

@AntonMartyniuk Thanks for mention!

After 12 years in software development, I stopped learning from Big Tech case studies. They were impressive — but they didn't change how I think. People did. Some think that following creators won't make you skilled. And you need to write code and build apps instead. But how you think while writing that code is what separates juniors from seniors and seniors from architects. Skills come from building systems. But judgment is learned by watching how others reason about trade-offs. That's what actually compounds over time. Here are the 10 best Newsletters to read: 1. Reach Top 1% of .NET devs and Architects by @AntonMartyniuk antondevtips.com 2. Elevate Your .NET Skills To The Next Level by @mjovanovictech milanjovanovic.tech 3. Tech World with Milan (best tech deep dives and personal growth) by @milan_milanovic newsletter.techworld-with-milan.com 4. How to build .NET apps without over-engineering by @kristijan_kralj lp.devsecrets.net/join 5. .NET Newsletter and Courses by @TheCodeMan__ thecodeman.net 6. Get better in .NET & AWS by @iammukeshm codewithmukesh.com 7. .NET, Azure, Backend by @julioc juliocasal.com 8. System Design Classroom by @RaulJuncoV newsletter.systemdesignclassroom.com 9. Level Up Coding System Design Newsletter by @NikkiSiapno blog.levelupcoding.com 10. System Design One by @systemdesignone newsletter.systemdesign.one ------ ♻️ Repost to help others follow the best software development content creators ➕ Follow me ( AntonMartyniuk ) to improve your .NET and Architecture Skills