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

推荐订阅源

D
DataBreaches.Net
F
Fortinet All Blogs
D
Docker
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
WordPress大学
WordPress大学
罗磊的独立博客
Y
Y Combinator Blog
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
J
Java Code Geeks
T
The Blog of Author Tim Ferriss
U
Unit 42
N
Netflix TechBlog - Medium
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
V
V2EX
云风的 BLOG
云风的 BLOG
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
T
Tailwind CSS Blog
Hugging Face - Blog
Hugging Face - Blog
Stack Overflow Blog
Stack Overflow Blog
爱范儿
爱范儿
酷 壳 – CoolShell
酷 壳 – CoolShell
P
Proofpoint News Feed
G
Google Developers Blog
H
Help Net Security

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
SaaS Won't Die Because of AI
Raahul Sesha · 2026-05-03 · via DEV Community

I've been coding for 25 years, and am not new to the "X is now dead; long live X" arguments. The latest fad seems to be the claim that "SaaS is dead" because anyone can "create their own software; so why rely on others?"

Let's dissect this.

1. Software is still not dead

There are two important points to note. Even with AI:

  1. Software has not disappeared (and we all agree with that easily).
  2. Code has not disappeared. It's just that AI helps write code for you. But the code is still there.

If software still exists, and it still exists in the form of code, then there will always be a need for people who maintain it, whom we can call software engineers.

It doesn't matter if non-programmers can create software too. For example, DIY has not rendered carpenters obsolete, right?

So software and its makers are both still in the game.

2. Solving yesterday's problem today is not necessarily an accomplishment

When I was a kid, I created my first crappy game using Game Maker, a free tool written in Delphi by a university professor. But just 10 years before that, games were incredibly hard to write because they not only required much more coding experience but also ran on limited hardware.

Just because I can easily do what took talent yesterday doesn't mean that talent isn't needed anymore. Those folks were creating even bigger games, ones that were not possible to do with Game Maker at the time.

It's like saying that since I can learn calculus in high school today, we don't need people like Newton anymore.

3. Creating some software doesn't mean one can create all software

LLMs can interpolate very well. So asking it to solve problems very similar to ones already solved for ages will be very easy.

But the true test is how one uses LLMs to solve NEW problems. To extrapolate from where we are. That's the kind of boundaries all the good computer scientists and software engineers are pushing.

However, most others focus on doing less to accomplish the same thing rather than setting bigger goals.

4. LLMs are good actuators that still need tools

Saying that we don't need SaaS anymore is like saying we don't need operating systems, too, because each person can write their own.

The fallacy is in thinking that LLMs "think" and can "do everything." If that were the case, LLMs would have improved on their own, rather than Anthropic or OpenAI employing large numbers of humans (many of them computer scientists and software engineers) to improve the model itself. In this case, instead of using LLMs as intelligent machines, they're using them as bootstrapped compilers.

LLMs require tools that they can call. And these tools need to be efficient. The entire universe of software, algorithms, and data structures is what LLMs would activate. But it still needs those machineries to be present in the first place. There will still be a need for better algorithms, data structures, designs, and even tacit knowledge that's digitized by humans.

For example, LLMs are pretty bad at design. Even if they are good, they still need good abstractions. An LLM that integrates deeply with Figma and uses all of its tools and design abstractions natively is a killer combination. But it's great only because Figma is a powerful toolbox for an LLM.


Conclusion

In short, software's here. Code is still here. Yes, the nature of a software engineer's job has changed. But when hasn't it really? How is it different from going from assembly to higher-level languages, thus leaving control of the low-level details?

And as long as there are software engineers and software to create, there will always be specialists providing specialized software products or services, which will invariably be better than hobbyist work.

What do you think?