From College Dropout to Professional Developer
This is about how Tim KIm became a self-taught software developer and how he learned and how to code without a computer science degree or coding bootcamp.
Let see his life journey that he was speaked in his channel
Table of Contents
Tim KIm :
I dropped out of college, was in debt, working 60 hours a week, hated my job, and most importantly, I felt stuck. This is the story of how I learned to code within four months and got a job, all without a computer science degree or a coding boot camp.
The Turning Point
Before getting into tech, I worked various dead-end sales jobs because I dropped out of community college and didn't have other skills. I disliked the idea of hopping from job to job. I wanted a career with long-term mobility. Despite not knowing much about coding, I knew the tech industry offered substantial growth and opportunities.
Discovering Coding
On day one, I went on Google and searched "how to code." That’s when I found FreeCodeCamp and started learning about web development. I quickly picked up HTML, CSS, and my first real programming language, JavaScript. I chose JavaScript because I wanted to build web apps, a field with high demand in the job market.
Initial Struggles
Using FreeCodeCamp, I learned coding basics like variables, loops, objects, and functions. However, I still felt incapable of applying for jobs. I realized that while I could code, I didn’t know how to program—that is, to use code to build something useful. But I was starting to love the journey and problem-solving.
Going All-In
I quit my job, moved to Korea to minimize expenses, and decided to learn coding full-time. This was much harder than I anticipated. I found a course called "Learning How to Learn" by Barbara Oakley, which taught me how to study effectively using techniques like Pomodoros and creating a dedicated learning space. I joined a coworking space and resumed my studies with renewed focus.
Daily Routine
Here’s what my typical day looked like:
- 08:00 a.m.: Wake up.
- 08:30 a.m.: Head to the train station.
- 09:00 a.m.: Arrive at the coworking space.
- 09:15 a.m.: Coffee, journaling, reviewing the curriculum.
- 09:30 a.m. to 12:30 p.m.: Study sessions in 30-minute Pomodoro increments.
- 12:30 p.m. to 1:30 p.m.: Lunch and a small break.
- 02:00 p.m. to 6:30 p.m.: More study sessions.
- 6:30 p.m. to 7:30 p.m.: Gym three times a week.
- 8:30 p.m. to 9:00 p.m.: Dinner with my grandma, then helping her clean.
This was my schedule six days a week, no exceptions.
Building Projects
The next part of FreeCodeCamp involved building front-end projects using HTML, CSS, and JavaScript. I felt stuck until I found a YouTube channel by Stephen, who streamed himself building projects. By following along, I gained confidence and skills. I also used watchandcode.com for additional learning.
First Full-Stack Project
To become a programmer, I decided to build my first full-stack project with Stephen’s help. We picked a project that would teach me the basics of CRUD (Create, Read, Update, Delete) operations. I chose to clone Pinterest. We used tools like Jira for project management and GitHub for version control. Stephen treated me like a junior developer, teaching me valuable skills like debugging and creating reusable code.
Job Search
After completing my first full-stack project, reality set in—I needed a job. I defined my ideal job criteria and found opportunities on sites like weworkremotely.com and remoteok.io. Instead of just applying, I reached out to hiring managers and developers, introducing myself and offering to work for free. This approach resulted in six responses, four interviews, and three job offers.
Landing the Job
I chose the company with the best learning opportunity and compensation package. My first salary was $50,000 a year, increasing to $65,000 after the probationary period, with benefits like health and dental. Importantly, I got to work remotely.
Conclusion
I’m not saying you’ll become an expert developer by following this plan, but it worked for me. Learning to code involves solving problems and persisting until you find answers. Now, with over a decade in tech, I know that credentials matter less than focused effort and practical skills.
If you’re interested in learning more, follow our blog. And if you want to see me apply these principles to something other than coding, check out the next blog.
Follow our Blog and Stay Updated with the Latest Insights!
.png){kind=avatar}
No comments:
Post a Comment