2 ms·
I'm a mostly self-taught web dev and a high school dropout who eventually got a (completely unrelated, non-computer) degree. I started out doing simple web pro
by solardev 4y ago
I'm a mostly self-taught web dev and a high school dropout who eventually got a (completely unrelated, non-computer) degree.
I started out doing simple web projects for tiny businesses, like neighborhood yoga studios or small nonprofits. They could be simple HTML + CSS pages, or basic Wordpress setup, or like integrating a signup form for their CMS vendor. It's a lot easier to learn a particular skill if it's limited in scope to a single feature/project, and also if you're getting paid even a bit for it. These tiny jobs didn't pay great ($15-$20/hr) but motivated me to learn the skills.
The trick for me was not to learn everything in a few months, but to gradually accumulate skills over time. Once I landed my first full-time dev gig (still only paying like $20-$25/hr), suddenly I could spend 2080 hours a year (estimated # of full-time working hours) learning on the job, on the employer's dime, reading Stack or whatever to fulfill a given business need.
Ten years later I'm still doing that, getting paid more these days and having much more experience and know-how, but still just generally learning on my own. Approximately 10-15% of my time is actually writing lines of code; the overwhelming majority of it is reading and researching and learning new skills all the time. In that sense every dev is probably self-taught to some degree.
My education was completely irrelevant to coding, but it did help me choose what industry (solar & renewables) I wanted to code for. I'm sharing that because sometimes companies don't just choose you for pure coding ability, but also your natural interest in whatever field they happen to be working in. "Cultural fit" is a part of any hiring process, whether they admit it or not, unless you're just a temp/contractor doing a specific thing. In my experience, people are way more willing to hire people they like, even if they're not the most qualified, than someone who's highly competent but not as relatable.
TLDR don't try to jam it all in into a few short weeks. Nobody can learn well like that, whether it's new language or anything else. Tackle a little digestable bit at a time, with an end goal in mind ("I'm going to build this small project, or this one screen, or this tiny feature", not "I'm going to become an expert dev in 9 months").
Spend time reading other people's code and questions on Stackoverflow. Ask your own. A lot. Pick things that are fun for you, whether for the technical challenge or because they relate to some hobby of yours. Don't just code in a vacuum, code for a purpose that you care about or enjoy. Make real projects, even if they're tiny.