Pratica di Shadowing: Everything a .NET Developer Needs to Know in 2025 - Impara a parlare inglese con YouTube

C2
Controlli di Shadowing
0% completato (0/138 frasi)
Hello everybody, I'm Nikhil.
⏸ In Pausa
Tutte le Frasi
138 frasi
1
Hello everybody, I'm Nikhil.
2
Welcome to my .NET Developer Roadmap for 2025.
3
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.
4
Now, I have to be extremely clear.
5
Everything you see here is an exhaustive list, meaning you don't actually need to know everything as a .NET developer.
6
If you are a junior, you need to know part of this.
7
If you're a mid, a bit more.
8
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
9
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
10
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
11
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.
12
Now something very interesting this year is that we didn't really have much of a change between 2024 and 2025 in the ecosystem.
13
So if you watch the old video, you really don't need to watch this one.
14
There are some new things and I will give new context on several things that changed.
15
But if you're already someone who is familiar with the ecosystem, then you don't need this.
16
This is just my opinion.
17
So what do we have here?
18
Well, we have all of these things that I'm going to go in in a second.
19
But before that, like last year, I'm offering a 20% discount code to anyone downloading this roadmap.
20
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.
21
Yes, we just launched some online workshops where I am live with you, teaching you a certain topic for two full days.
22
So link in the description for that.
23
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.
24
Use that link in the description and 11 hours of content is yours.
25
That's all the marketing I'm going to do.
26
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.
27
If not, then we don't.
28
Okay, so to start with, we have general developer skills.
29
Version control is the most important thing you need to know.
30
Git, it's the standard.
31
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.
32
But even then, you really need to know how to use Git, and you really need to know how to use GitHub.
33
You might need to also be able to use GitLab or Bitbucket, depending on what your company is using.
34
But all of that is built on the same principle, so you need to know Git.
35
then you need to know how to search.
36
So Google is a must know.
37
And that's what this green tick means.
38
Stack Overflow having a purple tick means that it's a good to know.
39
And that's because I see less and less Stack Overflow usability and usefulness over time.
40
And that's why ChatGPT this year is a must know.
41
It's gotten way, way better.
42
And I can tell you from personal use that I use that way more than Stack Overflow.
43
Surprisingly, it's getting really, really accurate.
44
It's not perfect yet.
45
And if you have a suspicions that it might be wrong, please check on Stack Overflow too.
46
This can fix many of your problems and answer many of your questions.
47
Then we have IDs.
48
You need to know that's a new addition.
49
I didn't know why I didn't have it previously.
50
You need to know how to use Visual Studio or Rider.
51
Now with the free non-commercial plan, I highly recommend it for everybody.
52
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.
53
so make sure you check that out and then cursor is an interesting alternative i have my eyes on i think eventually visual studio
54
and the visual studio team will integrate everything that cursor can do in visual studio code however for now it is
55
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.
56
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.
57
Everyone needs to know .NET Aspire.
58
The biggest brain of the .NET team are on this.
59
You should absolutely know how to use it and integrate it into your applications especially if you're doing distributed systems and cloud stuff.
60
Then we have the solid principles as well as Yanni Dry and Kiss.
61
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.
62
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.
63
I still am against stored procedures and triggers, you should not be using these features anymore, they have problems.
64
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.
65
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.
66
And then SQL Server and MySQL or MariaDB.
67
Then you have your REST, Minimal API, Fast and Point as an alternative, Hot Chocolate for GraphQL, and then GRPC.
68
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.
69
And you have RepoDB, which is a hybrid scenario.
70
And then you have an Hibernate, which I think you should not really use anymore.
71
It's very archaic at this point.
72
And then you have Dependency Injection, the native package, and then Scrutor to add some interesting extensions.
73
You have your NoSQL databases, such as Redis and Elasticsearch, as well as cloud proprietary ones like DynamoDB, CosmosDB.
74
You might also have MongoDB here.
75
You might also have RavenDB here.
76
There's many type of NoSQL databases as well as Couchbase, I think.
77
So there's many, many options, but ultimately those are the ones you should know.
78
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.
79
Then you have your caching, output caching, response caching, as well as Redis caching with the Stack Exchange library.
80
We have your logging with the logging extensions package, as well as Serilog.
81
I recommend you know both.
82
I do use both myself.
83
Then you have your messaging.
84
So Service Bus, CW, UFS, NSXQS, RabbitMQ, Mass Transit, Wolverine.
85
I am back at recommending N Service Bus this year.
86
That's because they have been seriously improving and modernizing the product.
87
So I think it's worth another shot.
88
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.
89
Then you have unit testing.
90
You know, I still stand by X unit and unit is a great alternative.
91
MS test is getting better, but it hasn't gotten better enough for me to be able to recommend it as an alternative yet.
92
But I think next year this will be changing.
93
Then we also have TUnit that just sort of launched, but I don't want to put it in here yet.
94
I'm keeping an eye on it.
95
Maybe next year TUnit will also be here.
96
It's a greatly designed library, I think, and it has a bright, bright future if the developer keeps working on it.
97
Then any of the mocking libraries, N Substitute is what I'm using.
98
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
99
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.
4.9/5 su App Store & Google Play

