is it hard getting a job as a web dev.?

Go for it ! I it’s really a good choise

I don’t think that’s a waste of time at all. I always encourage everyone to have at least some knowledge of the full stack.

Yes you are. However It takes years/decades to assemble the big picture and get a sense of what is and is not a good usage of your time. And necessarily you have to waste a lot of your own time in order to develop a taste. OK so then is it a waste? Not sure But short answer, yes, JS is a waste of time, *and* it will teach you terrible lessons and terrible habits which take years to unlearn Things that are not a waste of time - C - Erlang - Assembly - actual projects that do an actual useful thing, irrespective of the language - SICP (you may need to have a bit of programming experience to really appreciate it, not sure) If I had to do it over, I would start with SICP and then Erlang then C then Assembly.

@@krakenmetzger i know c and assembly already

Either JS or PHP. Start with either.

start with rust

rust is better than both of those

Congrats on the internship! As for transitioning to Java, whenever I need to learn a new language/framework for work there's a few things I do: 1. Watch some KZfaq videos. I usually try to find one of those ~1 hour long "full" tutorials. Personally I try to avoid the beginner ones that will spend hours teaching you what a variable is, but up to you. 2. If the KZfaq videos aren't clicking, a few times I have bought cheap courses on Udemy or similar platforms. Some of these I actually expensed to the company, but that depends on the company policies of course. This also might not be a great choice depending on the length of your internship as full-time employees generally have more time to ramp up than interns do (I know it's kind of backwards). 3. You can also try some free online tutorial websites. I would Google something like "Java for Python developers". I can't vouch for any particular one, but I am sure there are some good ones. 4. Make it clear to your manager/mentor that you are new to the stack. Hopefully they will be helpful in providing you guidance, in my case they always were. 5. Ask tons of questions. If you are stuck on something for > 30 minutes or so, it is probably time to ask a question. Try to frame the question with what you have tried already, and ask for help figuring it out. This is much better than just asking someone to do things for you. And if they say something in answering your question that you don't understand, make sure to follow up on that rather than just being confused by the answer (I made this mistake a ton as an intern). 6. Read through pull requests put up by other people on the team to get an idea for how they are structuring their code. 7. Give it time. The more practice you get, the better things will feel. You also might want to try to figure out if the pain point is specifically Java or the frameworks. That can help you narrow down what resources to look into more. For example, in my first internship I was having a lot of trouble with some of the frontend of our stack, but it turned out that RxJS was really the main culprit for my confusion. A few tutorials on that and I was feeling a lot better, even if I never fully understood it deeply during that internship. Good luck, you got it 👍

@@ConnerArdman Thank you Conner 😊

I wouldn't start with Ruby (at least for someone looking to do primarily frontend work), but it can definitely go in the "choose your own adventure" category after learning the basics. That said, Ruby/Ruby on Rails has seemingly gotten a lot less popular over the last 5-10 years, so I'm not sure its a great recommendation for beginners unless they have a specific use case in mind for it.

@@ConnerArdman Yeah I agree, if you’re looking to be frontend focused than Node is the way to go. I actually learned Ruby as my first language and then backend engineering as a whole before I learned frontend. It definitely made learning frontend and JS a little more challenging, but I will say since Ruby/Rails has declined in popularity hardly anyone is learning it so there’s a shortage of new Ruby developers which is why they’re some of the highest paid at the moment. I ended up focusing on frontend during my first job but moved over to being a Ruby developer for the increase in pay.

Oops I thought this comment was on a different video talking about frontend 😅 But yeah there’s definitely money to be made learning “declining” tech. I think for someone new wanting to do back-end, I’d probably still recommend to start with newer/easier stacks, but learning Ruby to start wouldn’t be a terrible idea either.

I appreciate the detailed comment, but honestly I disagree with just about all of this and much of it is objectively inaccurate. The reason I said to start with JS/TS or Python is mostly due to the ease of learning. People are much more likely to stick with it if they learn something simpler first. Learning Erlang or C as first languages in 2023 just isn't the most effective way to learn in my opinion, especially if you are trying to self teach without a lot of guidance. I would certainly recommend learning them eventually (especially C), but just not right from the beginning. That said, the idea that these languages aren't used at real companies is entirely false. JS/TS and Python are the most used languages by professional developers according to last year's StackOverflow developer survey. Node.js was also the most used web framework, and Flask was high on the list as well. To be honest, I don't think most people care much about what the companies they work for are making as long as they get paid and have good benefits (assuming those products aren't grossly unethical). Many people would love to work for these "fake" companies you are describing. Moreover, there are plenty of "real" companies using Python and JS, both major tech companies and fortune 500s. For example, Netflix, Reddit, LinkedIn, and Lyft all reportedly use Flask. Python is used at basically every company, but Microsoft, Intel, NASA, Chase, and Spotify to name a few. NodeJS is also used across the industry - Walmart, IBM, Paypal, SAP, AWS, Twitter, and Uber to name a few more. Nothing wrong with recommending people to read SICP, but the idea that you should start with a textbook is just unreasonable. Without taking the accompanying university classes, it will be very difficult for anyone new to the field to get anything from it. If you want extra context, I think Harvard's CS50 would be a great recommendation, potentially to follow before doing anything else in this video. That said, I also don't think that is a necessity right out the gate. A lot of people just want to gain some basic "practical' experience first. As for learning higher level math, to be honest this just feels like gatekeeping. 98% of developers outside of specialized fields like ML will never need math beyond what they learned in high school. It's not entirely useless of course, but it certainly is not a requirement.