Comments
Hacker News
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?
by nitotm
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.
by brudgers
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.
by mixmastamyk
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”.
by sdevonoes
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.
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
by catzapd
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.
by rozenmd
I highly recommend you read this classic post from Patrick McKenzie: https://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-pr...
> 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.
by gk1
Join the discussion
Write your take first — we'll ask for email only when you're ready to publish.
- Hacker News
- 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?by nitotm
- 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.
by brudgers - 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.
by mixmastamyk - 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”.
by sdevonoes - 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.
- 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
by catzapd - 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.
by rozenmd - I highly recommend you read this classic post from Patrick McKenzie: https://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-pr...
> 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.
by gk1