Anton Martyniuk

𝗛𝗮𝗹𝗳 𝗼𝗳 𝟮𝟬𝟮𝟲 𝗶𝘀 𝗲𝗻𝗱𝗶𝗻𝗴 𝗶𝗻 𝟯𝟬 𝗱𝗮𝘆𝘀
If you're still trying to level up as a .NET developer, that day won't magically come.

Here is a simple, structured 8-week .NET learning roadmap you can start today.

Week 1: .NET 10 and C# 14
Learn the new features from C# 8 to C# 14.
Learn new LINQ methods from .NET 6 to .NET 10
Improve your skills in and async programming, parallel processing and thread synchronization.

Get Free .NET Roadmap:
https://lnkd.in/d2smTQmr

Week 2: Web APIs in .NET
Build your Web API → Minimal APIs, Controllers, routing, validation, filters, and middleware.
Learn how to improve performance: OutputCaching, HybridCache, ResponseCompression, customize JSON settings, and Rate Limiting.

Free guide: https://lnkd.in/gndP8mx2

Week 3: Data Access & EF Core
Improve data access with EF Core → query optimization, migrations, relationships, LINQ.
Learn how to improve query performance: optimize projections, AsNoTracking, Eager Loading, Pagination, Compiled Queries, AsSplitQuery, raw SQL.

Free guide: https://lnkd.in/d6K7pBPJ

Week 4: Authentication & Authorization
JWT, Refresh tokens, identity providers, claims, roles, and secure API design.

Free guide: https://lnkd.in/eX7mDKtT

Week 5: Architecture Basics
Learn how to structure your solution with Clean Architecture and Vertical Slices. When to use and when to avoid Repositories, how to prevent code duplication and how to avoid over-engineering.

Free guide: https://lnkd.in/eQx6b3xe

Week 6: Testing Essentials
Write unit tests, integration tests, architecture and load tests.

Week 7: CI/CD & Deployments
Add .NET Aspire orchestration to your project.
Learn how to deploy with GitHub Actions, Docker and Cloud deployment.

Free guide on project setup: https://lnkd.in/dTWhZtFD

Week 8: Final Project
Bring everything together → real app, real APIs, real database, real architecture.

If you want a clear starting point without wasting hours deciding folder structures, naming conventions, or architecture...

👉 Use my .NET Project Template.
It gives you a clean, professional, production-ready structure you can build your entire learning roadmap on:
↳ https://lnkd.in/dWsDws_x

👉 I've compiled 650+ hand-picked resources for mastering all the mentioned topics in C#, .NET, ASP .NET Core, and EF Core. Get PDF for free:
↳ https://lnkd.in/d2ytfzGn

——

♻️ Repost to help others learn .NET with a clear roadmap

➕ Follow me ( Anton Martyniuk ) to improve your .NET and Architecture Skills

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 Anton Martyniuk
https://antondevtips.com/

2. Elevate Your .NET Skills To The Next Level by Milan Jovanović
https://lnkd.in/duVZ88q3

3. Tech World with Milan (best tech deep dives and personal growth) by Dr Dr Milan Milanović
https://lnkd.in/dQEhn_YP

4. How to build .NET apps without over-engineering by Kristijan Kralj
https://lnkd.in/dVU3FBeW

5. .NET Newsletter and Courses by Stefan Đokić
https://thecodeman.net/

6. Get better in .NET & AWS by Mukesh Murugan
http://codewithmukesh.com/

7. .NET, Azure, Backend by Julio Casal
https://juliocasal.com/

8. System Design Classroom by Raul Junco
https://lnkd.in/dgwJXPN6

9. Level Up Coding System Design Newsletter by Nikki Siapno
https://lnkd.in/dtdmMpFi

10. System Design One by Neo Kim
https://lnkd.in/dSfi5Ui3

------

♻️ Repost to help others follow the best software development content creators

➕ Follow me ( Anton Martyniuk ) to improve your .NET and Architecture Skills

👉 I just created something I wish I had 12 years ago.

