TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Ask HN: How important are stacks and specialization?

7 pointsby StefanWestfalover 3 years ago
Over the last year&#x27;s I have worked in different roles and with different technologies. Python, Go, C, TS&#x2F;React, domain specific languages and tooling, and played with frameworks like Elm and Svelte. Mainly in the areas of web, technical simulations, and DataScience.<p>I would argue that I am flexible but that comes at a cost, low specialization.<p>My question: To build a career, how much do tech stacks matter? Should I stick to one (React, FastAPI, PostgreSQL) or doesn&#x27;t it really matter as long as I can ship something? Is it fine to use Svelte for a new project when breaking into the market or should I stick to React?<p>Note: I worked in different roles not described as SWE but in practice I am writing code full time for almost 3 years. Building a career refers to &quot;becoming officially a SWE&quot;.

6 comments

codingdaveover 3 years ago
I&#x27;m at the tail end of a career, and found that specializing in a stack can be great when you are in mid-career and the stack is hot. You don&#x27;t want to specialize too early because it pigeonholes you. And you don&#x27;t want to stay specialized too late, because your skills stagnate. But I rode one stack for 15 years -- got in it when it was young, did great in it for 5 years, then once it declined, I spent 10 years helping people shut it down and transform to new stacks. In the process picked up the next stack to specialize in.
tacostakohashiover 3 years ago
&gt; To build a career, how much do tech stacks matter?<p>Tech stacks come and go every few years (5 years is a pretty good run for a framework &#x2F; stack), careers last 20-40 years.<p>You&#x27;re going to need to develop skills outside the tech stack that are generally useful and have a longer half-life (like debugging, SQL, shell scripting, source code management), and also proactively switch to a new stack every now and then.
评论 #29985984 未加载
closeparenover 3 years ago
Big high-flying Silicon Valley tech companies are pretty stack-agnostic; hiring is based on algorithms and architecture. Smaller, less engineering-centric companies seem to more strongly identify programmers with their stacks and ask for N years with a specific tool.
tharneover 3 years ago
Don&#x27;t overthink this one. Go online and make a note of job postings that seem interesting and desirable to you. Then, note the kinds of things they ask for and focus on those.<p>Re: how important stacks and specialization is, that really depends on the hiring manager and the culture of the company you&#x27;re applying to. Generally speaking though, it shouldn&#x27;t be overly important for more junior roles.
评论 #29985784 未加载
jstx1over 3 years ago
The question in the title shouldn&#x27;t matter to you. You&#x27;re looking for your first job, there&#x27;s nothing to specialise in yet. The tools that you already know are in demand and are enough to land you job - don&#x27;t distract yourself with other stacks until you can get that first job.
he11owover 3 years ago
Since you&#x27;re asking about building a career, I&#x27;d give the answer you weren&#x27;t asking for: build domain expertise.<p>The intersection of software and domain expertise is highly prized. So it takes chips off the table on whichever bet you make around tech stacks.