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

推荐订阅源

博客园_首页
阮一峰的网络日志
阮一峰的网络日志
S
Secure Thoughts
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
C
Cyber Attacks, Cyber Crime and Cyber Security
T
Threat Research - Cisco Blogs
P
Privacy & Cybersecurity Law Blog
The Hacker News
The Hacker News
H
Heimdal Security Blog
W
WeLiveSecurity
L
LINUX DO - 热门话题
Hacker News: Ask HN
Hacker News: Ask HN
WordPress大学
WordPress大学
The Last Watchdog
The Last Watchdog
Hugging Face - Blog
Hugging Face - Blog
博客园 - 【当耐特】
D
DataBreaches.Net
I
Intezer
Webroot Blog
Webroot Blog
C
Cisco Blogs
AWS News Blog
AWS News Blog
博客园 - 聂微东
T
The Blog of Author Tim Ferriss
V
Vulnerabilities – Threatpost
罗磊的独立博客
Google DeepMind News
Google DeepMind News
N
Netflix TechBlog - Medium
Schneier on Security
Schneier on Security
宝玉的分享
宝玉的分享
博客园 - 叶小钗
PCI Perspectives
PCI Perspectives
D
Docker
Scott Helme
Scott Helme
NISL@THU
NISL@THU
J
Java Code Geeks
B
Blog RSS Feed
Google Online Security Blog
Google Online Security Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
T
The Exploit Database - CXSecurity.com
AI
AI
美团技术团队
Cloudbric
Cloudbric
月光博客
月光博客
P
Proofpoint News Feed
T
Tailwind CSS Blog
Google DeepMind News
Google DeepMind News
小众软件
小众软件
www.infosecurity-magazine.com
www.infosecurity-magazine.com
The Cloudflare Blog
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org

Adactio

June 16th, 2026, 11:12am June 16th, 2026, 10:16am Enhancing with CSS Grid Lanes How building an HTML-first site doubled our users overnight Speaking in Dublin June 13th, 2026, 9:09pm A tale of two browsers Sarah Canary by Karen Joy Fowler June 12th, 2026, 5:59pm The Field Guide to CSS Grid Lanes June 12th, 2026, 12:24pm June 12th, 2026, 8:58am June 11th, 2026, 6:22pm June 11th, 2026, 6:20pm June 10th, 2026, 6:25pm June 10th, 2026, 10:14am June 9th, 2026, 8:50pm June 9th, 2026, 1:55pm June 8th, 2026, 7:45pm June 8th, 2026, 4:32pm Amsterdamming June 5th, 2026, 3:16pm June 4th, 2026, 8:21pm June 2nd, 2026, 8:37pm 25 years of The Session Happy Monday everyone, and let's talk about gender and ethnicity ratios at tech events. AI and the Rise of Mediocrity May 28th, 2026, 7:24pm Picture at an exhibition May 27th, 2026, 9:41pm May 27th, 2026, 1:52pm May 25th, 2026, 8:03pm Gaeltacht cois Tamaise 2026 May 25th, 2026, 3:07pm May 23rd, 2026, 8:06pm May 23rd, 2026, 8:31am May 22nd, 2026, 3:38pm May 22nd, 2026, 8:19am May 22nd, 2026, 7:22am May 21st, 2026, 8:19pm Brigid by Kim Curran May 20th, 2026, 7:12pm May 17th, 2026, 6:21pm May 15th, 2026, 4:19pm Tito as Gaeilge The closing talks at UX London 2026 Three things about data Native Apps Should Be Avoided Whenever Possible — No One's Happy WebKit Features for Safari 26.5 May 11th, 2026, 4:17pm I knew my writing students were using AI. Their confessions led to a powerful teaching moment | Micah Nathan Gideon The Ninth by Tamsyn Muir May 8th, 2026, 3:55pm Better Browser Caching with No-Vary-Search May 7th, 2026, 9:55am May 7th, 2026, 7:49am The schedule for UX London 2026 Google’s Prompt API Reminder: You Can Stitch Together Lots of Little HTML Pages With Navigations For Interactions Netizen | Derek Sivers April 30th, 2026, 7:59pm April 29th, 2026, 8:12pm April 27th, 2026, 7:47pm April 25th, 2026, 12:03pm April 25th, 2026, 12:00pm April 25th, 2026, 8:03am April 24th, 2026, 7:57pm April 24th, 2026, 5:12pm Two Paradigms for Enhancing HTML Tags Summary punishment It's Not AI. It's FOMOnetization. Alistair Davidson / validation-enhancer · GitLab Never Lose Form Progress Again :: Aaron Gustafson Dilation Expansion artifacts April 19th, 2026, 6:03pm Finn Mac Cool by Morgan Llywelyn April 17th, 2026, 7:58am April 16th, 2026, 6:42pm Threat models No-stack web development Design and Engineering, As One · Matthias Ott April 14th, 2026, 7:21am April 13th, 2026, 7:47pm April 11th, 2026, 8:39am April 10th, 2026, 5:36pm My salary history Conference organising in 2026 April 7th, 2026, 8:32pm TinyStart AI Might Be Our Best Shot At Taking Back The Open Web | Techdirt April 6th, 2026, 12:46pm The AI Great Leap Forward April 4th, 2026, 6:42pm April 3rd, 2026, 5:27pm April 2nd, 2026, 8:58pm April 2nd, 2026, 4:32pm Web Day Out - 12 March 2026 Mistrust HTML Video Poster Image: Enable Responsive Images and ALT Text for Poster
The value is in the difficulty - Annotated
2026-05-19 · via Adactio

