Prática de Shadowing: Learning Software Engineering During the Era of AI | Raymond Fu | TEDxCSTU - Aprenda a falar inglês com o YouTube

Difícil

Controles de Shadowing

0% concluído (0/128 frases)

Transcriber: Brenda Meza Reviewer: Emilia Soso At the turn of the century, when I started to learn software engineering, one of my professors told us that in the future, every job will be a programming job.

⏸ Pausado

Velocidade:

Nº de repetições:

Modo de espera:

Sinc. legendas:0ms

Todas as frases

128 frases

0:00.00 – 0:17.23 (17.2s)

That was in 2001.

0:17.46 – 0:18.86 (1.4s)

And he said that we’re holding a golden ticket to job security.

0:19.66 – 0:24.06 (4.4s)

Just last month, the CEO of GitHub said that the future of programming is natural language.

0:24.86 – 0:32.43 (7.6s)

It looks like the prediction of my professor at the turn of the century is going to become true, but probably not in the way that he had imagined.

0:34.00 – 0:42.36 (8.4s)

Artificial intelligence is capable of writing code for you through a natural language prompt.

0:43.20 – 0:48.90 (5.7s)

GitHub Copilot can complete code for you and fix bugs for you.

0:49.26 – 0:54.23 (5.0s)

And ChatGPT can create an entire project for you within seconds.

0:54.66 – 0:59.40 (4.7s)

And all these tools are available to anyone.

0:59.93 – 1:02.76 (2.8s)

So I find myself wondering, have we lost our golden tickets to job security?

1:03.66 – 1:08.63 (5.0s)

And as a CSTU professor and a father to a daughter who studied Computer Science, there's a bigger question for me.

1:09.63 – 1:17.90 (8.3s)

If AI is going to do programming, is it still worth it for us to learn software engineering anymore?

1:18.60 – 1:25.10 (6.5s)

Today, I would like to explore this question with all of you guys.

1:26.70 – 1:30.26 (3.6s)

Let’s talk about what AI can do and more importantly, how our students of software engineering can prepare for the future roles of a real software engineer.

1:30.43 – 1:41.76 (11.3s)

So let’s dive in.

1:42.20 – 1:43.33 (1.1s)

First, let’s talk about what AI is good at.

1:43.76 – 1:46.43 (2.7s)

In terms of programming, AI is really good at generating thousands of lines of code.

1:47.70 – 1:53.40 (5.7s)

It translates between programming languages.

1:53.70 – 1:56.20 (2.5s)

It can create user interfaces and fix bugs for you.

1:56.40 – 2:01.23 (4.8s)

And it excels at repetitive tasks, and, you know, pattern recognition.

2:02.06 – 2:06.96 (4.9s)

You know, once I asked ChatGPT to create a project for me, a dating app like Tinder in Python.

2:07.93 – 2:14.70 (6.8s)

And within seconds it actually created a complete application with user profiles, the swiping logic, and even a sample database.

2:15.30 – 2:24.16 (8.9s)

The only thing it didn't do for me is find me a date.

2:24.83 – 2:27.90 (3.1s)

(Laughs) But AI has a lot of limitations. We have to accept that.

2:28.36 – 2:33.56 (5.2s)

It still doesn’t understand the why behind all the tasks we ask them to do.

2:33.73 – 2:37.83 (4.1s)

It needs your human input for real-world context and scenarios.

2:38.16 – 2:44.23 (6.1s)

It may not work well, prioritizing long-term business goals and assessing trade-offs.

2:44.73 – 2:50.66 (5.9s)

And last but not least, it's not reliable.

2:51.30 – 2:54.46 (3.2s)

It hallucinates and sometimes gives the wrong answer.

2:55.16 – 2:58.46 (3.3s)

The statistics say that 55% of the developers today are actually starting to use Copilot, but only 30% of them are accepting the outcome without any changes.

3:00.50 – 3:12.36 (11.9s)

So if you are a developer and you are not in the first 55%, that means you’re not using AI, and you’re in trouble.

3:12.36 – 3:20.00 (7.6s)

But if you are in the 30%, that means you trust AI too much.

3:20.60 – 3:25.16 (4.6s)

You may be in bigger trouble.

3:25.33 – 3:27.26 (1.9s)

So all the leading AIs today are built on top of large language models, and it’s trained on the text of human knowledge.