I've compiled 650+ hand-picked resources for mastering C#, .NET, ASP .NET Core, EF Core, and Microservices.

These resources will help developers level up with targeted knowledge.

I spent hours putting them together from my library.

You can get these resources for free as PDF.

This isn't just another PDF - it's the ultimate learning guide I always wanted when I started my developer journey.

Inside, you'll find carefully selected resources:

📌 Official docs, tutorials, and guides

📌 Best blogs, videos

📌 Expert tips from my 12+ years as a .NET Technical Lead and Microsoft MVP

Why trust me?

Each Tuesday, 𝟮𝟱,𝟬𝟬𝟬+ developers receive my newsletter filled with practical tips on building robust, scalable .NET applications.

My goal?

To help developers craft better software, faster, using the right tools for each case.

Want this PDF?

Here's how you get it:

1️⃣ Follow me Anton Martyniuk
2️⃣ Comment ".NET" below 👇
3️⃣ I'll send the PDF your way!
4️⃣ Repost to help more developers get these resources!

♻️ Repost to help others get these resources

➕ Follow me ( Anton Martyniuk ) to improve your .NET and Architecture Skills

Comment ".NET" now, and you will get the best set of resources for free, you can't find anywhere else.

P.S.: Stay subscribed to my Newsletter to ensure you receive future updates

𝗔𝗿𝗲 𝗬𝗼𝘂 𝗡𝗮𝗺𝗶𝗻𝗴 𝗬𝗼𝘂𝗿 𝗗𝗧𝗢𝘀 𝗖𝗼𝗿𝗿𝗲𝗰𝘁𝗹𝘆? 🤔

What naming convention to pick 👇

When building Web APIs, your endpoints consume and produce data.

A common convention is to suffix these models with DTO (Data Transfer Object).

But here's the problem 👇

❌ DTOs often mix input and output into the same class.

❌ Over time, they become bloated and confusing.

👉 My preferred approach: use Request and Response suffixes instead:
• CreateUserRequest (for input)
• UserResponse (for output)

Why is this better?

✅ Clear Intent – you instantly know if it's for input or output model.

✅ Scalable – changes to Response models don't affect Request models.

✅ Maintainable – no more guessing what a "UserDto" is supposed to represent.

📌 Pro tip: Be consistent. Whatever convention you choose, apply it across the codebase.

Here are 15 more mistakes developers make when creating Web APIs:
https://lnkd.in/dmXF55VJ

—

♻️ Repost to help others choose better naming conventions

➕ Follow me ( Anton Martyniuk ) to improve your .NET and Architecture Skills

With Dapper you run the application and it crashes because of a bug in SQL string
Here is how to fix it 👇

Dapper is fast and gives you full control over SQL.
But that control comes with a hidden cost.

Every INSERT, UPDATE, and DELETE you write lives inside a string.
And strings have zero type safety.

↳ Rename a column? No compile error.
↳ Change a property type? No compile error.
↳ Misspell a parameter name? No compile error.

You only find out something is broken when your app crashes at runtime.

Here is what most developers do when using Dapper:
❌ Write SQL commands as plain strings
❌ Map every parameter by hand
❌ Repeat the same column lists across Insert, Update, and Delete
❌ Hardcode table and schema names everywhere

One small refactor breaks half of your queries.
And the compiler will not save you.

There is a much better way.

In my latest video, I show how to solve this with 𝗗𝗮𝗽𝗽𝗲𝗿 𝗣𝗹𝘂𝘀 𝗠𝗮𝗽𝗽𝗶𝗻𝗴.

Dapper Plus gives you 3 ways to map your entities to the database - all type-safe.

𝟭. 𝗔𝘂𝘁𝗼 𝗠𝗮𝗽𝗽𝗶𝗻𝗴
→ Zero configuration needed
→ Library matches class name to table name
→ Properties match column names automatically
→ Just call SingleInsert or BulkInsert and it works

