Some good ol’ CSS.
A few weeks ago, I wrote a short post on “What you should focus on as a new web developer?” In it, I suggested just learning how to build things, and not worrying about the frameworks/languages.
But after talking with a few readers, I can see there’s a need for help when deciding which framework/language/skills a new developer should learn (even if they are focusing on learning how to build things).
This makes sense. Besides basic HTML, CSS, and Javascript, there are so many frameworks/languages. And every job post seems to require different skills.
I remember navigating this time in my career. Here’s the process that seemed to work at that time:
“Hi company X, I saw your job posting for Y. I’m interested in working for your company because of A, B, C; but I don’t think I have all the qualifications required yet for the job role. Could I come to your office to discuss my current skill set, and get an idea of skills I’d need to learn before applying for a job like this in the future?”
Many employers won’t respond. Try to not take their lack of response as a negative judgment on your character. You’re asking for help — and they might be busy right now.
A few employers will respond. Those employers realize that cultivating new talent is valuable — and that connecting with smart people (like you) will pay off in the long run. Jump on these opportunities to meet.
You will generate a short-list of skills to learn. Go learn them. It might take you a year or more if you have other priorities in your life (like most of us do). There’s no time limit.
Stay in contact with the employers. When you get towards the end of your learning list, reach out to them again. Communicate your progress and ask about job openings. There may be some openings, there might not. Or the employers may suggest you learn a few more things. Go learn them, too.
At some point, your skills will surpass the requirements for a job somewhere, and you’ll be in. And after that happens, try to remember to help someone else behind you.