11–20 of 22 posts
By breadth I mean learning other programming language, frameworks, system design etc.
By depth I mean that - if you claim to know React - then get to know the deep detail of React, TS and the related ecosystem.
You can showcase the expertize by writing code, demoing it or sharing on github. Writing about it is another way
The job has never been about "writing code". You're there to solve problems for the business. I'd reach out to people you've worked with before and ask if they need help.
Because it is not finding a job.
And when you are done learning a new stack, your network is still the same and your on the job experience is just further in the past.
Finding a job sucks. Learning a new stack doesn’t change that.
The job has never been about "writing code". You're there to solve problems for the business. I'd reach out to people you've worked with before and ask if they need help.
nevermind, i was asked for "10 years of React experience" as a mandatory condition for a job, which was a no-pass in my case
if you think you can do the job, track down the hiring manager and convince them.
Instead focus on education: masters, certifications, and such. Secondly, write code in your spare time where you ship completed applications.
Serious employers don’t care what tools you used, they care what heights did you reach (what kind of projects did you deliver).
In contract roles, they often seek a particular skillset
Serious employers don’t care what tools you used, they care what heights did you reach (what kind of projects did you deliver).
Earlier quoted context omitted.
I dunno I find it almost more important than ever to have deep domain experience. You need to be able to scan output and spot any problems/improvements instantly. If I am just auditing AI output around an area I don’t have mastery of I am basically useless.
A stack is still not a domain. You could have domain expertise in building highly scaled distributed systems and still not call yourself a ____ programmer. The point is that your value lies more in knowing how to build for performance, consistency, reliability at scale and not in knowing where the semicolon goes.
That is why I would be hesitant to review complex Rust or some other code I have no experience in, sure the language has ways to handle things like async, garbage collection, etc. but I would just be assuming the AI is doing it right or even worse trying to steer it to handle it in a Javascript or Go manner.