𝟮. 𝗗𝗮𝘁𝗮 𝗔𝗻𝗻𝗼𝘁𝗮𝘁𝗶𝗼𝗻𝘀
→ Use [Table], [Column], [Key], [NotMapped] attributes
→ Familiar to anyone using EF Core
→ Keeps mapping next to your model

𝟯. 𝗙𝗹𝘂𝗲𝗻𝘁 𝗔𝗣𝗜 𝗠𝗮𝗽𝗽𝗶𝗻𝗴
→ Full control with strongly-typed lambdas
→ Map only what you need: .Map(x => new { x.Name, x.Price })
→ MapAuto method and DapperPlus figures it out for you
→ Refactor-friendly: rename a property and the compiler tells you

You can also organize mappings with 𝗗𝗮𝗽𝗽𝗲𝗿 𝗣𝗹𝘂𝘀 𝗖𝗼𝗻𝘁𝗲𝘅𝘁:
→ Global context - configure once at startup
→ Instance context - configure per use case
→ Inheritance context - reuse mappings across services

And the best part?

The same mapping works for 𝗯𝗼𝘁𝗵 free Single methods 𝗮𝗻𝗱 paid Bulk methods.

No more SQL strings scattered across your codebase.
No more runtime surprises after a refactor.
Just clean, type-safe writes.

Watch the full video and see all 3 mapping approaches in action.

P.S.: You can get a free trial for this library and test for 30 days, and you can extend the trial for another month as needed.

Get started with Dapper Plus Mapping:
https://lnkd.in/dEZr-BHv

Here is the source code:
https://lnkd.in/d98dxfGj

How do you solve runtime bugs in SQL strings when using Dapper? Share below 👇

——
♻️ Repost to help others write type-safe Dapper queries

➕ Follow me ( Anton Martyniuk ) to improve your .NET and Architecture Skills

Many thanks to ZZZ Projects for sponsoring this post

Dapper 𝗵𝗮𝘀 𝗮 𝗯𝗶𝗴 𝗽𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 𝗽𝗲𝗻𝗮𝗹𝘁𝘆 𝘄𝗵𝗲𝗻 𝘆𝗼𝘂 insert multiple rows.

Here is how to address this problem 👇

Developers love Dapper for blazing-fast reads.

But for inserting or updating many rows, it becomes painfully slow.
(even slower than EF Core)

But Why?

Dapper sends each row to the database one by one.
10,000 rows = 10,000 round-trips.

And here is another problem:
↳ You need to write a lot of boilerplate code when using Dapper.

Here is what most developers do when using Dapper:
❌ Write manual INSERT and UPDATE SQL statements
❌ Build complex SQL with hundreds of parameters by hand
❌ Write CREATE TABLE scripts

And the problem is that you don't have type safety when writing SQL commands inside strings. When something goes wrong you will only know at runtime.

There is a much better way.

In my latest video, I show how to solve this with 𝗗𝗮𝗽𝗽𝗲𝗿 𝗣𝗹𝘂𝘀.

👉 𝗦𝘁𝗼𝗽 𝗪𝗿𝗶𝘁𝗶𝗻𝗴 𝗖𝗼𝗺𝗽𝗹𝗲𝘅 𝗦𝗤𝗟 𝘁𝗼 𝗦𝗮𝘃𝗲 𝗗𝗮𝘁𝗮 - 𝗟𝗲𝘁 𝗗𝗮𝗽𝗽𝗲𝗿 𝗣𝗹𝘂𝘀 𝗗𝗼 𝗜𝘁 𝗳𝗼𝗿 𝗬𝗼𝘂.

Dapper Plus gives you clean, simple methods for every write operation.

𝗙𝗿𝗲𝗲 𝗦𝗶𝗻𝗴𝗹𝗲 𝗠𝗲𝘁𝗵𝗼𝗱𝘀:
→ SingleInsert - insert one entity without writing SQL
→ SingleUpdate - update one entity
→ SingleDelete - delete one entity
→ SingleMerge - upsert in one line (insert or update)
→ SingleSynchronize - keep your data in sync with the source
→ CreateTable - create the table directly from your C# class

