Engineers: Stop trying to win other people's game
anthonyputignano.com
Engineers: Stop trying to win other people's game
1–10 of 25 posts
Re: Engineers: Stop trying to win other people's game
#2Experience matters and it’s an advantage, that’s not a reason for new people not to compete but rather one to understand that context and use it to help them grow.
Re: Engineers: Stop trying to win other people's game
#3Re: Engineers: Stop trying to win other people's game
#4Re: Engineers: Stop trying to win other people's game
#5> Swarms of others have been developing expertise with technologies that emerged last decade for… at least a decade. It’s already their superpower. It’s unlikely to become yours, too.
I agree that juniors should be open to experimenting with new technology, but they shouldn’t ignore the basics. It’s true that you’re probably not going to become the premier React expert and rise to the top of the field, but that’s not a good goal to start with anyway. Knowing some core technologies well is basically mandatory so you have something to build upon.
It’s also key to being able to get a job. Being the junior who doesn’t have much foundational knowledge but has a bunch of surface level frontier AI experiments they don’t really understand in their GitHub portfolio is not a good place to be, but I’m seeing more and more junior applicants like this. They follow articles like this and think that learning anything that isn’t extreme cutting edge is a waste of their time. The result is a junior who doesn’t really have a good foundation of the basics, but also doesn’t really have the skills necessary to understand the frontier AI work they’ve been trying to get on to their resume.
So exploring and experimenting is good, but don’t neglect the mature technologies. Those mature technologies are what’s going to get you the job. Don’t become the person with the “AI engineer” resume who can’t do simple interview questions to demonstrate basic understanding of the boring things.