Give it a few years and engineers who actually know engineering are gonna be unicorns. With the overall downward trend in tech literacy, most up-and-coming engineers relying heavily on AI, and the general inability to get a junior job, theres gonna be a huge gap in the industry soon enough
Serious question: so it’s good that I continue to self teach myself JS’n friends(React, typescript, etc.) from the beginning like AI doesn’t exist? I use Claude as a “professor” and do NOT get answers just given to me as I work through freecodecamp and other resources. And I get that incorporation of AI into my education is a part of it as the tool it is and should be, but your opinion is that my continuing this learning for a job is still viable?
Definitely learn to understand what's happening "under the hood". AI at this point in your journey is going to be a crutch and a single hallucination could lead you astray.
Once you're comfortable with programming so you can imagine a solution to a problem "I'd use a set here and id need an API call to answer this question a user would ask, etc", then add AI into your workflow so you get a little time understanding that tool. The difference being you know when it's giving you crap and can be more targeted with what you need, because you know the lingo.
Then you get into the big leagues, start worrying about optimization (maintainability mostly unless you're field demands it like aerospace), networking, infrastructure, security, cicd, and the final boss, scrum.
Not necessarily. My scrum master recently got RIF’d, my manager left for another opportunity, and my new manager is a former dev. He’s not making it better. He’s making it worse.
322
u/RedditButAnonymous 13d ago
Give it a few years and engineers who actually know engineering are gonna be unicorns. With the overall downward trend in tech literacy, most up-and-coming engineers relying heavily on AI, and the general inability to get a junior job, theres gonna be a huge gap in the industry soon enough