No more manual SQL.
No more parameter mapping by hand.
Just call the method and Dapper Plus handles the rest.

All single methods are 𝗳𝗿𝗲𝗲 𝘁𝗼 𝘂𝘀𝗲.

𝗣𝗮𝗶𝗱 𝗕𝘂𝗹𝗸 𝗠𝗲𝘁𝗵𝗼𝗱𝘀 (for high performance):
→ BulkInsert
→ BulkUpdate
→ BulkDelete
→ BulkMerge
→ BulkSynchronize

This is where the real magic happens.

I inserted 10,000 product records into the database:
❌ Dapper: 7,000 ms
✅ Dapper Plus BulkInsert: 300 ms

That is over 𝟵𝟲% 𝗳𝗮𝘀𝘁𝗲𝗿 with a single line of code.

Dapper Plus supports SQL Server, PostgreSQL, MySQL, Oracle, MariaDB, and SQLite.

Watch the full video and see every method in action.

P.S.: You can get a free trial for this library and test for 30 days, and you can extend the trial for another month as needed.

Get started with Dapper Plus:
https://lnkd.in/duEZ7DzW

Here is the source code:
https://lnkd.in/d98dxfGj

How do you currently handle bulk inserts in Dapper? Share below 👇

——
♻️ Repost to help others speed up their Dapper write queries

➕ Follow me ( Anton Martyniuk ) to improve your .NET and Architecture Skills

Many thanks to ZZZ Projects for sponsoring this post

With Dapper you run the application and it crashes because of a bug in SQL string
Here is how to fix it 👇

Dapper is fast and gives you full control over SQL.
But that control comes with a hidden cost.

Every INSERT, UPDATE, and DELETE you write lives inside a string.
And strings have zero type safety.

↳ Rename a column? No compile error.
↳ Change a property type? No compile error.
↳ Misspell a parameter name? No compile error.

You only find out something is broken when your app crashes at runtime.

Here is what most developers do when using Dapper:
❌ Write SQL commands as plain strings
❌ Map every parameter by hand
❌ Repeat the same column lists across Insert, Update, and Delete
❌ Hardcode table and schema names everywhere

One small refactor breaks half of your queries.
And the compiler will not save you.

There is a much better way.

In my latest video, I show how to solve this with 𝗗𝗮𝗽𝗽𝗲𝗿 𝗣𝗹𝘂𝘀 𝗠𝗮𝗽𝗽𝗶𝗻𝗴.

Dapper Plus gives you 3 ways to map your entities to the database - all type-safe.

𝟭. 𝗔𝘂𝘁𝗼 𝗠𝗮𝗽𝗽𝗶𝗻𝗴
→ Zero configuration needed
→ Library matches class name to table name
→ Properties match column names automatically
→ Just call SingleInsert or BulkInsert and it works

𝟮. 𝗗𝗮𝘁𝗮 𝗔𝗻𝗻𝗼𝘁𝗮𝘁𝗶𝗼𝗻𝘀
→ Use [Table], [Column], [Key], [NotMapped] attributes
→ Familiar to anyone using EF Core
→ Keeps mapping next to your model

𝟯. 𝗙𝗹𝘂𝗲𝗻𝘁 𝗔𝗣𝗜 𝗠𝗮𝗽𝗽𝗶𝗻𝗴
→ Full control with strongly-typed lambdas
→ Map only what you need: .Map(x => new { x.Name, x.Price })
→ MapAuto method and DapperPlus figures it out for you
→ Refactor-friendly: rename a property and the compiler tells you

You can also organize mappings with 𝗗𝗮𝗽𝗽𝗲𝗿 𝗣𝗹𝘂𝘀 𝗖𝗼𝗻𝘁𝗲𝘅𝘁:
→ Global context - configure once at startup
→ Instance context - configure per use case
→ Inheritance context - reuse mappings across services

And the best part?

