惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Engineering at Meta
Engineering at Meta
博客园_首页
J
Java Code Geeks
Jina AI
Jina AI
B
Blog RSS Feed
量子位
有赞技术团队
有赞技术团队
M
MIT News - Artificial intelligence
L
LangChain Blog
Microsoft Security Blog
Microsoft Security Blog
小众软件
小众软件
博客园 - 聂微东
月光博客
月光博客
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
博客园 - 三生石上(FineUI控件)
Last Week in AI
Last Week in AI
MongoDB | Blog
MongoDB | Blog
I
InfoQ
罗磊的独立博客
H
Hackread – Cybersecurity News, Data Breaches, AI and More
爱范儿
爱范儿
Y
Y Combinator Blog
Vercel News
Vercel News
雷峰网
雷峰网

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
The Winner of the AI-Pocalypse? The Full-Stack Generalist...
Ben Link · 2026-06-18 · via DEV Community

We've been told since late 2022 that "within 6 months, we won't need software engineers anymore". I think that's half-right.

I also think it's just the AI flavor of an old Holy War.

Remember the Olden Days

Think wayyyyyyyyy back to... 2010. (I have children older than this, and that makes me feel a sense of existential dread 😱)

  • Businesses were weathering an economic downturn and trying to "do more with less".
  • We were starting to realize that deeply-specialized "Silos" were (at best) problematic and (at worst) causing harm to our productivity.
  • More powerful Javascript frameworks were becoming super-popular, and more "traditionally backend logic" was moving its way into the "traditionally design-only frontend".

This led to the rise of a concept called the "Full Stack Engineer" - someone who could generalize and interact easily with the development stack at multiple layers. Need some SQL? They can give you a passable version. Need to integrate with a vendor API? They've got you. Have a CSS bug that's causing the widget to be invisible only on Thursdays? They'll pair up and help you find it.

Half the tech community said that FullStack engineers were unicorns, that nobody could keep that much in their head at once. Half the community said that every software engineer should become FullStack if they wanted to survive the downturn with a job. Half the community (who apparently struggled with arithmetic on multiple fronts 🤔) advertised themselves on LinkedIn as FullStack Engineers with 20 years of ReactJS experience.

FullStackers: Plausible (but with a caveat)

In fancy management and corporate leadership courses, there's a popular concept of "Professionals of Certain Shapes".

  • There's the "I" shaped person, who has chosen to obsess over a single topic and dived deeply into it. They're not often super aware of other topics and disciplines, but they know their one thing inside and out.

  • There's the "T" shaped person, who knows a single topic very well but has basic general knowledge about several others. We tend to call them "generalists"... jacks of all trades, master of... well... one or less.

  • There's a "Comb" shaped person, who knows several topics very well while having a passing knowledge of many others. These tend to be your generalists with a little more career time, who have potentially moved around the organization a bit and held a few roles on different teams.

The more prolific HR folks probably have other shapes of people out there, but that feels to me like splitting hairs and these 3 shapes probably suffice for most of us to work with.

I'm of the opinion that the "FullStack Engineer" is just someone who's moved into the "T" or "Comb" shaped realm. I'm also of the opinion that anyone can become one of these shapes with curiosity and study time. It's not something reserved for the elite, so much as defined by the eliteness of people who do it.

Get to the Part Where They Survive the AIPocalyse, Blink

I know, I know -- I digress.

The common trait among all "T" and "Comb" shaped people is that they're adaptable. Generally, they started as "I" shaped people who knew a lot about something, and then they started to attend to things adjacent to their specialty.

They weren't experts in those other things, but they were curious about them. They got just good enough to solve the basic problems, and then lean on the experts when things got too deep.

Which Leads Me to AI

AI in the software development lifecycle is going to eat the "I" shaped people for breakfast. When you can give all the world's knowledge to a language model and let it answer questions, generate code samples, and sniff out bugs, an "I" shaped software engineer isn't really going to be needed. The value of that one language, of that one specific niche technology, is eliminated.

But you know what AI can't do? Understand its surroundings. Even as context windows get larger and inferences get faster and cheaper... people can out-think them any day of the week. I think one of the greatest human characteristics is the ability to solve a problem based on a completely different set of unrelated data that just happens to kinda pattern-match... like when Mr. Miyagi tells Daniel to "Paint the Fence", in an effort to help him learn Karate.

Miyagi helping Daniel paint the fence

This happens to be a speciality of people who are good at... Adapting. When they immerse themselves in a new technology for the first time, everything seems weird and different. But instead of being confounded by it, they notice patterns of the same "shape" as other technologies that they do know well, and it helps them learn.

It's something the bots can't do. Bots need direct correlations, they need pre-training.

And That's Why The Generalists Will Win

If the hype about AI holds true (I don't believe it will, but let's game this out), The "I" shaped people are going to struggle because they're easy to replace with a model. Pre-train it on "technology X" and boom, they're done. The "T"s and "Comb"s on the other hand will be able to leverage their lateral-thinking advantage to survive.

If the hype falls apart, we're going to have a big need for those generalists. They're going to have to unravel a bunch of code, likely touching multiple technologies in the stack, and pay off tech debt along the way.

But it's gonna be a while

Dilbert strip: It's still a bad time to look for a job

We probably have another year or two before we see the full effects of this AI stuff... which is rough if you're looking for work in tech right now. I'm sorry to be the bearer of bad news but it's gotta get a little bit worse before it gets better. If you can just hold on, though... and spend the time learning a few new technologies, you'll be in a really good place when the demand curve bends its way back in a favorable direction!

The Moral of the Story: Avoid Hype, Focus on Fundamentals

Yeah, you can try to replace all SaaS companies with a $200/month Claude Code subscription and maybe get-rich-quick. But you'll get better return on your investment if you spend that time, money, and effort on broadening your knowledgebase. Are you a coder? Learn a CI/CD stack. Are you a SysAdmin? Take a course in Python or Rust or Go or whatever language you'd like to play around with. Are you an AI bro? Make sure you know how to do all of the things you scream "AGENTICCCCCCCC" about, but with your WiFi turned off.

There are ultimately two kinds of technologists: those who enjoy the challenge of growing and learning, and those who are doing it all to hit a jackpot. I know which one I am... do you?