Anomalocaris canadensis. Credit: Paleozoo

I got no sleep last night, which means I'm awake early thinking through things I can't fix. One haunted topic is how software creation is going through a value collapse and despite all the vibe coding poasts on the subject, I'm still not sure most people in the industry have yet worked out what that means and what comes next.

Pop economics gives a tidy answer to what makes something valuable. It's scarce or hard to produce (or both). Price roughly reflects the cost of making something, plus whatever premium scarcity allows. When barriers to production are high, supply stays limited. A limited supply X real demand = higher value.

This value holds until something disrupts the barriers. When production suddenly becomes cheap or easy, supply floods in. When that supply reaches a saturation point, then prices must slide toward the marginal costs. When the costs approaches zero, inevitably so does the price.

Even if buyers can't evaluate quality directly, the fact that something was hard and expensive to make is a useful proxy. A handmade suit is probably better quality than a fast-fashion one. Software that took a team of expert engineers a year to build probably solves a problem thoroughly. This labour signal communicates some value before you've experienced the product. Are scarcity and labour signals are about to stop applying to software, and how can they not?

Before language models, writing software required significant and genuine expertise, time and capital. Most users didn't need to understand how code worked to understand that it was bloody hard. You'd hire a developer, or teams of them, pay them a boat load of money, and they'd spend months working on something hard. That effort was visible and it priced the market.

There was a real scarcity of people who could write code well. Years of training, accumulated pattern recognition, architectural instincts. That stuff took time to develop. You couldn't shortcut it to the level that shipped reliable, scalable AAA software. That constraint is now going, or gone.

Vibe coding collapses all these the barriers and the labour signal will be the first to break. Anyone with taste, a bit of domain knowledge, a decent prompt, and a tokens budget can now ship something functional in days. A weekend vibe-coder can produce something that looks and behaves comparably to months of professional work. Maybe not enterprise-grade distributed systems perhaps (well, not yet), but something functional. Something good enough to solve a problem. Something good enough to sell (well, for now).