3:29.50 – 3:37.36 (7.9s)

It’s impressive.

3:37.70 – 3:38.70 (1.0s)

If you give a clear prompt, it’ll give you very good results.

3:38.70 – 3:42.50 (3.8s)

But all the strategic thinking are still us. It’s the human.

3:42.86 – 3:47.20 (4.3s)

You can think of AI as a brilliant junior developer that you hire to your team, and they can do a lot of jobs very quickly and efficiently.

3:47.46 – 3:57.93 (10.5s)

But it's up to us human to define the vision, to validate the results and ensure what we're building is good for the society.

3:58.26 – 4:08.10 (9.8s)

So there’s another thing that I want to talk about that AI is struggling with.

4:09.76 – 4:14.36 (4.6s)

It's struggling to communicate and collaborate with human beings.

4:14.56 – 4:18.80 (4.2s)

Well, maybe you will say this is more of a human problem, right?

4:19.63 – 4:23.30 (3.7s)

We humans sometimes deal with the same problem too.

4:23.46 – 4:26.26 (2.8s)

But this is something we will have to work out.

4:26.80 – 4:29.56 (2.8s)

Let AI do what AI is good at, and we humans can take care of the boring jobs such as handling office politics.

4:29.56 – 4:37.80 (8.2s)

So talk about the capabilities and limitations of AI.

4:38.63 – 4:42.80 (4.2s)

Now we can take a look at the software engineering roles.

4:43.20 – 4:46.33 (3.1s)

So software engineering roles is not just about writing code.

4:47.66 – 4:52.10 (4.4s)

It actually is about how we need to understand what the user needs.

4:52.10 – 4:57.26 (5.2s)

We need to collaborate across roles and also make tough decisions with empathy and responsibility.

4:57.26 – 5:04.70 (7.4s)

This is what a software engineer should be doing, right?

5:04.90 – 5:07.90 (3.0s)

We're not just text executors.

5:07.90 – 5:09.60 (1.7s)

The best engineers are not the ones who code the fastest, but the ones who think the deepest.

5:10.66 – 5:15.80 (5.1s)

So a good engineer will take messy problems, ambiguous problems, and guide machines towards structured and meaningful outcomes.

5:17.16 – 5:26.26 (9.1s)

So there are system architects who design the best solutions, and they should be the AI collaborators who use AI to implement those solutions.

5:27.00 – 5:38.16 (11.2s)

And then they need to be ethical technologists to make sure the solutions that we’re building are truly benefiting human beings.

5:38.76 – 5:46.96 (8.2s)

So AI is actually democratizing a lot of complicated technical tasks.

5:47.96 – 5:52.93 (5.0s)

Like, today a designer can mock up an application with a prompt.

5:52.96 – 5:59.73 (6.8s)

And also marketers, they don’t need data engineers.

6:00.03 – 6:03.13 (3.1s)

They can just run data analytics without writing any code.

6:03.13 – 6:07.73 (4.6s)

Does that mean software engineers are losing advantages?

6:08.43 – 6:11.73 (3.3s)

The answer is no.

6:12.43 – 6:13.56 (1.1s)

It still remains essential for software engineers.

6:15.63 – 6:18.83 (3.2s)

And the reason is as follows.

6:18.83 – 6:21.20 (2.4s)

First, we understand AI better.

6:22.13 – 6:25.30 (3.2s)

We not only know how to prompt, and we also know what’s under the hood.

6:25.80 – 6:30.10 (4.3s)

The models, the data pipelines, the limitations and risks.

6:30.46 – 6:34.76 (4.3s)

And the understanding of these are very important because AI is integrated into every product we’re using and we’re building in the future.

6:35.50 – 6:44.36 (8.9s)

Second, we can make better use of AI when building software.

6:44.66 – 6:48.80 (4.1s)

So nowadays anybody can prototype a demo or create a simple application of features.

6:49.40 – 6:55.83 (6.4s)

But software engineers think of the bigger picture.

6:56.30 – 6:59.06 (2.8s)

We are actually using AI to build a production-ready software that’s scalable and reliable with long-term maintainability.

6:59.70 – 7:08.46 (8.8s)

Finally, we are making AI better.

7:09.83 – 7:12.56 (2.7s)

We fine-tune models.

