シャドーイング練習: How I Learned to Code in 4 Months & Got a Job! (No CS Degree, No Bootcamp) - YouTubeで英語スピーキングを学ぶ
B2
I dropped out of college, was in debt, working 60 hours a week, hated my job, and most importantly, I felt stuck.
121 文
文が短すぎたり長すぎる場合は、Editをタップして調整してください。
1
I dropped out of college, was in debt, working 60 hours a week, hated my job, and most importantly, I felt stuck.
2
This is the story of how I learned how to code within four months, and I got a job.
3
I did it with no computer science degree or a coding BootCamp I am going to explain exactly what I learned, how I got a job, and how much that job paid.
4
Let's go. Before I got into tech, I was working a lot of dead end sales jobs, because I dropped out of community college and I didn't really have any other skills.
5
I didn't like the idea of always having to hop from job to job If I didn't like something.
6
I wanted something with a little bit more career mobility long term.
7
I didn't even really know what coding was.
8
I just knew that the tech industry was, let's say, a great environment for $180 grand now $200 ish $250,000 $400,000 annually growth... Yeah.
9
By the way, I'm not knocking sales.
10
I think sales is a really important skill to learn.
11
I just needed a change, and it really just wasn't for me long term.
12
And I wanted to gain the ability to build something of my own.
13
The idea of building something from zero to one seemed like a superpower to me.
14
Day one, I just went on Google and I typed in how to code.
15
That's when I found a site called FreeCodeCamp, and I started to learn about web development.
16
I quickly learned about HTML, CSS, and I learned about my first real programming language called JavaScript.
17
There's a bunch of different programming languages that you could learn, but I personally chose JavaScript because I wanted to build web apps.
18
Even major companies like Uber and Airbnb use it, and there's a massive demand for it in the job market.
19
By using FreeCodeCamp, I started to learn the basics of coding.
20
I learned things like variables, loops, objects, and functions.
21
But even after doing the tutorials, I didn't really feel like I could apply to anything.
22
And I still didn't even know how to do something as basic as building a website.
23
And I realized that I learned how to code, not exactly how to program.
24
I was writing code to solve logic problems, but I didn't know how to program, which is using the code to build something useful.
25
At this point, though, already I was starting to love the journey.
26
I really liked problem solving, and I could see myself doing something like this long term.
27
So I did what any sane person would do and I quit my job and I moved to Korea to minimize my expenses.
28
And I decided to learn full time.
29
Learning full time was a lot harder than I thought.
30
I've actually never studied anything this complicated or tough before, and I was quickly starting to realize that I didn't really know how to study at this pace.
31
I would sit in front of my computer and hours and hours would go by.
32
That was when I went online, I typed in how to learn.
33
And I found a course called "Learning how to Learn" by Barbara Oakley.
34
This course was life changing.
35
My two main takeaways were one, it taught me how to learn in space segments, A technique called Pomodoros.
36
And the course taught me that I needed to create a dedicated space for learning.
37
So I joined a Coworking space, so I could focus better.
38
Now, armed with new knowledge, I got back to studying. And it worked.
39
Here's what a normal day looked like.
40
08:00 a.m wake up.
41
8:30, Head to the train station.
42
09:00 a.m. Arrive at the coworking space.
43
9:15, Coffee Journaling reviewing the curriculum.
44
9:30 to 12:30, I would have my first study session, where I did 30 minutes increments of Pomodoros.
45
From 12:30 to 1:30, I would eat lunch and take a small break, then back to studying.
46
From 02:00 p.m to 6:30, it was more 30 minutes increments of Pomodoros until I was ready to head out.
47
From 6:30 to 7:30, I would gym three times a week, And then 8:30 to 9:00, I would eat dinner with my grandma, then help her clean.
48
This was my schedule for six days a week, no exceptions.
49
The next part of FreeCodeCamp was a lot more challenging.
50
Front end projects.
51
They essentially give you a list of projects that you have to build using HTML, CSS and JavaScript.
52
To me, this felt like a massive jump because I never actually built anything before.
53
I felt stuck at this stage until I found a YouTube channel of this guy named Stephen who would stream himself building these projects line by line.
54
By copying him and recreating what he was doing, I was able to use that experience and build the next couple of projects on my own.
55
I also found a great resource called watchandcode.com, where you watch and code.
56
By following along once again and modeling others, the concepts really started to take hold, and I was really starting to understand what I was doing, not just solving a math problem.
57
In exactly one month, I ended up earning my FreeCodeCamp Front End Developer certificate.
58
I was learning a lot, but I never actually built anything full stack before.
59
Something with a front end or an interface, the thing that you see within the browser.
60
A database where all the information lives, essentially, and a server which handles and manipulates all the data in the back end by taking in requests from the front end.
61
So I still felt like an imposter and not a real developer.
62
You're not an intellectual. You're a fake and a fraud.
63
So to become a programmer, I decided to build my first full stack project.
64
Remember Stephen with a YouTube channel?
65
I reached out to him to get his assistance to help me build my first full stack web app, we decided to meet three times a week.
66
Here's what we did.
67
We picked one major overarching project which will teach me the basics of CRUD, which is Create, read, update and delete.
68
These are the foundations for any web application.
69
I decided to clone Pinterest.
70
I honestly don't think I would have gotten a job without this next part, so pay attention.
71
I asked Stephen to treat me like a real junior developer working at a company.
72
We implemented a project management tool called Jira.
73
We used Jira to compartmentalize the entire project and write the requirements of exactly what I'd be building.
74
This taught me how to estimate my work and plan how to build an entire web app from zero to launch.
75
We also set the project up on GitHub, which is a version control application.
76
This taught me how to develop different branches for when I was working on certain features, and I could learn how to control different versions of the code.
77
Most tech companies use some version of the two applications because being a developer isn't just about knowing how to code.
78
It's about knowing how to work collaboratively with other people as well.
79
Stephen grilled me on our pair of programming sessions.
80
He was very strict about me keeping the deadlines and the estimates that I originally wrote out for myself.
81
He would constantly question why I was doing what I was doing.
82
And he even taught me the concept of DRY, just Don't Repeat Yourself, or essentially just making reusable code.
83
I had to learn how to build by Googling for answers and using sites like Stack Overflow.
84
And he would leave me a lot of comments on things that I needed to change.
85
So I learned how to debug my code on my own.
86
This made me feel like I was a real developer.
87
at this time, I supplemented my learning journey with Udemy courses on React and Node because these were the two frameworks that I chose to build my Pinterest clone.
88
As a result of building my first full stack project, I ended up learning how to do things like how to design a database, build APIs, set up Auth, and eventually push the app to a cloud server.
89
These are all things I would have never learned by just doing tutorials.
90
And in around two months, I finished my first full-stack web app.
91
I remember when I finished the app, I felt like a real programmer.
92
That's when reality set in and I realized I'm still broke.
93
I haven't made a single penny in over a couple of months, and I still needed to find a job.
94
It was time to see if everything that I learned was actually worth anything.
95
First, I defined the job that I wanted.
96
I wanted to be remote. And most importantly, I wanted to work for a small to medium sized company, because I hate working in a corporate environment.
97
I found all the jobs that fit my parameters on sites like weworkremotly.com and remoteok.io And instead of just applying to these jobs, I found the contact information of the hiring managers and developers who worked at the company, and I messaged them to introduce myself.
98
I explained exactly what I had learned up until this point,what I was looking for.
99
I even included the link to my GitHub so they could see the projects that I had built.
100
Most importantly, I included an offer that I know that they couldn't refuse.
101
I offered to work for free.
102
And I understand guys, not everyone can afford to do this, but I had originally estimated that this was going to take me around four months anyways.
103
And I had another month of time that I could essentially dedicate to learning.
104
I knew all I had to do was get my foot into a company,I could essentially learn there and then prove my worth over time to leverage that into a real job long term.
105
Overall, I found around 22 jobs I thought fit the parameters of what I was looking for.
106
I got around six responses. From those responses, I got four interviews.
107
And out of the four interviews, I ended up getting three legitimate job offers.
108
Even though I had offered to work for free, after the technical interviews, the employers thought that I had enough skills at that point where I was worth hiring for a full time job.
109
I ended up choosing the company with the best opportunity to learn, and that also happened to have the best compensation package as well.
110
My first salary was $50,000 a year, and then after my probationary period, I was making $65,000 a year.
111
My benefits kicked in like health and dental.
112
But the biggest perk for me was that I got to work remotely the entire time as long as I worked the US time zone.
113
I'm not saying that you'll be an expert developer if you follow this plan.
114
I'm just sharing what I did to learn just enough to land me a job, as most of the progress that I've had as a developer all came on the job.
115
No luck here, just focused effort.
116
Now, I've been working in tech for over a decade, and let me be the first to tell you that nobody cares about your credentials.
117
Learning how to code was mainly two things learning how to solve problems, and two, persisting until you find the answer that you're looking for.
118
If you're interested in seeing us learn more cool stuff, make sure to subscribe to the channel.
119
And also, if you want to see me apply these principles to something other than coding, like something artistic, click on this video.
120
Where we're going to put it?
121
Here?
アプリをダウンロード
話したすべての文をAIが採点
TRENDING
人気動画
この動画でスピーキングを練習する理由は？
この動画は、プログラミングを学ぶ過程とその結果として得られる職を通じて自己成長を促進するストーリーを提供しています。話者は、大学を中退し、多忙な仕事から解放されるためにプログラミングの世界に飛び込み、4ヵ月間の努力で新しいキャリアを築きました。このような背景は、英語スピーキング練習に適しており、実生活の経験や感情を使った表現を学ぶことができます。動画を通じて、感情豊かな言葉遣いや、自分の意見を明確に述べるスキルを向上させることができるでしょう。特に、YouTubeで英語学習を行うことで、発音や文脈を意識しながら練習することができます。
文法と表現の文脈
- "how to learn how to learn" - このフレーズは、学習方法を学ぶという概念を強調しています。このような自己反省の表現は、自分の学習を評価できる能力を養います。
- "I wanted to gain the ability to build something of my own" - 自分の未来を築くことへの強い願望を表しています。このような自己表現は、英語で自分の目標を述べる際に役立ちます。
- "I chose JavaScript because I wanted to build web apps" - 理由を述べる際のフレーズ構造が優れています。「because」を使うことで、意図を明確にすることができます。
- "I realized that I learned how to code, not exactly how to program" - この文は、微妙な違いを明確にすることが重要であることを示しています。英語では、明確さがコミュニケーションの鍵です。
一般的な発音の罠
この動画では、発音の難しい単語やフレーズがいくつかあります。特に、"JavaScript"や"dedicated"の発音は、英語を学ぶ際に注意が必要です。これらの単語は、音声のリズムやアクセントが重要であるため、shadow speechを活用し、正しい発音を体得することが大切です。また、話者のアクセントは、流暢さや自信を持って話す上での一因であるため、英語シャドーイングを行うことで、発音の精度を向上させることができるでしょう。
シャドーイングとは？英語上達に効果的な理由
シャドーイング（Shadowing）は、もともとプロの通訳者養成プログラムで開発された言語学習法で、多言語習得者として知られるDr. Alexander Arguelles によって広く普及されました。方法はシンプルですが非常に効果的：ネイティブスピーカーの英語を聞きながら、1〜2秒の遅延で声に出してすぐに繰り返す——まるで「影（shadow）」のように話者を追いかけます。文法ドリルや受動的なリスニングと異なり、シャドーイングは脳と口の筋肉が同時にリアルタイムで英語を処理・再現することを強制します。研究により、発音精度、抑揚、リズム、連音、リスニング力、そして会話の流暢さが大幅に向上することが確認されています。IELTSスピーキング対策や自然な英語コミュニケーションを目指す方に特におすすめです。