跟读练习: The unfair way I got good at Leetcode - 通过视频学习英语口语

Lead code is hard, not only because it's hard to be good enough to solve questions, to land a job at high paying companies,

but also because it's hard to know how and exactly where to start when there is so much information available.

When I just got started, I couldn't even solve an easy question well enough to pass an interview.

But I had no choice, so I invested lots of time, I made lots of mistakes, but also learned a lot.

reached out to me on LinkedIn to pass their interviews and receive offers, I realized that back then I wasn't bad.

I was just getting started.

Especially in the beginning, you should put more time into learning solutions rather than solving questions,

so that you start developing intuition within that topic more quickly and then solve questions faster.

So for example, if I'm now starting to learn binary trees, instead of just choosing a list and then trying to solve question by question,

I would make two lists of easy and medium tree questions, starting with the common ones, and then I would separate each list again into two.

and instead of trying to solve the question, I will go to the solution and learn the common solution well.

After doing that, for all of the questions in that list, I will go to the second list and I will start practicing.

When I land on a question that I could not come up with an answer for, it can be a one -off or an outlier,

but when just starting, it usually means that it's a new pattern I was not exposed to, and I will learn that solution and move forward rather than wasting

But give it a try and see

if it also helps you get better at lead code much more efficiently which is what matters

Solving a question during an interview, at least for me, feels more like acting on a stage

and the scene is that you solve a question rather than actually solving a question.

The reason is, is that you don't get to have even 5 minutes to think quietly and sketch some ideas.

You need to entertain the interviewer.

Well, not entertain per se, but you need to keep them engaged.

Share your thought process and walk them through what you're doing.

Your attention is split, which makes it really difficult to think.

When I'm asked in the first few minutes, I either know what the answer is that thanks to something I've solved

that is at least similar or don't and in

that case I just try to get away with asking the interviewer to have time to think

and throw some ideas as they come until I land on something

that might lead to a solution

and usually Interviews will also nudge you towards the right direction

when you voice it So once you have practiced for long enough

so that you're able to solve medium level questions if you stop there need to practice on websites like Pramp,

and start solving these questions when your attention is more split, compared to when you solve questions on your own, and get good at solving technical questions in an interview style.

Although, over time, the more you interview, you will naturally get better at this.

you It's not about quantity alone nor quality alone.

You need both.

Quality means that you follow a roadmap

that exposes you to the most common questions and topics to practice so that you have a sound starting point.

This way you can slowly work your way to expand the spectrum of questions that you can intuitively recognize.

for the types of questions that you will see during the interviews.

For example, I've never been given a question on dynamic programming, whether I interviewed at FANG, a popular startup or a mid -tier paying company.

But I've been given a lot of questions on arrays similar to the common ones but somewhere on trees, backtracking and priority cues.

Something additional I've noticed during the 15 + interviews I've done is

that the more the question you're asked is higher into this pyramid, the more similar it is to common questions in that topic.

So when I was asked the question on trees, it was virtually identical to a common tree question I've thoroughly solved before

which helped me to easily solve the question during the interview.

On the other hand, when the question was seen before.

Even though it was solved using the same pattern from common questions from before, it required more adjustments

which is why sometimes being asked about less common topics can make things easier for you

when you had practiced several such questions.

Make sure that you're not solving questions for the sake of solving questions.

I know it sounds strange but

when I practiced initially I got caught up with all the community trying to learn the best

or fastest solution and so on but I was wasting lots of time.

When you interview, the solution you need is the solution that gets you to pass the interview.

You do it consistently and that's how you land offers.

This rarely means having the shortest solution or an exotic one

than a reasonable common solution that is usually suggested to that question.

When you're interviewing, there will be specific posts and lists, sometimes even for smaller companies, so research and practice these questions that others have posted.

I've seen more than once a question I was asked

which was identical to a question someone else posted on a website like Litcode or Glassdoor.

With some companies, you will have a round with the hiring manager.

That will sometimes be technical but often will also include some of the high -level related does.

When you know you have a round with the hiring manager, do your due diligence about the company and their engineering work,

think about their challenges and things that they had to overcome and weave that in the conversation.

Each time I had a round with the hiring manager, I could see how doing this at some point made me vibe with the hiring manager

and I could see how so long I don't do awfully on the technical questions, I will have the offer.

