跟讀練習: Everything a .NET Developer Needs to Know in 2025 - 通過影片學習英語口語

選擇練習模式

每種模式都會開啟全屏練習室。

138 句

如果句子過短或過長，請點選 Edit 進行調整。

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.

下載應用

流利口語所需的一切

AI 發音評分逐句打分

音標練習掌握每個音

詞彙學習建立你的詞庫

詞彙遊戲邊玩邊學

掃碼

Download on theApp Store Get it onGoogle Play

FOR YOU

為什麼要通過這個影片練習口語？

在學習英語的過程中，尤其是為了提升雅思口語練習的能力，利用實際的對話影片非常重要。這類影片不僅提供了豐富的語言材料，還有助於我們理解開發人員的生態系統以及所需的技能。在影片中，Nikhil以清晰而有條理的方式闡述了2025年.NET開發人員需要掌握的內容。通過模仿他的語音、語調和表達，學習者可以提升他們的英語口語練習能力，達到更自然的溝通效果。

語法和表達的上下文

我們可以從Nikhil的講解中識別出一些重要的語法結構和表達方式：

條件句：例如“If you are a junior, you need to know part of this.”這種句子結構可以幫助學習者理解條件及其結果之間的關係。
強調語氣：他使用了“I have to be extremely clear.”來強調資訊的重要性。學習者可以模仿這種方式，使自己的表達更具說服力。
列舉和總結：在提到技能時，Nikhil使用了“And,”以及“but”來連線不同的觀點。這樣的連線詞使他的講述更加流暢，方便學習者在口語練習中使用。
無壓力的學習理念：例如“don't feel like there's pressure to you to know everything as a junior.”這樣的表達能夠讓學習者感受到輕鬆和積極，從而更願意進行英語口語練習。

常見的發音陷阱

在影片中，有一些詞彙的發音可能對學習者構成挑戰：

Git：注意這個詞的發音，很多非母語者可能會發錯，正確的發音是/gɪt/。
visual：在“Visual Studio”這個詞中，注意“vi”的發音要清晰，常常會被髮音不準的人弱化。
developer：這個詞的發音結構可能讓學習者容易混淆，注意重音在第二個音節“dev-el-op-er”。

在進行shadow speak和shadowspeak練習時，學習者可以通過反覆模仿影片中的發音，來糾正自己的發音，進一步提升口語能力。

影片中的語法

說話人最常用的結構，並附上影片中的原話：

結構	影片中的用法
現在完成時 have/has + 過去分詞 — 過去發生但與現在仍有關聯的事	We've talked · have been · hasn't gotten
被動語態 be + 過去分詞 — 強調發生了什麼，而不是誰做的	is built · is misspelled · should be added
定語從句 who / which + 從句 — 補充說明人或事物	someone who is · RepoDB, which is

什麼是跟讀法？

跟讀法 (Shadowing) 是一種有科學依據的語言學習技巧，最初開發用於專業口譯員的培訓，並由多語言者Alexander Arguelles博士普及。這個方法簡單而強大：您在聽英語母語原聲的同時立即大聲重複——就像是一個延遲1-2秒緊跟說話者的影子。與被動聽力或語法練習不同，跟讀法強迫您的大腦和口腔肌肉同時處理並模模擬實的講話模式。研究表明它能顯著提高發音準確性，語調，節奏，連讀，聽力理解和口語流利度——使其成為雅思口語備考和真實英語交流最有效的方法之一。

影子跟讀法: 閱讀完整分步指南 →

跟讀練習: Everything a .NET Developer Needs to Know in 2025 - 通過影片學習英語口語

選擇練習模式

下載應用

推薦影片

How I’d Learn Coding in 2026 (Without Wasting Years)

.NET in 100 Seconds

5 Things Under $20 Every ARCHITECT Needs

Claude Code: The Advanced Guide (99% of Devs Skip These Features)

Every Networking Concept Explained In 20 Minutes

STOP Running Code On Your Computer

Everything we learned in 29 minutes at Harvard Business School (part 1)

Fluent Forever

Everything You Need to Know About Educational Technology

Beyond Code Coverage: Functionality Testing with Playwright — Marlene Mhangami, Microsoft

My 4.9-Star iOS App Is Actually a Website: Here’s How I Built It

NCLEX 2026 Update: What’s Changing (and What’s Not) + How to Study Smarter | SimpleNursing

為什麼要通過這個影片練習口語？

語法和表達的上下文

常見的發音陷阱

影片中的語法

什麼是跟讀法？