跟讀練習: The unfair way I got good at Leetcode - 通過影片學習英語口語
選擇練習模式
每種模式都會開啟全屏練習室。
75 句
如果句子過短或過長，請點選 Edit 進行調整。
1
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,
2
but also because it's hard to know how and exactly where to start when there is so much information available.
3
When I just got started, I couldn't even solve an easy question well enough to pass an interview.
4
But I had no choice, so I invested lots of time, I made lots of mistakes, but also learned a lot.
5
reached out to me on LinkedIn to pass their interviews and receive offers, I realized that back then I wasn't bad.
6
I was just getting started.
7
Especially in the beginning, you should put more time into learning solutions rather than solving questions,
8
so that you start developing intuition within that topic more quickly and then solve questions faster.
9
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,
10
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.
11
and instead of trying to solve the question, I will go to the solution and learn the common solution well.
12
After doing that, for all of the questions in that list, I will go to the second list and I will start practicing.
13
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,
14
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
15
But give it a try and see
16
if it also helps you get better at lead code much more efficiently which is what matters
17
Solving a question during an interview, at least for me, feels more like acting on a stage
18
and the scene is that you solve a question rather than actually solving a question.
19
The reason is, is that you don't get to have even 5 minutes to think quietly and sketch some ideas.
20
You need to entertain the interviewer.
21
Well, not entertain per se, but you need to keep them engaged.
22
Share your thought process and walk them through what you're doing.
23
Your attention is split, which makes it really difficult to think.
24
When I'm asked in the first few minutes, I either know what the answer is that thanks to something I've solved
25
that is at least similar or don't and in
26
that case I just try to get away with asking the interviewer to have time to think
27
and throw some ideas as they come until I land on something
28
that might lead to a solution
29
and usually Interviews will also nudge you towards the right direction
30
when you voice it So once you have practiced for long enough
31
so that you're able to solve medium level questions if you stop there need to practice on websites like Pramp,
32
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.
33
Although, over time, the more you interview, you will naturally get better at this.
34
you It's not about quantity alone nor quality alone.
35
You need both.
36
Quality means that you follow a roadmap
37
that exposes you to the most common questions and topics to practice so that you have a sound starting point.
38
This way you can slowly work your way to expand the spectrum of questions that you can intuitively recognize.
39
for the types of questions that you will see during the interviews.
40
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.
41
But I've been given a lot of questions on arrays similar to the common ones but somewhere on trees, backtracking and priority cues.
42
Something additional I've noticed during the 15 + interviews I've done is
43
that the more the question you're asked is higher into this pyramid, the more similar it is to common questions in that topic.
44
So when I was asked the question on trees, it was virtually identical to a common tree question I've thoroughly solved before
45
which helped me to easily solve the question during the interview.
46
On the other hand, when the question was seen before.
47
Even though it was solved using the same pattern from common questions from before, it required more adjustments
48
which is why sometimes being asked about less common topics can make things easier for you
49
when you had practiced several such questions.
50
Make sure that you're not solving questions for the sake of solving questions.
51
I know it sounds strange but
52
when I practiced initially I got caught up with all the community trying to learn the best
53
or fastest solution and so on but I was wasting lots of time.
54
When you interview, the solution you need is the solution that gets you to pass the interview.
55
You do it consistently and that's how you land offers.
56
This rarely means having the shortest solution or an exotic one
57
than a reasonable common solution that is usually suggested to that question.
58
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.
59
I've seen more than once a question I was asked
60
which was identical to a question someone else posted on a website like Litcode or Glassdoor.
61
With some companies, you will have a round with the hiring manager.
62
That will sometimes be technical but often will also include some of the high -level related does.
63
When you know you have a round with the hiring manager, do your due diligence about the company and their engineering work,
64
think about their challenges and things that they had to overcome and weave that in the conversation.
65
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
66
and I could see how so long I don't do awfully on the technical questions, I will have the offer.
67
Finally, get good.
68
It took me well over a year of practicing each day
69
with no exceptions to get to a point where I interview pretty well and can pass interviews.
70
When you start, it's a marathon.
71
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,
72
you can recall and can quickly get in an interviewing shape when you need to.
73
With that said, thank you so much for watching and I hope to see you in the next one.
74
Bye.
75
you
FOR YOU
推薦影片
B21
22 句
I'm an ex-Google interviewer. You're doing LeetCode wrong.
Business EnglishInterview EnglishUniversity Students
B267
15 句
Unlock Your Potential: Storytelling Beats Generic Answers #shorts
American AccentBusiness EnglishInterview EnglishUniversity Students
B21
405 句
Answering behavioral interview questions is shockingly uncomplicated
Interview EnglishUniversity StudentsWorking Adults
B26
35 句
Steven Bartlett’s Secret To Business Success (Hint: It’s Not Hard Work)
Business EnglishInterview EnglishUniversity Students
B21
72 句
Fight brain-rot with Worked Examples
Daily ConversationUniversity StudentsWorking Adults
B24
233 句
How to Think 10 Steps Ahead In Any High Stakes Conversation
Business EnglishInterview EnglishUniversity Students
B211
89 句
The Art Of Winning In Tech
Business EnglishInterview EnglishUniversity Students
B26
67 句
How to Ace an Interview: 5 Tips from a Harvard Career Advisor
Interview EnglishUniversity StudentsWorking Adults
B23
183 句
I Learned More English in 24 Hours Than in 6 Months of Studying
Interview EnglishDaily ConversationUniversity Students
B25
218 句
My Entire Job Search Process: Software Engineer Resume & Interviews
Business EnglishInterview EnglishUniversity Students
B212
72 句
Why Are You a Good Fit for this Role - How to Answer
American AccentBusiness EnglishInterview EnglishUniversity Students
B21
121 句
How I Learned to Code in 4 Months & Got a Job! (No CS Degree, No Bootcamp)
Interview EnglishWorking 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 |
什麼是跟讀法？
跟讀法 (Shadowing) 是一種有科學依據的語言學習技巧，最初開發用於專業口譯員的培訓，並由多語言者Alexander Arguelles博士普及。這個方法簡單而強大：您在聽英語母語原聲的同時立即大聲重複——就像是一個延遲1-2秒緊跟說話者的影子。與被動聽力或語法練習不同，跟讀法強迫您的大腦和口腔肌肉同時處理並模模擬實的講話模式。研究表明它能顯著提高發音準確性，語調，節奏，連讀，聽力理解和口語流利度——使其成為雅思口語備考和真實英語交流最有效的方法之一。