In interviews, I do care, but more on why you're using this stack. If you know only one stack and use that for everything, that's pretty bad. If you're thinking, "Hey let's use JS/Kotlin on every part of the stack," that hints at a fear of learning new stacks as well.
By ten years of experience, you should probably have used all the major tech stacks in your area of expertise. If you're BE, probably Go, Node, Rails, Django, Spring, maybe even PHP. If mobile you should be able to use native, capacitor, PWA, Flutter, React Native, maybe KMP. And so on.
It's sometimes a bonus if you're using something someone has never heard of. Y Combinator is named after a Lisp thing. PG was using Lisp as a hack while everyone else was using C and he credits it for his rapid development speed. Many tools are just built for teams of > 3, and lose the advantage of having a solo dev.
If you're competing with Google's AI team and you use something generic, then... you're probably not going to make it. If you're building something that doesn't require a lot of technical expertise, they might still want to suss out that you know the difference between JavaScript and Java.
>By ten years of experience, you should probably have used all the major tech stacks in your area of expertise. If you're BE, probably Go, Node, Rails, Django, Spring, maybe even PHP. If mobile you should be able to use native, capacitor, PWA, Flutter, React Native, maybe KMP. And so on.
That's not real life.
Most Devs get a job and learn a stack and then they stay in that stack unless there is a reason to change
Most BE will know one of either Java or .Net or Python. As that is what most corporates use.
Interesting, we're building a Vision based AI product so I wrote a super comprehensive list for what AI models + the software stack I think we should be using. Its different than what we're actually using because I made that list with the funding and talent in mind and sort of a 3 year tech stack than a 3 month tech stack.
muzani|6 months ago
By ten years of experience, you should probably have used all the major tech stacks in your area of expertise. If you're BE, probably Go, Node, Rails, Django, Spring, maybe even PHP. If mobile you should be able to use native, capacitor, PWA, Flutter, React Native, maybe KMP. And so on.
It's sometimes a bonus if you're using something someone has never heard of. Y Combinator is named after a Lisp thing. PG was using Lisp as a hack while everyone else was using C and he credits it for his rapid development speed. Many tools are just built for teams of > 3, and lose the advantage of having a solo dev.
If you're competing with Google's AI team and you use something generic, then... you're probably not going to make it. If you're building something that doesn't require a lot of technical expertise, they might still want to suss out that you know the difference between JavaScript and Java.
v5v3|6 months ago
That's not real life.
Most Devs get a job and learn a stack and then they stay in that stack unless there is a reason to change
Most BE will know one of either Java or .Net or Python. As that is what most corporates use.
codecracker3001|6 months ago
quantdev1|6 months ago
codecracker3001|6 months ago
sama004|6 months ago
1oooqooq|6 months ago
PaulHoule|7 months ago