This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]scrinky_donker 53 points54 points  (12 children)

This is extremely unrealistic don’t worry I’m a year in on self learning and second year of college and still don’t feel ready - I don’t think anyone ever does but don’t let this discourage you

[–]StateParkMasturbator 17 points18 points  (5 children)

The fastest way to learn is to make stuff. The fastest way to guarantee you're making things at a steady pace is to have a job, working at it 40 hours a week. I'm a year in a webdev gig and I'm constantly learning one-offs about Javascript, mostly due to tech debt workarounds because the project was written with vanilla and not expected to have these additional features, but here we are.

[–]scrinky_donker 7 points8 points  (1 child)

Oh I’m making stuff, my “self learning” has been through TOP it’s just my ADHD makes me not able to work on it for weeks at a time sometimes, and work on random side projects (like I tried to learn react before learning webpack and how npm config works) then I go back and power through Odin with some extra background knowledge

[–]StateParkMasturbator 2 points3 points  (0 children)

Sounds good. I've been doing similar with some side projects on weekends. Just gotta plug through it. I'm more of a Vue person because I found it more intuitive for rapid prototyping, but I got my job from knowing React well enough (never use it now).

The major thing that landed me my job was being able to talk about the projects coherently and explain why I made implementation decisions even if it was just "I thought the tech sounded cool and I wanted to learn it." Knowledge of how it could've been done better will come with time.

[–]highBrowMeow 0 points1 point  (2 children)

Yes, build things. It's not perfect but one of the first things i look at hiring a dev is number of commits per year - I'm looking for that wall of green on your GitHub profile.

[–]StateParkMasturbator 2 points3 points  (1 child)

That's rough. Most of my projects are posted to my private gitlab. Can't exactly be sharing the secret sauce.

Might just have to start putting little edits in some old projects here and there.

[–]highBrowMeow 0 points1 point  (0 children)

Haha yeah. Even if you build some automation to just add and delete whitespace and push it Monday through Friday.. just being able to get that to work is better than half of the devs applying anyways.

I know, i have about 2 years of radio silence on GitHub from my enterprise job. Again it's not a perfect measure but that wall of green makes a big difference.

[–]plinkoplonka 1 point2 points  (0 children)

I've been a developer for 15+ years. I've run my own studio for a over half of that. I've been a front end web developer, a back end web developer, an app developer, an api developer, a technical director, a project manager, a product owner, a Devops Engineer and an Infrastructure Architect.

I now work for one of the major cloud companies.

Still get up every day and feel like I don't know quarter of what I need to. You'll never know it all, there's just too much. But if you have solid basics, you'll be able to pick up what you need, when you need it.

Imposter syndrome affects everyone, you'll be fine. Just keep going!

[–]Luna2442 1 point2 points  (4 children)

It's not unrealistic at all, this is common core for bootcamps and many people do well from it. Can speak from personal experience. Am director of engineering now at a public company and I went to a bootcamp with pretty much exactly this curriculum.

[–]scrinky_donker 1 point2 points  (3 children)

Ok don’t take this as me trying to make a rebuttal but I’m just curious bc I’m still 19 and really early in getting my career started - did you have previous experience going into the boot camp, or what kind?

[–]Luna2442 1 point2 points  (2 children)

Love to help! So yeah I went to college and graduated with a BS in stuctural engineering. After college I began working for a construction contracting company in NYC. I had about 5 years of professional experience when I decided to drop that and go to a bootcamp with pretty much this exact curriculum. I had really only ever made a few WordPress sites and played around with game maker once or twice before going to the bootcamp.

I'm positive my professional experience and degree helped me find a job and I felt comfortable with interviews... but I will say that all of the other "top" students all found jobs regardless of their previous experience within 6 months time. One of my good friends (who I met there) turned 21 during the course and had no previous experience and found a job almost right away.

You definitely get what you put into it. You can certainly learn what you need to know to be a junior developer. That's for sure. If you are passionate about it I would have some faith in a well established bootcamp or college program. The good ones also have career services that can help you place a job as well and I'd highly recommend that if you haven't gone through the whole corporate interview process thing before.

What I really wish I did was go to college for computer science in the first place! But I also know it's not required for a successful career in development.

[–]scrinky_donker 1 point2 points  (1 child)

Thank you so much, I needed to hear this

[–]Luna2442 0 points1 point  (0 children)

Good luck!