Finally, get good.

It took me well over a year of practicing each day

with no exceptions to get to a point where I interview pretty well and can pass interviews.

When you start, it's a marathon.

You will most likely also need to practice for a very long time, at least if you're like me, but afterwards, it will be more like a sprint where thanks to all of that practice,

you can recall and can quickly get in an interviewing shape when you need to.

With that said, thank you so much for watching and I hope to see you in the next one.

Bye.

you

✨ 推荐视频

22 句

English Podcast for Easy English Learning | Daily Life Conversation Practice B1- B2 | Education Talk

Business EnglishInterview EnglishDaily Conversation

354 句

How To Learn Any New Skill So Fast It’s Unfair

Business EnglishUniversity StudentsWorking Adults

为什么要通过这个视频练习口语？

通过这个视频练习口语，能够让学习者在真实场景中感受英语表达的节奏与语调。视频中的内容围绕面试技巧展开，强调了在紧张环境下如何有效沟通和思考。这不仅可以提高你的英语口语能力，还帮助你建立在职场内的自信心。当你学习者模仿视频中的讲话方式时，意味着你在深入理解语境和情感，这对提升你的英语水平至关重要。所以，加入这种shadowing site练习吧，让你在看YouTube学英语时大幅提高口语能力。

语法与表达在语境中的应用

视频中使用了多个重要的语法结构和表达方式，这些都对提升你的英语口语大有裨益：

条件句：如“如果我开始学习……”。这种结构常用于假设情境，可以帮助你在讨论方案时更具逻辑性。
被动语态：如“这些问题被问到……”。使用被动语态可以使句子更加正式，适合面试等场合。
进行时态：如“我正在尝试……”。进行时的使用强调正在进行的动作，非常适合表达你此刻的思想。
反义疑问句：如“这个问题很难，不是吗？”这样的句型增强与听者的互动，增加对话的流畅性。

通过分析这些句式，你可以更好理解它们在口语中的运用，提升你的英语表达能力。

常见发音陷阱

在视频中，有一些发音和重音问题需要重点注意：

“interviewer”的发音：许多学习者在发这个单词时可能会不注意重音，使其听起来不够自然。
“question”的发音：注意在快速语速中，该词的元音可能会变得不清晰，影响沟通效果。
连音现象：在一些短语中，比如“to solve a question”，可能因为连音使得语句模糊不清，学习者需要特别注意分隔这些词汇。

克服这些发音陷阱，能帮助你在提高英语发音的同时，听起来更加流利自然。如果你在练习时遇到困难，可以尝试借助shadowspeaks等工具进行针对性提升。

视频中的语法

说话人最常用的结构，并附上视频中的原话：

结构	视频中的用法
被动语态 be + 过去分词 — 强调发生了什么，而不是谁做的	was not exposed · is split · been given
现在完成时 have/has + 过去分词 — 过去发生但与现在仍有关联的事	I've solved · have practiced · I've never been given
定语从句 who / which + 从句 — 补充说明人或事物	efficiently which is · split, which makes

什么是跟读法？

跟读法 (Shadowing) 是一种有科学依据的语言学习技巧，最初开发用于专业口译员的培训，并由多语言者Alexander Arguelles博士普及。这个方法简单而强大：您在听英语母语原声的同时立即大声重复——就像是一个延迟1-2秒紧跟说话者的影子。与被动听力或语法练习不同，跟读法强迫您的大脑和口腔肌肉同时处理并模仿真实的讲话模式。研究表明它能显着提高发音准确性，语调，节奏，连读，听力理解和口语流利度——使其成为雅思口语备考和真实英语交流最有效的方法之一。

影子跟读法: 阅读完整分步指南 →

跟读练习: The unfair way I got good at Leetcode - 通过视频学习英语口语

I'm an ex-Google interviewer. You're doing LeetCode wrong.

I cloned 3 apps and now make $35K/month

How To Land Your First Junior Dev Role

Walk Me Through Your Resume: How to Answer

Interview Question: “What Are Your Weaknesses?” And You Say, “...”

Ace every UX/UI design interview like THIS

How To Speak Like A Billion-Dollar CEO

Googleyness and Leadership Interview Question

My Entire Job Search Process: Software Engineer Resume & Interviews

Fight brain-rot with Worked Examples