Every few months, some new framework drops and the internet loses its collective mind. React alternatives, Rust in the kernel, Go for everything—you know the drill. But here's the uncomfortable truth nobody's posting hot takes about: chasing trends is a losing game for most developers. A thought-provoking piece on DEV.to argues that choosing your tech stack by personal affinity—not whatever's trending on Hacker News—produces better outcomes and more sustainable careers. The article comes from developer Carlos Arturo Castañeda, who traces his own journey back 12 to 15 years to when AI was still firmly in academic territory. Back then, working with image identification in Python or motion recognition systems wasn't glamorous—it was niche, specialized work that most developers wouldn't touch with a ten-foot pole. "It was very academic, scientific, some said," Castañeda notes about those early days. That specificity turned out to be the point.

Why Trend-Chasing Burns Developers Out

The core argument isn't anti-progress—it's pro-intentionality. When you pick technologies because they genuinely resonate with how you think, you naturally invest more deeply in understanding them. That intrinsic motivation translates into mastery faster than grinding through another Express boilerplate tutorial just because Node.js is "what everyone uses." There's a psychological trap here that affects junior devs especially hard. When you build your skill tree based on market demand rather than genuine interest, you're constantly running on external validation. New job posting drops with "required: Svelte"—now you need to learn Svelte. Next quarter it's Bun. Castañeda's retrospective framing is telling. Those "academic" AI applications he worked on in the early 2010s—audio improvement systems, image identification pipelines, motion recognition—all became foundational skills when the deep learning boom hit around 2012-2014 with ImageNet and convolutional neural networks.

The Affinity Framework for Tech Decisions

So what does picking by affinity actually look like in practice? It starts with honest self-assessment: What problems genuinely fascinate you? Where do you lose hours without noticing because you're deep in the work? When something breaks at 2 AM, do you reach for coffee or do you lean forward with curiosity about what's happening under the hood? The author isn't suggesting ignoring market realities entirely—rent still exists. But within the space of viable career options, affinity should be the filter, not Twitter buzz.

The Long Game

Here's what the trend-chasers miss: technology stacks have longer shelf lives than blog posts claim. COBOL runs on bank mainframes. Fortran powers scientific computing. Assembly still matters for embedded systems. The technologies you love tend to stick around in your career because you'll keep using them, keep learning them deeply, and keep finding opportunities where they fit—even when the hype has moved on.

Key Takeaways

  • Intrinsic motivation beats external validation for building lasting expertise
  • Market demand matters within constraints, but affinity should be your primary filter
  • The "academic" skills you build today often become essential when trends catch up
  • Trend-chasing creates a constant cycle of shallow learning and burnout

The Bottom Line

Stop letting the crowd pick your tools. The most durable careers in tech come from developers who found their stack through genuine affinity—not because some podcast host said it was "the future." Your gut knows what you'll actually master. Trust it.