The same mapping works for 𝗯𝗼𝘁𝗵 free Single methods 𝗮𝗻𝗱 paid Bulk methods.

No more SQL strings scattered across your codebase.
No more runtime surprises after a refactor.
Just clean, type-safe writes.

Watch the full video and see all 3 mapping approaches in action.

P.S.: You can get a free trial for this library and test for 30 days, and you can extend the trial for another month as needed.

Get started with Dapper Plus Mapping:
https://lnkd.in/dEZr-BHv

Here is the source code:
https://lnkd.in/d98dxfGj

How do you solve runtime bugs in SQL strings when using Dapper? Share below 👇

——
♻️ Repost to help others write type-safe Dapper queries

➕ Follow me ( Anton Martyniuk ) to improve your .NET and Architecture Skills

Many thanks to ZZZ Projects for sponsoring this post

Managing Windows Server in 2026 is harder than it has ever been.

Hybrid setups, AI workloads, and security threats keep piling up

Most teams I talk to are stuck in the same loop:
❌ Patching servers that need a full restart (and downtime)
❌ Managing on-prem, cloud, and edge with 5 different tools
❌ Guessing how to prepare infrastructure for AI workloads
❌ Worrying about post-quantum threats with no clear plan
❌ Migrating to the cloud manually, server by server

The result? Burned-out admins and fragile infrastructure.

That will change when you see what Microsoft is doing at the 𝗪𝗶𝗻𝗱𝗼𝘄𝘀 𝗦𝗲𝗿𝘃𝗲𝗿 𝗦𝘂𝗺𝗺𝗶𝘁 𝟮𝟬𝟮𝟲.

It's a free 3-day virtual event (May 11-13) where the actual Microsoft engineering teams walk through what's new, what's coming, and how to use it.

Here are the sessions I'm most excited about:

📌 𝗗𝗮𝘆 𝟭 - 𝗩𝗶𝘀𝗶𝗼𝗻 𝗮𝗻𝗱 𝗖𝗼𝗿𝗲 𝗧𝗲𝗰𝗵
→ Windows Server 2025 in Practice - Hotpatching without restarts
→ The Future of Hyper-V - performance roadmap and faster recovery
→ Security Baselines and Benchmarks - real demos, not slideware
→ Evolving Server Management with Azure Arc and System Center

📌 𝗗𝗮𝘆 𝟮 - 𝗠𝗼𝗱𝗲𝗿𝗻 𝗧𝗼𝗼𝗹𝘀 𝗮𝗻𝗱 𝗔𝗜
→ Azure Arc for Servers - one control panel for everything
→ Windows Admin Center Virtualization Mode (this looks huge)
→ AI-powered server migration to Azure
→ AI Workloads on Windows Server - hardware planning that actually scales

📌 𝗗𝗮𝘆 𝟯 - 𝗙𝗲𝗲𝗱𝗯𝗮𝗰𝗸 𝗮𝗻𝗱 𝗔𝗱𝘃𝗮𝗻𝗰𝗲𝗱 𝗙𝗲𝗮𝘁𝘂𝗿𝗲𝘀
→ Future-Proofing PKI for post-quantum security
→ Modernize AD for hybrid identity
→ Failover Clustering at scale (cloud that never goes down)

But here's the part most people miss

The Summit is not a one-way broadcast.
There is a dedicated Feedback session on Day 3 where you can tell Microsoft directly what is working and what is not.

This is your chance to shape the next version of Windows Server.
The product team listens. The roadmap actually changes based on this input.

For anyone running on-prem, hybrid, or planning AI workloads, this is the highest-signal event of the year.

✅ It's free
✅ It's virtual
✅ Sessions are recorded
✅ You hear directly from the engineering teams

Register for the free event here:
👉 https://fandf.co/4tPYnWP

——

♻️ Repost to help others modernize their Windows Server setup
 
👉 Follow me ( Anton Martyniuk ) to improve your .NET and Architecture Skills

Many thanks to Microsoft Developer for sponsoring this post!