I like your list and linked resources, but I hope people will not take it as a step by step curriculum. So here are some remarks that came into my mind:
I would rather move your last point more upfront: Create a LinkedIn profile right away! Participate in other communities like dev.to and StackExchange. Start writing your resume soon and improve it as you move on. You may even want to apply for jobs or internships quite soon. It does not hurt to have a LinkedIn profile, even if you are not a programmer, and you can start to grow your network before completing a learning roadmap.
If you are lucky to get an internship or take part in coding events like a hackathon or meetup, it helps to develop your collaboration and communication skills as well. Many people learn better and faster with a personal coach or at least some real person they can talk to or ask for a code review.
And don't forget about YAGNI: you might not need everything that is trending and seems important right now. For example, I have been doing full-stack web development for more than twenty years without ever writing a single line of GraphQL. I would personally recommend to take this list as an inspiration but not strive to complete the whole list step by step in only six weeks.
Thank you for the feedback @ingosteinke
! I think you make a very valid point about creating your LinkedIn ASAP. I see no harm in this, I may want to make some adjustments. You should always work on growing your network! Joining a tech community and engaging is like steroids for growth potential.
I mostly left it at the end because I would like individuals with no experience to be able to speak about technology and what they have done before applying for jobs. I have interviewed a lot of candidates over the years. There always seems to be a difference between entry-level candidates who say "I am learning this right now" vs the ones that say "I built this".
That being said I would like the takeaway from this to be, just go build something! You don't need to be an expert. Find a stack that works for you. Build it. Apply for jobs. Talk about your passion for building, what you learned, and how you want to continue to grow. That will resonate with a lot of engineers who interview you.
Use this roadmap as a super high-level blueprint for landing your dream job! You will become an expert in time.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I like your list and linked resources, but I hope people will not take it as a step by step curriculum. So here are some remarks that came into my mind:
I would rather move your last point more upfront: Create a LinkedIn profile right away! Participate in other communities like dev.to and StackExchange. Start writing your resume soon and improve it as you move on. You may even want to apply for jobs or internships quite soon. It does not hurt to have a LinkedIn profile, even if you are not a programmer, and you can start to grow your network before completing a learning roadmap.
If you are lucky to get an internship or take part in coding events like a hackathon or meetup, it helps to develop your collaboration and communication skills as well. Many people learn better and faster with a personal coach or at least some real person they can talk to or ask for a code review.
And don't forget about YAGNI: you might not need everything that is trending and seems important right now. For example, I have been doing full-stack web development for more than twenty years without ever writing a single line of GraphQL. I would personally recommend to take this list as an inspiration but not strive to complete the whole list step by step in only six weeks.
Thank you for the feedback @ingosteinke ! I think you make a very valid point about creating your LinkedIn ASAP. I see no harm in this, I may want to make some adjustments. You should always work on growing your network! Joining a tech community and engaging is like steroids for growth potential.
I mostly left it at the end because I would like individuals with no experience to be able to speak about technology and what they have done before applying for jobs. I have interviewed a lot of candidates over the years. There always seems to be a difference between entry-level candidates who say "I am learning this right now" vs the ones that say "I built this".
That being said I would like the takeaway from this to be, just go build something! You don't need to be an expert. Find a stack that works for you. Build it. Apply for jobs. Talk about your passion for building, what you learned, and how you want to continue to grow. That will resonate with a lot of engineers who interview you.
Use this roadmap as a super high-level blueprint for landing your dream job! You will become an expert in time.