ฝึกพูดภาษาอังกฤษด้วยเทคนิค Shadowing จากวิดีโอ: Everything a .NET Developer Needs to Know in 2025

การควบคุม Shadowing

0% เสร็จสิ้น (0/138 ประโยค)

Hello everybody, I'm Nikhil.

⏸ หยุดชั่วคราว

ความเร็ว:

จำนวนรอบ:

โหมดรอ:

ซิงค์คำบรรยาย:0ms

ประโยคทั้งหมด

138 ประโยค

Hello everybody, I'm Nikhil.

Welcome to my .NET Developer Roadmap for 2025.

Like every year, I'm releasing one of those so you can understand how you can navigate the ecosystem and what you need to learn as a .NET developer.

Now, I have to be extremely clear.

Everything you see here is an exhaustive list, meaning you don't actually need to know everything as a .NET developer.

If you are a junior, you need to know part of this.

If you're a mid, a bit more.

if you're a senior a bit more and if you're principal or a lead then ideally everything but don't feel like there's pressure to

you to know everything as a junior or someone just starting you don't i will explain how things are per level as we go and

also this is an interactive roadmap that you can get download and then keep track of for yourself so for example if you say oh i learned git

i don't need to worry about this anymore i can go ahead and say that this is now done and you can keep track of your progress for yourself.

Now something very interesting this year is that we didn't really have much of a change between 2024 and 2025 in the ecosystem.

So if you watch the old video, you really don't need to watch this one.

There are some new things and I will give new context on several things that changed.

But if you're already someone who is familiar with the ecosystem, then you don't need this.

This is just my opinion.

So what do we have here?

Well, we have all of these things that I'm going to go in in a second.

But before that, like last year, I'm offering a 20% discount code to anyone downloading this roadmap.

So you can use the link in the description, download it, you're going to get the code you can use in any course or bundle, as well as on any online workshop that I'm running.

Yes, we just launched some online workshops where I am live with you, teaching you a certain topic for two full days.

So link in the description for that.

Not only that, but until the end of February, you can get our two C Sharp courses, the Getting Started and the Deep Dive completely for free and they're yours to keep.

Use that link in the description and 11 hours of content is yours.

That's all the marketing I'm going to do.

The last thing I want to mention is that if there's a star next to any of those things listed, then on Dome Trainer we have a course for it.

If not, then we don't.

Okay, so to start with, we have general developer skills.

Version control is the most important thing you need to know.

Git, it's the standard.

I know this changes if you're in game development and you use Unity or UE, and there are different softwares you need to use for that.

But even then, you really need to know how to use Git, and you really need to know how to use GitHub.

You might need to also be able to use GitLab or Bitbucket, depending on what your company is using.

But all of that is built on the same principle, so you need to know Git.

then you need to know how to search.

So Google is a must know.

And that's what this green tick means.

Stack Overflow having a purple tick means that it's a good to know.

And that's because I see less and less Stack Overflow usability and usefulness over time.

And that's why ChatGPT this year is a must know.

It's gotten way, way better.

And I can tell you from personal use that I use that way more than Stack Overflow.

Surprisingly, it's getting really, really accurate.

It's not perfect yet.

And if you have a suspicions that it might be wrong, please check on Stack Overflow too.

This can fix many of your problems and answer many of your questions.

Then we have IDs.

You need to know that's a new addition.

I didn't know why I didn't have it previously.

You need to know how to use Visual Studio or Rider.

Now with the free non-commercial plan, I highly recommend it for everybody.

Visual Studio Code is a good alternative, especially with a C-Sharp dev kit, but that does require a license for commercial use, same as Visual Studio.

so make sure you check that out and then cursor is an interesting alternative i have my eyes on i think eventually visual studio

and the visual studio team will integrate everything that cursor can do in visual studio code however for now it is

an amazing id it integrates ai features into your id and it's just mind-blowing what you can do i can do front-end even on a back-end developer that's how good it is.

Then for C Sharp we have C Sharp 13, .NET 9, .NET CLI as well as .NET Aspire which this year in my opinion is a must know.

Everyone needs to know .NET Aspire.

The biggest brain of the .NET team are on this.

You should absolutely know how to use it and integrate it into your applications especially if you're doing distributed systems and cloud stuff.

