Permanently Deleted

  • pixxelkick@lemmy.world
    link
    fedilink
    arrow-up
    8
    ·
    edit-2
    8 months ago

    It’s typically a good idea to first focus on a stack in demand, then once you have some $$$ you can enjoy the hobby of learning esoteric stuff :)

    My recommendation is always the same:

    1. Contact a couple local tech recruiter agencies in your city.

    2. Ask them for what are the top 2-3 tech stacks most in demand the past 2 years, as well as any relevant certificates companies were looking for, and expected entry level wage for each stack.

    3. Analyze those 3 stacks, pick the one that seems best for you.

    4. Go learn it, make an easy application for it full stack with an open source DB like Postgres or Mongo

    5. Bonus points: setup a basic dockerfile for it and docker compose

    6. MOST IMPORTANT: Make detailed “how to install manually, how to compile, how to docker deploy” guides on the github README. Include pictures of your app in the README, make it look good to a cursory glance.

    7. Aight now that you have a simple working app on your guthub, pin it on your profile so it’s first thing people see. Link your github to your LinkedIn, add this project to your LinkedIn profile.

    8. Now go look up those certs you found about in step 2. Look up the price to get em solo proctored from home. Usually they are a couple hundred bucks.

    9. Do it, study, get a cert or two and add to your resume.

    10. Okay now go back to that recruitment agency, ask them for help with optimizing your resume. This is a free service they offer, you don’t have to pay as the dev, the companies pay the costs to recruit you, the process is free for you.

    11. They will now find jobs for you, negotiate wage for you, and find interviews for you. Keep applying on your own and improve your app you made, study the deeper nuances of your stack, etc

    12. When you do get an interview, spend the days prior studying their stack and try to get to the point you can hold a convo about . “Oh yeah, you guys use Fwibble.js? I’ve been really excited to learn Fwibble.js, I have heard cool things about how it is good for wumbling tuples!”, etc etc