Read on Twitter
Want to get a job as a self-taught web developer and you want to do it as quickly as possible (less than a year)?
Here's some actionable steps that helped me.
Here's some actionable steps that helped me.
1. Pick a tech stack/language and stick to it--all the way though.
I'd recommend JavaScript (along with HTML/CSS) as there are tons of web developer jobs out there utilizing this language and so many opportunities to branch out with different technologies that use it.
I'd recommend JavaScript (along with HTML/CSS) as there are tons of web developer jobs out there utilizing this language and so many opportunities to branch out with different technologies that use it.
2. Pick a resource to start with & limit the number of OTHER resources that you learn from.
I'd suggest @freeCodeCamp and no more than 2 other resources to learn with.
Follow the course for as long as you can, try to understand it deeply, and DO NOT skip the practice projects!
I'd suggest @freeCodeCamp and no more than 2 other resources to learn with.
Follow the course for as long as you can, try to understand it deeply, and DO NOT skip the practice projects!
3. Learn about Git and signup for a github account.
By learning Git, you'll most likely learn some command line as well, this is literally killing two birds with one stone, and you'll need these in your tool belt from here on out.
Your github account will come in handy
By learning Git, you'll most likely learn some command line as well, this is literally killing two birds with one stone, and you'll need these in your tool belt from here on out.
Your github account will come in handy
4. Start building out projects and pushing them to your gituhub account.
These can start out as course projects, but ideally you'll want to start pushing yourself to branch out and just google what you don't know to fill in the gaps.
Make these projects your BIG tasks ...
These can start out as course projects, but ideally you'll want to start pushing yourself to branch out and just google what you don't know to fill in the gaps.
Make these projects your BIG tasks ...
5. Your 'smaller' tasks should be building small landing pages/websites/applications EVERY DAY.
Set a timer at 2 hours or so, pick a simple E-Commerce page, open up your editor, now build it.
Get as far as you can, then stop. Continue this daily and gradually decrease the time.
Set a timer at 2 hours or so, pick a simple E-Commerce page, open up your editor, now build it.
Get as far as you can, then stop. Continue this daily and gradually decrease the time.
...5 cont.
This was the biggest turning point for me. The habit of building small projects daily on a time limit serves several purposes.
It forces you to become efficient and exposes you to what you trying to learn often. Soon, you won't need to google certain things.
This was the biggest turning point for me. The habit of building small projects daily on a time limit serves several purposes.
It forces you to become efficient and exposes you to what you trying to learn often. Soon, you won't need to google certain things.
6. After you have 4 or so projects and TONS of little toy projects on your github, build a portfolio site.
Contrary to belief, it doesn't have to shock the world, it can be a very simple place to share your story and your projects.
Make it yours, but keep it easy to follow.
Contrary to belief, it doesn't have to shock the world, it can be a very simple place to share your story and your projects.
Make it yours, but keep it easy to follow.
7. Start networking.
This can be on Twitter, through YT videos, through a blog, doesn't matter. Just start talking to people, make friends, ask questions, give help.
Grow your circle, this will only benefit you later, and the dev community just rocks!
This can be on Twitter, through YT videos, through a blog, doesn't matter. Just start talking to people, make friends, ask questions, give help.
Grow your circle, this will only benefit you later, and the dev community just rocks!
8. Been said before, but start applying BEFORE you're ready.
Here's the tip, when making your resume, do it in google docs, NOT in photoshop or Figma.
Even if you export as a pdf (you should), you want a computer to be able to read your resume and pull keywords out.
Here's the tip, when making your resume, do it in google docs, NOT in photoshop or Figma.
Even if you export as a pdf (you should), you want a computer to be able to read your resume and pull keywords out.
9. When applying to jobs, look over the posting and jot down keywords or technologies they're looking for.
Don't lie, but if you've been exposed to something they're looking for, put those key terms in your resume and in your cover letter--yes, always do a custom cover letter.
Don't lie, but if you've been exposed to something they're looking for, put those key terms in your resume and in your cover letter--yes, always do a custom cover letter.
10. Work harder than everyone else.
Don't neglect your learning, but once you get to the application phase, BEAST MODE!
We're talking as close to 10 or more custom applications/cover letters a day.
If you have linkedIn, find a recruiter from the company and reach out!
Don't neglect your learning, but once you get to the application phase, BEAST MODE!
We're talking as close to 10 or more custom applications/cover letters a day.
If you have linkedIn, find a recruiter from the company and reach out!
REPEAT 4 through 10. Don't stop learning, but make it focused learning.
Resist the urge to jump to a new framework or tech stack you saw on twitter, they'll never stop honestly.
There will always be time to learn new stuff once you get a job!
Resist the urge to jump to a new framework or tech stack you saw on twitter, they'll never stop honestly.
There will always be time to learn new stuff once you get a job!