7:13.00 – 7:14.53 (1.5s)

We optimize the performance and improve usability.

7:14.53 – 7:18.66 (4.1s)

We make AI available and useful for everybody else.

7:19.10 – 7:22.96 (3.9s)

The next generation of AI is still built by software engineers.

7:23.46 – 7:27.16 (3.7s)

Do you guys remember this quote from CEO of GitHub?

7:27.96 – 7:31.13 (3.2s)

This is not a reality yet.

7:31.66 – 7:33.50 (1.8s)

It's still up to the software engineers to improve AI and make this happen.

7:33.53 – 7:39.70 (6.2s)

So software engineers were not losing the golden ticket to job security.

7:41.53 – 7:46.26 (4.7s)

As a matter of fact, we’re collecting even more because we’re no longer just building software.

7:46.53 – 7:51.16 (4.6s)

We're actually building the future intelligence itself.

7:51.36 – 7:55.06 (3.7s)

And how we train, direct and supervise AI today will define the kind of systems, technology and society that we’re building tomorrow.

7:57.13 – 8:08.43 (11.3s)

AI is raising the floor, but software engineers are raising the ceiling.

8:10.23 – 8:15.06 (4.8s)

And I want to share this not just with… You can applaud, that’s okay.

8:15.86 – 8:19.50 (3.6s)

I want to share this with not just system engineers.

8:19.63 – 8:22.66 (3.0s)

This is for everyone, all right?

8:22.66 – 8:24.30 (1.6s)

We have AI that’s raising us up from the floor.

8:24.33 – 8:26.76 (2.4s)

But it’s us humans that have to reach to the ceiling and raise up the ceiling.

8:26.76 – 8:31.56 (4.8s)

All right, so after all this, now we can talk about software engineering education, right.

8:32.96 – 8:37.73 (4.8s)

So, in the past, coding was a very important piece of software engineering education.

8:37.73 – 8:42.86 (5.1s)

But software engineering education is not just about writing code.

8:42.86 – 8:46.53 (3.7s)

It's also about teaching you how to break complex problems into steps, think logically and critically, and harness the digital tools to build solutions that really matters.

8:46.53 – 8:58.30 (11.8s)

So in a time when AI is everybody’s assistant, engineers become the orchestrators.

8:59.33 – 9:06.66 (7.3s)

We remove barriers and open doors.

9:07.03 – 9:10.30 (3.3s)

And in order for us to be a successful software engineer, the students should go beyond learning code as quickly as possible and get into the following things.

9:11.56 – 9:22.40 (10.8s)

So in order to become a successful engineer in the future, we should focus on mastering the foundations.

9:24.26 – 9:29.90 (5.6s)

The data structure, the algorithm, the programming concepts.

9:30.50 – 9:33.53 (3.0s)

100

They are still very important.

9:33.53 – 9:34.96 (1.4s)

101

Spend enough time to learn all these and become an expert on them because they’re very important basics.

9:34.96 – 9:41.86 (6.9s)

102

Next, think about a system like an architect because, you know, aim higher.

9:42.80 – 9:49.53 (6.7s)

103

Meet the expectation of a senior engineer as soon as possible.

9:49.96 – 9:53.60 (3.6s)

104

And think about designing systems that are reliable and scalable.

9:53.60 – 9:58.03 (4.4s)

105

Go beyond, go full-stack across disciplines.

9:59.83 – 10:03.43 (3.6s)

106

The days when a software engineer could focus on either the front end or the back end or the database are gone.

10:04.00 – 10:11.53 (7.5s)

107

The future software engineers are full-stack engineers.

10:11.86 – 10:14.76 (2.9s)

108

And there’s more.

10:15.13 – 10:16.13 (1.0s)

109

You need to also get into the other disciplines like design, product, data, project management, and be prepared to wear multiple hats.

10:16.23 – 10:23.76 (7.5s)

110

Practice communication and collaborations.

10:25.33 – 10:28.40 (3.1s)

111

Learn to work with people through team projects.

10:28.80 – 10:33.03 (4.2s)

112

Because in the future, if you can explain and connect, it will become increasingly important, and it will set you apart.

10:33.43 – 10:42.83 (9.4s)

113

Use AI as a creative partner.

10:44.56 – 10:46.56 (2.0s)

114