Then we have the solid principles as well as Yanni Dry and Kiss.

We've talked about this a billion times as well as ASP.NET Core, basics from web API to minimal API routing, all the way to things like Jot, Basic Auth, and all the other types of auth that are extremely, extremely popular.

When you have the RDBMS databases, you need to know your SQL syntax, you need to know how RDBMSs work, indexes, how to write queries, SQL, those are fundamentals that every developer needs to know.

I still am against stored procedures and triggers, you should not be using these features anymore, they have problems.

And if you want to see a video on why you should use the procedures, for example, leave a comment down below and I will make that video.

As well as the engines you should know, like PostgresQL, extremely popular, one of the most popular, if not the most popular, RDBMS engine out there.

And then SQL Server and MySQL or MariaDB.

Then you have your REST, Minimal API, Fast and Point as an alternative, Hot Chocolate for GraphQL, and then GRPC.

You have your Dapper for database connections is what I use, but you can also use EntiFirmware Core with all of these other sub-branches.

And you have RepoDB, which is a hybrid scenario.

And then you have an Hibernate, which I think you should not really use anymore.

It's very archaic at this point.

And then you have Dependency Injection, the native package, and then Scrutor to add some interesting extensions.

You have your NoSQL databases, such as Redis and Elasticsearch, as well as cloud proprietary ones like DynamoDB, CosmosDB.

You might also have MongoDB here.

You might also have RavenDB here.

There's many type of NoSQL databases as well as Couchbase, I think.

So there's many, many options, but ultimately those are the ones you should know.

If you know these, then you can adapt your knowledge on NoSQL databases on any other NoSQL database because they're built on the same patterns.

Then you have your caching, output caching, response caching, as well as Redis caching with the Stack Exchange library.

We have your logging with the logging extensions package, as well as Serilog.

I recommend you know both.

I do use both myself.

Then you have your messaging.

So Service Bus, CW, UFS, NSXQS, RabbitMQ, Mass Transit, Wolverine.

I am back at recommending N Service Bus this year.

That's because they have been seriously improving and modernizing the product.

So I think it's worth another shot.

I still think ultimately mass transit is a better library, but it is a great package to use as well, especially with all the modernization efforts.

Then you have unit testing.

You know, I still stand by X unit and unit is a great alternative.

MS test is getting better, but it hasn't gotten better enough for me to be able to recommend it as an alternative yet.

But I think next year this will be changing.

Then we also have TUnit that just sort of launched, but I don't want to put it in here yet.

I'm keeping an eye on it.

Maybe next year TUnit will also be here.

It's a greatly designed library, I think, and it has a bright, bright future if the developer keeps working on it.

Then any of the mocking libraries, N Substitute is what I'm using.

mock and then fake it easy that not that many people use but still a great library this year i recommend shouldly for fluent sessions so

a session is done in a fluent way i advise against fluent sessions the library due to the package changes and the bait and switch then

100

you have test data generation bogus is great for realistic looking fake data and then auto fixture for the rest integration testing again i

101

stand by test containers and respawn you can do tons of things with it and this year I added architectures and paradigms so I do think to some capacity you should be aware with domain design,

102

clean architecture, modular monoliths, vertical slice architecture, event-driven architecture, and event source.

103

Again, if you're on a strong web start, we do have courses on all of those things.

104

So you should definitely take a look at it if you are looking to join a company that uses any of those.

105

Snapshot testing, Verify is a must-know.

106

I don't know why I forgot to change this.

107

This should be a green.

108

Verify is an excellent, excellent library for verifying test data.

109

Then end-to-end testing playwright is great.

110

Performance testing K6 is still the boss, in my opinion.

111

And then you have things like async documentation, open API.

112

We don't have swagger anymore that you need to know, not that this is a specific type of technology.

113

It was just a flavor of visualizing everything.

114

Then API documentation, open API more relevant than ever with the latest .NET 9 changes.

115

Async API is still there.

116

If you want to document your async APIs, then you have Riffit still as the king of API SDK libraries.

117

You have your task scheduling, as well as OpenTelemetry being the king of monitoring and telemetry.

118

I think you still need to know Prometheus, Grafana, and the ELK stack.

119