Shadowing English Su Mobile

Impara l'inglese sempre e ovunque con l'app Shadowing English. Migliora le tue capacità di comunicazione oggi stesso!

Tieni traccia dei tuoi progressi di apprendimento
Valutazione e correzione degli errori tramite intelligenza artificiale
Ricca libreria video
Download on theApp Store
GET IT ONGoogle Play
Shadowing English Mobile App

Perché praticare la conversazione con questo video?

Praticare la conversazione in inglese è essenziale per migliorare la propria fluency e confidenza. Questo video, presentato da un esperto sviluppatore .NET, offre un contesto reale e professionale in cui si può ascoltare un linguaggio tecnico e pertinente. Attraverso il shadowing in inglese, puoi imitare e ripetere le frasi, acquisendo così una migliore intonazione e ritmo. I contenuti sono stati scelti per stimolare la tua curiosità e rendere l'apprendimento più coinvolgente. Ogni volta che pratichi, non solo migliori la tua pronuncia, ma anche la tua capacità di comprendere termini specifici del settore, cruciali per chi aspira a lavorare nel campo della programmazione.

Grammatica & Espressioni nel Contesto

Nel video, il presentatore utilizza varie strutture grammaticali e espressioni che meritano di essere analizzate:

  • Uso dei tempi verbali: L'uso del presente semplice per descrivere fatti generali, come "Git è lo standard" e "Google è un must know", è fondamentale per esprimere verità universali.
  • Condizionale: Frasi come "se sei un junior, devi sapere parte di questo" forniscono indicazioni su cosa gli utenti devono apprendere in base al loro livello di esperienza.
  • Frasi imperativa: “Scarica questa roadmap” è un esempio di come il tono diretto possa motivare l'azione, ottimo per incoraggiare chi sta imparando.
  • Terminologia settoriale: Frasi come "version control" e "IDEs" rappresentano concetti chiave. Familiarizzare con queste espressioni migliorerà la tua comprensione e capacità di comunicare nel tuo campo.

Trappole Comuni di Pronuncia

Quando si ascolta e si pratica, è importante prestare attenzione a determinate parole e accenti che possono risultare difficili:

  • Termini tecnici: Parole come "repository" e "developer" possono avere pronunce non intuitive per chi sta imparando. Fai attenzione alla corretta articolazione di queste parole durante la pratica di conversazione in inglese.
  • Accento sull'ultima sillaba: Frasi come “you need to know Git” possono essere pronunciate rapidamente, rendendo difficile seguire il ritmo naturale. Esercitarsi con shadow speech può aiutarti a superare questa barriera.
  • Uso del linguaggio colloquiale: Frasi come “you don’t need to worry about this anymore” richiedono attenzione ai suoni, in particolare la contrazione e l'intonazione. L'adozione della tecnica di shadowspeak può migliorare sensibilmente la tua capacità di ripetere frasi in modo naturale e fluido.

Impegnati a migliorare la tua pronuncia inglese attraverso la pratica regolare, utilizzando risorse video che presentano dialoghi autentici e contestualizzati. In questo modo, non solo acquisirai competenze linguistiche, ma anche la sicurezza necessaria per comunicare in ambienti professionali e sociali.

Cos'è la tecnica dello Shadowing?

Shadowing è una tecnica di apprendimento delle lingue supportata da studi scientifici, originariamente sviluppata per la formazione dei traduttori professionisti e resa popolare dal poliglotta Dr. Alexander Arguelles. Il metodo è semplice ma potente: ascolti un audio in inglese di madrelingua e lo ripeti immediatamente ad alta voce — come un'ombra che segue il parlante con un ritardo di solo 1–2 secondi. A differenza dell'ascolto passivo o degli esercizi di grammatica, lo shadowing costringe il tuo cervello e i muscoli della bocca a elaborare e riprodurre simultaneamente i modelli di discorso reale. La ricerca dimostra che migliora significativamente la precisione della pronuncia, l'intonazione, il ritmo, il discorso connesso, la comprensione dell'ascolto e la fluidità del parlato — rendendolo uno dei metodi più efficaci per la preparazione alla prova di speaking dell'IELTS e per la comunicazione reale in inglese.

☕ Offrici un caffè