Embrace AI, don’t hate it.

10:47.16 – 10:49.13 (2.0s)

115

And learn LLM, generative AI, model fine-tuning and RAG, etc.

10:49.53 – 10:56.06 (6.5s)

116

You discuss your project with AI, and delegate your work to AI as if it’s one of your teammates.

10:56.76 – 11:02.46 (5.7s)

117

Last but not least, stay adaptable.

11:03.86 – 11:06.33 (2.5s)

118

Tools change, principles last.

11:06.96 – 11:09.80 (2.8s)

119

So you should always focus on learning how to learn.

11:10.46 – 11:13.83 (3.4s)

120

So in the future, when everyone can code a little, the ones who can master the craft, will build the path for everyone and become the leader.

11:15.20 – 11:25.26 (10.1s)

121

So in the era of AI, software engineering is becoming the foundation of leadership.

11:26.00 – 11:32.06 (6.1s)

122

I've talked a lot about programming, but perhaps programmer is no longer the right term we should be using to refer to software engineers.

11:34.60 – 11:41.60 (7.0s)

123

The software engineers of the AI era should be visionaries who can define meaningful problems.

11:42.20 – 11:50.33 (8.1s)

124

A bridge builder who can connect tools, teams and disciplines, and leaders who not only lead human beings, but also lead AI.

11:50.70 – 12:01.00 (10.3s)

125

So the future doesn't belong to those who code the fastest, it should belong to the ones who think deeply, adapt quickly, and collaborate efficiently.

12:01.96 – 12:12.70 (10.7s)

126

They are the ones who don't just predict the future.

12:13.30 – 12:16.16 (2.9s)

127

We build the future.

12:16.66 – 12:17.90 (1.2s)

128

Thank you.

12:19.26 – 12:20.26 (1.0s)

O que é a Técnica de Shadowing?

Shadowing é uma técnica de aprendizado de idiomas com base científica, originalmente desenvolvida para o treinamento de intérpretes profissionais. O método é simples, mas poderoso: você ouve áudio em inglês nativo e repete imediatamente em voz alta — como uma sombra seguindo o falante com 1-2 segundos de atraso. Pesquisas mostram melhora significativa na precisão da pronúncia, entonação, ritmo, sons conectados, compreensão auditiva e fluência na fala.

Como praticar de forma eficaz no ShadowingEnglish

Escolha seu vídeo: Escolha um vídeo do YouTube com inglês claro e natural. TED Talks, BBC News, cenas de filmes, podcasts — todos funcionam bem. Cole a URL na barra de pesquisa.
Ouça primeiro, entenda o contexto: Na primeira vez, mantenha a velocidade em 1x e apenas ouça. Não tente repetir ainda. Concentre-se em entender o significado.
Configure o modo Shadowing:
- Modo de espera: Escolha +3s ou +5s — após cada frase, o vídeo pausa automaticamente para você repetir.
- Sinc. legendas: Legendas do YouTube às vezes estão adiantadas ou atrasadas. Use ±100ms para alinhar.
Faça Shadowing em voz alta (a prática principal): Assim que a frase tocar — ou durante a pausa — repita em voz alta, clara e confiante. Imite o ritmo, ênfase, tom e sons conectados do falante.
Aumente o desafio: Quando um trecho ficar confortável, aumente a velocidade para <code>1.25x</code> ou <code>1.5x</code>. Pratique 15-30 minutos por dia para resultados visíveis em poucas semanas.

☕ Pague-nos um café

O ShadowingEnglish permanece 100% gratuito graças ao seu apoio. Os custos de servidor e IA são altos — seu café nos mantém ativos! 🙏

Doar via PayPal

ShadowingEnglish.com – Prática de Shadowing em Inglês

Fale inglês fluentemente usando a técnica de Shadowing. Ouça vídeos nativos do YouTube, repita frase por frase e desenvolva pronúncia e fluência reais — usado por estudantes de IELTS no mundo todo.

Prática de Shadowing: Learning Software Engineering During the Era of AI | Raymond Fu | TEDxCSTU - Aprenda a falar inglês com o YouTube

Contexto & Antecedentes

As 5 Principais Frases para Comunicação Diária

Guia Passo a Passo de Shadowing

O que é a Técnica de Shadowing?

Como praticar de forma eficaz no ShadowingEnglish