All of these are used pretty much everywhere.

120

Then in terms of containers, you have Docker and Podman as an alternative, especially with the license changes.

121

Some people are using Podman now.

122

Then you still have orchestration with Kubernetes and tooling with K9 and Lens if you want to visualize what's going on into your cluster.

123

Then we have serverless, Azure Functions, NWS Lambdas, of course, and file storage.

124

This is misspelled, Azure Storage, and AWS S3.

125

In terms of libraries, again, poly, fluent validation, that hasn't changed yet into a paid license, hopefully it doesn't.

126

Humanizer Core for humanizing your context of your application.

127

than benchmark.net, a must know in my opinion nowadays, mediator and units.net again from human readable units, as well as DevOps with infrastructure as code with Terraform and Pulumi.

128

Terraform in many ways is still the king and Pulumi.

129

I should point out that you should really know whatever your cloud provider is also using.

130

So the CDK for AWS or BICEP for Azure, I will add them into this list as well.

131

But ultimately, that's all there is to it in my opinion.

132

I didn't want to make it extremely long because I don't want to scare you with how many things you need to learn.

133

And that's why I didn't talk about some of the other subjects.

134

Yeah, they're here, but maybe they're not as relevant for you.

135

But now I wonder from you, what do you think about this roadmap and what do you think is missing or should be added or even changed or removed?

136

Leave a comment down below and let me know.

137

Well, that's all I had for you for this video.

138

Thank you very much for watching and as always, keep coding.

YouTube

4.9/5 บน App Store และ Google Play

Shadowing English
บนมือถือ

เรียนภาษาอังกฤษได้ทุกที่ทุกเวลาด้วยแอป Shadowing English พัฒนาทักษะการสื่อสารของคุณวันนี้!

ติดตามความคืบหน้าในการเรียนรู้ของคุณ

การให้คะแนน AI และการแก้ไขข้อผิดพลาด

คลังวิดีโอที่หลากหลาย

สแกนเพื่อดาวน์โหลด

Download on theApp Store

GET IT ONGoogle Play

เทคนิค Shadowing คืออะไร?

Shadowing เป็นเทคนิคการเรียนรู้ภาษาที่ได้รับการรับรองทางวิทยาศาสตร์ พัฒนาขึ้นสำหรับการฝึกนักแปลมืออาชีพ วิธีการนี้เรียบง่ายแต่ทรงพลัง: คุณฟังเสียงภาษาอังกฤษจากเจ้าของภาษาและพูดตามทันที — เหมือนเงาที่ตามผู้พูดด้วยช่วงเวลาห่าง 1-2 วินาที การวิจัยแสดงว่าเทคนิคนี้ปรับปรุงความแม่นยำในการออกเสียง ทำนองเสียง จังหวะ การเชื่อมเสียง การฟังเข้าใจ และความคล่องแคล่วในการพูดได้อย่างมีนัยสำคัญ

☕ เลี้ยงกาแฟเราสักแก้ว

ShadowingEnglish ยังคงเปิดให้ใช้งาน ฟรี 100% ได้ด้วยการสนับสนุนจากคุณ ค่าใช้จ่ายสำหรับเซิร์ฟเวอร์และ AI นั้นสูงมาก — กาแฟของคุณช่วยให้เราเดินหน้าต่อไปได้! 🙏

บริจาคผ่าน PayPal

ShadowingEnglish.com – ฝึกพูดภาษาอังกฤษแบบ Shadowing

ฝึกพูดภาษาอังกฤษด้วยเทคนิค Shadowing จากวิดีโอ: Everything a .NET Developer Needs to Know in 2025

Shadowing English
บนมือถือ

เกี่ยวกับบทเรียนนี้

คำศัพท์และวลีสำคัญ

เคล็ดลับการฝึกฝน

เทคนิค Shadowing คืออะไร?

ฝึกพูดภาษาอังกฤษด้วยเทคนิค Shadowing จากวิดีโอ: Everything a .NET Developer Needs to Know in 2025

Shadowing English บนมือถือ

เกี่ยวกับบทเรียนนี้

คำศัพท์และวลีสำคัญ

เคล็ดลับการฝึกฝน

เทคนิค Shadowing คืออะไร?

Shadowing English
บนมือถือ