Shadowing Practice: How I Learned to Code in 4 Months & Got a Job! (No CS Degree, No Bootcamp) - Learn English Speaking with Video
Elige un modo de práctica
Cada modo abre una sala de práctica a pantalla completa.
121 oraciones
Si las oraciones son demasiado cortas o largas, haz clic en Editar para ajustarlas.
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?
Descargar app
Todo lo que necesitas para hablar con fluidez
Pronunciación con IAEvalúa cada oración
Práctica de IPADomina cada sonido
VocabularioConstruye tu banco de palabras
Juego de vocabularioAprende mientras juegas
FOR YOU
Recomendar Video
B21
179 oraciones
She learned one new skill that unlocked a $120K salary
Business EnglishInterview EnglishWorking Adults
B22
187 oraciones
How to ACTUALLY Get a DevOps Job in 2026
Interview EnglishUniversity StudentsWorking Adults
B22
75 oraciones
The unfair way I got good at Leetcode
Interview EnglishUniversity StudentsWorking Adults
B25
37 oraciones
I'm making my Ansible and Kubernetes DevOps books free this month
Business EnglishInterview EnglishWorking Adults
B2370 oraciones
Improve English Speaking Skills | Meeting a girl | Shadowing Practice with a Simple Conversation 💬
Interview EnglishWorking Adults
B22
697 oraciones
How To Write Words That Make People Buy (Full Course)
Business EnglishInterview EnglishUniversity Students
B24
85 oraciones
How To Dominate 2026 as a Software Developer
Business EnglishInterview EnglishUniversity Students
B2171 oraciones
Interview Tips from a Senior Software Engineer... and a 4 year old
Business EnglishInterview EnglishUniversity Students
B22
183 oraciones
I Learned More English in 24 Hours Than in 6 Months of Studying
Interview EnglishDaily ConversationUniversity Students
B29
12 oraciones
How To Learn Faster Than 99% of People
Daily ConversationWorking Adults
B22
354 oraciones
순수 국내파 한국인이 실리콘밸리 빅테크 개발자로 입성한 특급 영어 공부법
American AccentBusiness EnglishInterview EnglishUniversity Students
B26
35 oraciones
Steven Bartlett’s Secret To Business Success (Hint: It’s Not Hard Work)
Business EnglishInterview EnglishUniversity Students
Vocabulario y notas de pronunciación para esta lección
Esta lección de conversación de nivel B2 se basa en el vídeo “How I Learned to Code in 4 Months & Got a Job!”. Las palabras que más se repiten: learn, build, code, project, learned. Este vídeo tiene 121 frases y 1965 palabras para practicar shadowing. La parte hablada dura 9:29. El hablante habla rápido, unas 207 palabras por minuto, así que espera sonidos enlazados y reducidos. Solo el 79 % de las palabras está entre las 3.000 más comunes del inglés, por lo que el vocabulario es exigente.
Vocabulario clave de este vídeo
Las 15 palabras más avanzadas del vídeo, con su pronunciación y significado:
| Palabra | Pronunciación | Significado |
|---|---|---|
| developer sustantivo | /dɪˈvɛləpɚ/ | desarrollador |
| stack sustantivo | /stæk/ | pila, montón |
| importantly adverbio | /ɪmˈpɔɹ.tənt.li/ | importantemente |
| dedicate verbo | /ˈdɛdɪˌkeɪt/ | dedicar |
| programmer sustantivo | /ˈpɹoʊɡɹæmɚ/ | programador, programadora |
| parameter sustantivo | /pəˈɹæm.ə.tɚ/ | parámetro |
| clone sustantivo | /kloʊn/ | clon |
| tutorial sustantivo | /ˌtjuːˈtɔːɹɪəl/ | tutoría, tutorial |
| compartmentalize verbo | /kəmˌpɑɹtˈmɛntəlˌaɪz/ | compartimentar |
| credential sustantivo | /kɹɪˈdɛnʃəl/ | credencial |
| impostor sustantivo | /ɪmˈpɑstɚ/ | impostor, impostora |
| overarching adjetivo | /ˌoʊvəɹˈɑɹt͡ʃɪŋ/ | arqueante / enarcante / arcante en lo alto |
| reusable adjetivo | reutilizable | |
| superpower sustantivo | superpotencia, hiperpotencia | |
| takeaway sustantivo | /ˈteɪkəweɪ/ | restaurante de manducatoria para recoger, jama para llevar |
Phrasal verbs que vas a escuchar
| Palabra | Pronunciación | Significado |
|---|---|---|
| end up verbo | terminar, ir a parar | |
| get back to verbo | responder / contestar (en un rato), volver / tornar a contactar | |
| wake up verbo | /ˌweɪk ˈʌp/ | despertarse, recordar |
Frases que vale la pena repetir
Frases cortas y completas del vídeo que puedes reutilizar en la conversación diaria:
- I didn't even really know what coding was.
- By the way, I'm not knocking sales.
- You're a fake and a fraud.
- Where we're going to put it?
Gramática en este vídeo
Las estructuras que más usa el hablante, con las palabras exactas del vídeo:
| Estructura | En el vídeo |
|---|---|
| Present perfect have/has + participio pasado — una acción pasada que sigue importando ahora | I've actually never studied · haven't made · I've had |
| Oraciones de relativo who / which + oración — información extra sobre una persona o cosa | program, which is · project which will · GitHub, which is |
Pronunciación a tener en cuenta
El hablante usa 28 contracciones y formas reducidas, como didn't, I'm, you're. Dilas en su forma corta, tal como las oyes.
- Palabras largas — cuida el acento: developer /dɪˈvɛləpɚ/, importantly /ɪmˈpɔɹ.tənt.li/, parameter /pəˈɹæm.ə.tɚ/, collaboratively /kəˈlæb.(ə).ɹə.tɪv.li/, compartmentalize /kəmˌpɑɹtˈmɛntəlˌaɪz/
Sonidos difíciles para hispanohablantes:
- /v/ — no es /b/: los dientes tocan el labio inferior: developer /dɪˈvɛləpɚ/, collaboratively /kəˈlæb.(ə).ɹə.tɪv.li/, overarching /ˌoʊvəɹˈɑɹt͡ʃɪŋ/, leverage /ˈlɛv.(ə.)ɹɪd͡ʒ/, variable [ˈvæɹ.i.ə.bl̩]
- /z/ — sonora, no /s/: compartmentalize /kəmˌpɑɹtˈmɛntəlˌaɪz/, minimize /ˈmɪn.ɪˌmaɪz/, browser /ˈbɹaʊ.zəɹ/, anyways /ˈɛn.iˌweɪz/
Cómo practicar con este vídeo
- Escucha el vídeo entero una vez sin hablar y anota las palabras que no conoces.
- Empieza a velocidad 0,75×, haz shadowing frase por frase y vuelve a la velocidad normal cuando te resulte fácil.
- Grábate y compara con el original, prestando atención a palabras como developer, stack, importantly.
¿Qué es la Técnica de Shadowing?
Shadowing es una técnica de aprendizaje de idiomas respaldada por la ciencia, desarrollada originalmente para la formación de intérpretes profesionales y popularizada por el políglota Dr. Alexander Arguelles. El método es simple pero poderoso: escuchas audio en inglés nativo y lo repites en voz alta de inmediato, como una sombra que sigue al hablante con solo 1-2 segundos de retraso. A diferencia de la escucha pasiva o los ejercicios de gramática, el shadowing obliga a tu cerebro y músculos de la boca a procesar y reproducir simultáneamente patrones de habla reales. Las investigaciones muestran que mejora significativamente la precisión de la pronunciación, la entonación, el ritmo, el habla conectada, la comprensión auditiva y la fluidez al hablar, convirtiéndola en una de las metodologías más efectivas para la preparación del IELTS Speaking y la comunicación en inglés en el mundo real.