Buyers now know this (or they're learning this). Once that's more-widely understood, the implicit premium attached to "software exists, therefore someone worked really hard on it" disappears, never to return.

We've seen this arc before, and music is the richest analogy.

Pre-internet, making and releasing music was genuinely expensive. Recording, pressing, distribution, promotion all cost real money and required real experts and gatekeepers. Fewer artists got through, but of those who did, a meaningful proportion could make a half-decent living. Then DAWs, MP3s, P2P sharing, and MySpace arrived almost all at once. Anyone could record and release a professional-sounding track for next to nothing.

The filters collapsed almost overnight.

The result was more musicians, more music, more creativity, more voices than ever before. Genuinely wonderful in many ways. And proportionally, far fewer artists able to make a sustainable living from their work.

Skip forward, and the long tail is now very long and very thin. Most musicians make music despite the economics. The joy is real; the money usually isn't. The entities making money are the streaming platforms, the ticket vendors, the merchandisers, the distributors. As in every gold rush, it's the shovel sellers that make the money.

What's interesting is that the music industry didn't flatten into equality when the barriers dropped. It sorted into three distinct tiers:

At the top, a tiny number of artists enjoy massive commercial success, but even that gets propped up by brand deals, sync licensing, touring. Streaming royalties alone rarely sustain even the very famous ones.

In the middle, a hollowed-out tier survives on direct-to-consumer relationships: Bandcamp sales, Patreon subscriptions, merch drops, ad reads. Less glamorous, but honest work. The model is: find the people who value what you make enough to pay you directly, and sustain that relationship.

Then the low end long tail—the vast majority—where the day job pays the bills and nights and weekends go to the thing they love. No illusions about going full-time. It's maybe the most-honest relationship between a maker and their craft. They make music because making something matters, regardless of whether it pays—and it usually doesn't. Software is heading for the same stratification.

After a couple of too many years working in product development, I know that the most valuable thing about software isn't always in the code itself.

Network effects work when value lives in who uses the product. WhatsApp isn't valuable because it's incredibly hard to build. It's valuable because everyone you want to message is already on it. A technically equivalent replacement doesn't matter. But genuinely networked products are rare as hen's teeth.

Distribution keeps attention scarce even when code is free. Getting software in front of users still requires marketing, trust, and often real money. But I wonder does control of distribution sustain value now, or does it just delay the erosion? This moat may be shallower than it appears. A well-funded competitor with a vibe-coded version can appear overnight and undercut immediately. The foundational AI companies are now expanding their product portfolios and sherlocking is a thing.

Deep domain expertise is the strongest argument. Knowing what to build for a genuinely complex problem—e.g. medical, legal, or industrial use cases—still requires knowledge language models can't (yet) replicate cheaply. The code is "easy". The insight about what the code needs to do isn't. But again, this protects only a narrow-but-lucrative slice of the overall software products market. Expect industries to try solve their problems internally now rather than pay external experts.

But broadly, are network effects, distribution and domain knowledge enough for most products? Are they enough for the flood of vibe-coded apps that are coming?

What I think actually happens is that value concentrates at the top. A small number of products with genuine moats capture most of the market. Everything else slides toward marginal costs. The middle market is where it may get really uncomfortable.

Those products existed because software was hard to build. The difficulty was the value. Remove the difficulty, and the rationale for their existence—and certainly their price—weakens considerably.

What follows is a Cambrian explosion of software products: vast in number, lacking in real differentiation, with near-zero individual value. Many useful things get built. Most generate no revenue. The long tail of content creation, now applied to software.

And here's the part that workers in the industry should sit with for a moment: Cui Bono? Who wins in this scenario? The Anthropics, the Lovables, the Vercels: the infrastructure layer. The shovel sellers that profit regardless of whether the builders succeed or not.

A diverse software ecosystem—lots of builders, lots of products, lots of different solutions to lots of different problems—has been a net benefit to everyone for many years.

But if the music industry example holds true, the picture that emerges isn't "zero software value". Its a power law that says a handful of big winners, a hollowed middle sustained by direct relationships and goodwill, and a long tail of useful things with a handful of users built by people who love building (without expectation of financial return).

That's not nothing. The long tail may produce real value for real users. But it's a very different world from the one the software industry has operated in for the last 30+ years. It's one where many in the industry may need to start looking for other forms of income.