> You are not defined by your chosen software stack: I recently asked via Twitter what young engineers wanted to know about careers. Many asked how to know what programming language or stack to study. It doesn’t matter. There you go.
This is especially true now, since coding agents make it possible to work with any stack.
ericmcer 1 days ago [-]
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.
patwork 1 days ago [-]
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.
ericmcer 4 hours ago [-]
I dunno even isolated to language specific aspects someone with no experience could hang themeselves. I use a ton of Go & Javascript, if you take a fundamental part of both languages, async operations and compare them they have radically different approaches. Even if I was skilled at distributed systems with deep JS knowledge I would lack the skills to audit Go code effectively. goroutines and channels require a bit different mental model than promises and callbacks. You could easily let the AI architect a mess that works.
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.
austin-cheney 11 hours ago [-]
React jobs, even fullstack, pay well but are ultimately beginner jobs in a market swollen with other well experienced beginners. Stop worrying about the stack and stop competing with beginners for basic employment.
Instead focus on education: masters, certifications, and such. Secondly, write code in your spare time where you ship completed applications.
rozenmd 1 days ago [-]
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.
Froedlich 1 days ago [-]
Managers might want solutions, but to get to them you have to go through HR, which wants checkboxes ticked.
That's two entirely different screening processes.
geldedus 22 hours ago [-]
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
rozenmd 11 hours ago [-]
shops you actually want to work at don't have "mandatory conditions", they have criteria that match an ideal candidate.
if you think you can do the job, track down the hiring manager and convince them.
brudgers 15 hours ago [-]
Learning a new stack is easier than finding a job.
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.
catzapd 1 days ago [-]
Rather than switch stacks, better way to phrase it is that one should try to increase breadth and depth of knowledge.
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
sdevonoes 1 days ago [-]
I started with js and php. Moved to Java. Then node. Then php again. Then Go. Then Kotlin. Then TS. Then Python. Then Go again. In between a bunch of sql, html, css, and many different tools, libraries and frameworks. The most important things Ive learned are around architecture/databases/distributed-systems, tho.
I don’t think i could have survived in this industry if I knew only 1 or 2 “stacks”.
mixmastamyk 1 days ago [-]
Don’t believe anyone is hiring “switchers” or people looking to learn new things these days. I only get interviews for things that done the last ten years.
Folks saying it doesn’t matter are correct in times of scarcity, but was always a hard sell to employers. Currently impossible without personal connections.
nitotm 1 days ago [-]
I'm on a similar situation. When you say "switch stacks" what do you have in mind? It seems your experience is pretty demanded already.
Do you have a strong Github profile?
aristofun 1 days ago [-]
Serious employers don’t care what tools you used, they care what heights did you reach (what kind of projects did you deliver).
UK-Al05 4 hours ago [-]
That often means employers big budgets and training.
khurs 8 hours ago [-]
He said "my last contract"
In contract roles, they often seek a particular skillset
> You are not defined by your chosen software stack: I recently asked via Twitter what young engineers wanted to know about careers. Many asked how to know what programming language or stack to study. It doesn’t matter. There you go.
This is especially true now, since coding agents make it possible to work with any stack.
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.
Instead focus on education: masters, certifications, and such. Secondly, write code in your spare time where you ship completed applications.
I'd reach out to people you've worked with before and ask if they need help.
That's two entirely different screening processes.
if you think you can do the job, track down the hiring manager and convince them.
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.
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
I don’t think i could have survived in this industry if I knew only 1 or 2 “stacks”.
Folks saying it doesn’t matter are correct in times of scarcity, but was always a hard sell to employers. Currently impossible without personal connections.
In contract roles, they often seek a particular skillset