Pratica di Shadowing: Creator of C# and TypeScript: "AI will NEVER Replace Coders, Here's Why" | Anders Hejlsberg - Impara a parlare inglese con YouTube
B2
Will AI replace software engineers?
216 frasi
Se le frasi sono troppo corte o troppo lunghe, clicca su Edit per modificarle.
1
Will AI replace software engineers?
2
I am highly skeptical.
3
Who's going to make the AI?
4
AI is not going to innovate.
5
Someone has to design the CPU, the operating system.
6
AI is not going to do that.
7
What are your opinions on vibe coding?
8
That doesn't really bring a lot to the table anyway.
9
That code has to come from somewhere.
10
It's not all going to be generated by AI.
11
When people are learning to code, what are some common mistakes you see people make?
12
Not spending enough time.
13
.
14
How this industry makes progress.
15
What was the story of you creating C Sharp?
16
Well the story probably starts like with my Today I'm sitting down with Anders Halsberg, a technical fellow at Microsoft, to talk about the future of coding and AI.
17
If you're in computer science or are a tech beginner, you need to pay attention.
18
Because Anders is not just a tech leader, but he is the literal creator of programming languages C sharp and TypeScript.
19
And so when he talks about AI and coding, he is speaking from decades worth of experience.
20
And he dispels a lot of the lies and nonsense people have been spewing about AI.
21
Plus, if you want to succeed and actually get ahead of most developers, he shares some crazy behind-the-scenes stories from building C Sharp and TypeScript,
22
and I am confident that will change the way you think about coding projects going into the future.
23
So a lot of value to unpack in this video, and let's get to it right away.
24
In the world of AI that we live in today, a lot of people are even questioning, is it worth learning how to code?
25
Oh, I absolutely think it's worth learning how to code.
26
Programming languages and code is how AI expresses itself.
27
And there's a whole different world from AI below
28
that has to exist that AI assumes the existence of in the code that it generates.
29
That code has to come from somewhere.
30
It's not all going to be generated by AI.
31
What are your opinions on Vibe coding is going to replace coders?
32
I am highly skeptical.
33
For a lot of stuff that is rote, how many times can you write this to-do list app?
34
AI in its training set has seen it a gazillion times, so it can riff over that.
35
And it can actually get more and more creative now.
36
But when it comes down to business logic or you've got to invent something, that's how this industry makes progress, right?
37
That's not going to come from AI.
38
True, true.
39
Like understanding the fundamentals.
40
Yesterday, I got the opportunity to have a quick chat with Satya.
41
I had asked him beginner level skills people need to know when they're getting into tech.
42
He mentioned understanding the architecture.
43
That's something AI can help you generate the code, but it won't do the fundamental design, which comes from the human mind.
44
And you designed languages such as C-sharp and TypeScript, and were very cognizant what problems you were trying to solve.
45
Rewinding the clock a little bit, what was the story of you creating C Sharp?
46
Well, the story probably starts like with my previous endeavor there at a company called Borland, where I wrote Turbo Pascal and then worked also as the architect of a product called Delphi.
47
This was all about making programmers more productive, rapid application development, and we competed with Microsoft's marquee product, Visual Basic.
48
Right.
49
And, you know, if you can't beat them, join them.
50
So I joined Microsoft in 96.
51
There was this thing called Visual Basic that was super easy to write apps in.
52
And then there was this thing called C++ that is where all the expressiveness and performance was available.
53
And people really wanted a little bit of both.
54
And so we set out to create that sort of best of both worlds, the best of both worlds, you know, something that gave you the power and expressiveness of C++,
55
but with the ease of use of Visual Basic.
56
With a bunch of modern infrastructure behind it, called .NET.
57
Are there any examples of features of the language that did both so you could explain to us?
58
Things like properties and events.
59
There were object-oriented programming languages already, but everyone was working with this notion of properties on their objects and events on their objects.
60
But no programming languages had given first-class treatment to them before.
61
Do you have any example of a great project to create with C-sharp?
62
Any kind of web backend or REST API or write a game.
63
I mean, like Unity, right?
64
Like a third of the world's C-sharp programmers write games.
65
It almost doesn't matter what you write.
66
Once you start writing code, you start understanding how programming languages work and how to build data structures and how to get performance, how to measure performance.
67
When you're learning, it's less important exactly what you write, but just the fact that you're writing.
68
You could go write a framework or set a collection classes if you wanted to, it doesn't matter.
69
Yeah, and did you think that C Sharp would be as big as it got to today?
70
No, of course not.
71
You never know, right?
72
I mean, and yes, C Sharp, I am very proud that it stood the test of time.
73
In fact, I was talking to someone earlier today
74
that it's 25 years since we released C Sharp at the 2000 Professional Developers Conference.
75
So 25 years, that's a long time for something to still be around and in widespread use.
76
Fast forwarding a little into your journey.
77
So TypeScript, right?
78
Can you give us the story of that and what problem you were trying to solve?
79
Really quick, as a software engineer, you would think writing code is what slows me down.
80
But it's actually the small tasks that pile up the most.
81
That's when I started using Superhuman Mail, which manages my inbox and keeps me organized without all the back and forth.
82
And now I can connect it to tools like ChatGPT or Claude and actually manage my inbox from there.
83
Let your AI agents run your inbox and calendar.
84
Let me show you how I use this.
85
I connected Superhuman Mail to Claude, and now I can run everything from here.
86
One thing I use a lot is cross-tool workflows.
87
For example, I can ask it to look through recent emails and summarize anything important, then send that straight into Slack.
88
Or after meetings, I can have a draft of follow-ups based on my notes without opening my inbox.
89
It removes a lot of the small tasks that usually add up.
90
If you're afraid of your email sounding too AI-generated, you can insert rules just using no em dashes
91
or ellipses to ensure you're all good to go and that it is in your tone of voice.
92
The beauty is these rules will apply every time without having to edit each time to match your voice and tone.
93
The biggest game changer for me was the AI to help me actually prepare for the day.
94
It can collect all the tasks and insights that I have and help me create a to-do list.
95
Set it up once and stay in control all year.
96
Sign up for a superhuman mail today and get one month free with my link.
97
Make sure to sign up for the business plan if you want to connect CLAW, ChatGPT, and other AI tools.
98
And now back to the video.
99
Well, Timescript, the story probably starts about 15 years ago when a team at Microsoft, the Outlook team, came to us, and I was doing C Sharp at the time,
100
and they came to us and they asked, hey, could you guys productize this thing called Script Sharp?
101
And I'm like, what's Script Sharp?
102
Well, it's this thing that takes C Sharp and cross compiles it to JavaScript.
103
Okay.
104
And I'm like, okay.
105
And why would someone want to do that?
106
Well, we do that because that's the only way that we can get great tooling and scalability for a large project.
107
And we're writing this enormous app in JavaScript because at the time,
108
everyone was moving to the browser and JavaScript as the true cross-platform solution.
109
You know, there was like a whole diversity of device form factors coming out like phones and tablets and the PC wasn't,
110
you couldn't just assume that it was going to run on a PC.
111
And so browser was it.
112
And HTML5 had happened and you could actually write decent UI, right?
113
And so people were just writing enormous apps in JavaScript and having a very hard time doing it.
114
And this team had chosen to solve the problem by writing the app in C Sharp and cross-compiling it to JavaScript.
115
And I'm like, but that's crazy.
116
Surely you're not going to write best of breed JavaScript apps by writing them in C Sharp.
117
Wouldn't you rather write them in JavaScript? what is it about JavaScript that's broken and can we fix it?
118
And so that was sort of the genesis of TypeScript, fixed JavaScript, if you will.
119
Make it usable for large scale projects and add those things to the language
120
that are necessary such that we can build great tooling on top.
121
And in particular, that meant adding a static type system to the language.
122
We then enable the ability to write great tool that you see in say, Visual Studio Code and our language.
123
So more like the developer experience exactly
124
because that's ultimately where the productivity comes from right it's like having things like statement completion
125
and code navigation and seeing red squigglies when you make a mistake
126
and whatever that's what developers love
127
that stuff yeah once you give it to them you can never take it away again yeah
128
so python developers might disagree slightly but well they might
129
but you know what i don't know that people are writing million line apps or programs in Python to the same extent.
130
Once something gets big enough, you really do need these things.
131
That readability in TypeScript.
132
Yeah.
133
As the creator of C-sharp and TypeScript, when people are learning to code, what are some common mistakes you see people make?
134
Not spending enough time learning the basic principles and really sort of understand what is it I'm doing?
135
What is a variable really?
136
And what is an array?
137
And what is a data structure?
138
And how do pointers work?
139
Once you grok
140
that, then it doesn't really matter what language you're in you
141
know that's just a veneer on top of the semantics right
142
but really understanding the semantics is super important because
143
that allows you to think in a more abstract fashion
144
if you don't get that deeper understanding of it then you're sort of thinking at
145
that veneer syntactic level of what do i have to write
146
but you're not really understanding why you're writing it interesting
147
if i'm a beginner in tech and i wanted to get hired at a big tech a company like Microsoft, what is your number one piece of advice?
148
Write a bunch of open source code, put it on GitHub, that becomes your resume.
149
There's nothing like demonstrating the ability to code.
150
And a fantastic way to demonstrate that is by building stuff and putting it out in the open.
151
Yeah.
152
So don't sit on it, share it.
153
Yeah.
154
And particularly with AI in the world that we live in, are there certain problems that you would choose to tackle?
155
It depends on what kind of programming excites you, because there are many different things you could do.
156
Some people like building apps, the UI aspect of it
157
and the experience of the app other people like systems like stuff
158
that doesn't have a ui at all or
159
but it's like they're into making it perform incredibly well
160
and you know that some people like the theory of it all right and
161
so there are many different ways you can dive into it
162
i mean for me i've always been fascinated with writing efficient data structures
163
and understanding how they work how does a hash table work?
164
Why does it work?
165
And how do I make it more efficient?
166
How can I structure the data in my program the right way?
167
Because ultimately, that's where the performance comes from.
168
Right, right.
169
Exactly.
170
Exactly.
171
It's like the small design choices that affect so much.
172
And do you think a computer science degree is worth it?
173
Oh, I definitely think so.
174
You know, I was sort of somewhat self-taught because at the time I went to college back in Denmark, I grew up in Denmark,
175
The engineering school I went to didn't even have computer science yet.
176
They started it the following year, right?
177
But I was like in the late 70s.
178
You could go to the other university for computer science, but I was doing engineering.
179
And so a lot of things I sort of had to learn by myself by doing.
180
Boy, I could have saved a lot of time by getting an education
181
that allows you to understand like the history of programming.
182
And like we've talked about here, like what is a programming language?
183
What are the principles of programming?
184
What is data structures?
185
What are databases?
186
What are operating systems? like all of this stuff it certainly
187
helps to have a passion for it you know for me i sometimes joke i never had a real job
188
because i was always doing my hobby coding was always my hobby right then i was fortunate yeah
189
if you aim to do your best work you there's got
190
to be a bit of passion in it you know right for sure
191
and one final question will ai replace software engineers no who's gonna make the AI, right?
192
And who's going to make the programming languages that the AI expresses itself in?
193
And who's going to write the frameworks that the AI talk?
194
I mean, no, AI is an accelerant and it's going to change the way that we do things.
195
And it's going to remove a lot of grunt work
196
that we don't need to do anymore because AI can help us do it, but it'll allow us to focus more on the creative side because AI is not going to innovate.
197
It's not going to like, Bing, have this crazy idea I had in the shower this morning, you know, AI doesn't work that way.
198
Right, right.
199
So right now, as a software engineer, we code five years from now when AI is more into the workflow.
200
More pervasive.
201
What do you see software engineers do?
202
AI will be able to do a lot of that grunt work.
203
But like I said, there's still the deeper side of the science.
204
These frameworks that you have to target, someone has to design the CPU, someone has to design the operating systems.
205
There's plenty left.
206
Someone has to get the right idea
207
and devise the right data structure for sharding this app so our startup can grow fast or what have you, right?
208
AI is not going to do that, but it's going to help you with these like, yeah, okay, the grunt work of writing a test for a pull request is fine.
209
That doesn't really bring a lot to the table anyway.
210
So yeah, hand that off.
211
Sweet.
212
Well, that's about all I have in this video.
213
I really hope that you guys enjoyed it.
214
And if you did, make sure to hit the like button and subscribe if you haven't already.
215
If you're interested in my absolutely free tech newsletter, link for that down below in the description.
216
And if you're interested in watching the conversation I had with the CEO of Microsoft, Satya Nadella, you might want to click right here.
Scarica l'app
Valutazione AI per ogni frase che pronunci
TRENDING
Popolari
Di Questo Insegnamento
In questa lezione, avrai l'opportunità di esplorare il dialogo tra il creatore delle lingue di programmazione C# e TypeScript, Anders Hejlsberg, riguardo al futuro della programmazione e all'intelligenza artificiale (AI). Imparerai concetti chiave sulla programmazione, il valore di apprendere a codificare e le common mistakes che i principianti tendono a fare. Questo non solo ti aiuterà a migliorare la tua comprensione del linguaggio tecnico, ma ti fornirà anche l'opportunità di esercitarti nella pronuncia e nella fluidità attraverso il metodo del shadow speaking.
Vocabolario Chiave & Frasi
- AI (Intelligenza Artificiale): Un sistema che imita l'intelligenza umana per svolgere compiti specifici.
- Codificare: Il processo di scrittura di istruzioni per un computer.
- Business logic: Le regole che determinano il comportamento degli affari in un'applicazione.
- Vibe coding: Un termine usato per descrivere un approccio meno formale alla codifica.
- Architettura del software: La struttura fondamentale di un sistema informatico.
- Productività del programmatore: L'efficacia e l'efficienza con cui un programmatore completa le sue attività.
- Rapid application development: Una metodologia per sviluppare software rapidamente.
Consigli per la Pratica
Per ottenere il massimo dal tuo esercizio di shadowing con questo video, segui questi consigli:
- Ascolta attentamente il video: Fai attenzione sia al contenuto che alla pronuncia di Anders Hejlsberg per cogliere le sfumature del linguaggio tecnico.
- Ripeti ad alta voce: Utilizza il metodo del shadowspeak per imitare non solo le parole ma anche il ritmo e l'intonazione. Questo ti aiuterà a migliorare la pronuncia inglese.
- Fermati e riascolta: Se non riesci a seguire a causa della velocità, non esitare a mettere in pausa e riprodurre nuovamente parti del dialogo per affinare la tua comprensione.
- Prendi appunti: Scrivi le frasi o i termini più difficili e esercitati a ripeterli. Questo è particolarmente utile per memorizzare il vocabolario tecnico specifico.
- Utilizza risorse di shadowing online: Cerca altre fonti che offrono esercizi di shadow speaker, in modo da praticare non solo qui, ma anche su diverse piattaforme per un'esperienza completa.
Incorporare esercizi di shadowing nella tua routine di studio può fare una grande differenza nella tua fluidità e nella tua fiducia nel parlare inglese, soprattutto se ti concentri su argomenti rilevanti e motivanti come la programmazione e la tecnologia.
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è
ShadowingEnglish rimane gratuito al 100% grazie al tuo supporto. I costi del server e IA sono elevati — il tuo caffè ci aiuta ad andare avanti! 🙏