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

推荐订阅源

Project Zero
Project Zero
GbyAI
GbyAI
Y
Y Combinator Blog
Google DeepMind News
Google DeepMind News
小众软件
小众软件
The GitHub Blog
The GitHub Blog
阮一峰的网络日志
阮一峰的网络日志
J
Java Code Geeks
WordPress大学
WordPress大学
Microsoft Security Blog
Microsoft Security Blog
IT之家
IT之家
F
Fortinet All Blogs
博客园 - 【当耐特】
H
Hackread – Cybersecurity News, Data Breaches, AI and More
P
Proofpoint News Feed
Schneier on Security
Schneier on Security
C
Cybersecurity and Infrastructure Security Agency CISA
L
LINUX DO - 热门话题
Spread Privacy
Spread Privacy
O
OpenAI News
V
V2EX
博客园 - 三生石上(FineUI控件)
AI
AI
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Stack Overflow Blog
Stack Overflow Blog
P
Privacy International News Feed
Microsoft Azure Blog
Microsoft Azure Blog
Blog — PlanetScale
Blog — PlanetScale
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
Jina AI
Jina AI
H
Help Net Security
L
LINUX DO - 最新话题
Application and Cybersecurity Blog
Application and Cybersecurity Blog
T
Tenable Blog
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
Cisco Talos Blog
Cisco Talos Blog
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
博客园 - 叶小钗
V
Vulnerabilities – Threatpost
C
Cisco Blogs
D
Darknet – Hacking Tools, Hacker News & Cyber Security
酷 壳 – CoolShell
酷 壳 – CoolShell
Hacker News: Ask HN
Hacker News: Ask HN
S
Security @ Cisco Blogs
S
Securelist
T
The Blog of Author Tim Ferriss
Apple Machine Learning Research
Apple Machine Learning Research
美团技术团队
雷峰网
雷峰网
V2EX - 技术
V2EX - 技术

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 Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
We're Linear Thinkers in an Exponentially-Changing World
Keith MacKay · 2026-05-11 · via DEV Community

Keith MacKay

We're Linear Thinkers in an Exponentially-Changing World

The more time I spend in the AI ecosystem, the more convinced I become that the pace of change isn’t just fast—it's explosive…and increasingly so. Most people still think in terms of linear change while the world is accelerating exponentially.

That mismatch is where disruption happens.


We’re linear thinkers living in an exponential world

We weren’t built to intuit compounding curves. It’s why exponential progress feels like it comes out of nowhere.

Most AI charts are logarithmic for a reason: they’re trying to compress the 10X-after-10X reality into something our brains can process. Turn those accelerations we don't process into nice straight lines.

And this is why the fast eat the slow. By the time a large company finishes planning, the curve has already bent again.


I first learned this over 20 years ago—Kurzweil rewired my thinking

At a Ray Kurzweil talk at MIT in the mid-2000s, he described the “Law of Accelerating Returns.” It permanently rewired how I think about the pace of technology change.

He wasn’t the first to notice this pattern:

  • Henry Adams – law of acceleration
  • Buckminster Fuller – ephemeralization (doing more and more with less and less)
  • Moore’s Law – exponential chip complexity
  • Hans Moravec – robotics advancing at Moore’s-law speed

Kurzweil unified and expanded these ideas to encompass all technology and evolution—and even applied them to his business strategy. He claimed that he began designing products years ahead of time, and calculating when the enabling technologies would be available. He developed a photocopier-sized text scanner for the blind in the 70s, and began designing his handheld version of the same soon afterwards. He was in production within months of when the enabling tech was finally small and performant enough to work for the product. Is it true? I don’t know – but the fact that it would be a striking example of true exponential thinking demonstrates how rarely it occurs.


Critics point to Kurzweil’s dates being off in some cases by a decade. But I would argue that in most cases, the limiting factor wasn’t technological capability—it was political will, regulation, or distribution. Exponential growth of technical capability is the rule rather than the exception. Rapid adoption of what's possible is the exception rather than the rule.

As William Gibson said: “The future is already here—it’s just not evenly distributed.”

It's never been more true. An example would be that Kurzweil's predictions for 2009 (made in 1999!) included “self-driving cars”. While not available to consumers in 2009, Google had, in fact, successfully logged over 200,000 miles with their self-driving technology by 2009, and Nevada was putting self-driving vehicle laws on the books. That future wasn't yet evenly distributed.


Today’s AI acceleration makes those early curves look quaint

Consider just a few signals as outlined in the Stanford AI Index Report 2025[1]:

  • Hardware costs have been dropping 30% per year
  • Energy efficiency has been improving 40% per year

And then on the software and training sides of the equation:

  • Google’s Gemini 3.1 showed that models can still gain intelligence through smarter training—not just more parameters as the recent trend had been (combine smarter training with more parameters, and there's no reason for the capability curves to flatten out yet)
  • Breakthroughs (like Mixture-of-Experts, 1-bit quantization, the tabular foundation model, etc.) emerge constantly

And finally, practitioners are learning new ways to get the most from the tools, and increasing efficiency while reducing costs:

  • I code with AI completely differently than I did a few months ago.
  • And I expect the same a few months from now.

Every layer of the ecosystem is growing. And doing so faster.


10X improvement per year changes everything

Most of my clients invest with a 3–7 year horizon. If AI capability continues at the ~10X per year that we’ve seen since at least GPT2:

  • 3 years → 1,000X more capable
  • 7 years → 10,000,000X more capable

Even “only” 5 more years of this curve gives you 100,000X improvement.

Put simply: software moats have largely evaporated over the past year.

  • In a recent diligence project, I replicated ~80% of the target’s product in a single weekend (in spare time) for something like $60 of Claude Code time. When the target wrote the product two years ago, it was ground-breaking. Now it was a weekend’s part-time work.
  • Another colleague did something similar on a recent project.
  • We’re both experienced software developers, and deeply ensconced in the context engineering rabbit holes. But a motivated junior engineer could very likely do this in under a week.

It's never technology, always psychology

My colleagues and I have successfully used context engineering principles and the latest generation of AI coding tools and LLMs to:

  • rebuild significant legacy systems into modern stacks with full test infrastructure and mature coding practices
  • build greenfield apps at unbelievable speed with legit UI frontend work
  • create agents, skills, commands, and developer workflow tools to further accelerate our own work with these tools
  • analyze legacy codebases and plan monolith decomposition and modularization
  • read, analyze, and fix bugs in open source projects
  • develop documentation and visualization for codebases, with no prior exposure to the code

The hardest part?

Change management. Humans can’t mentally accelerate at the same rate as the tools.

Rote tasks? AI is already there. That future just isn’t yet evenly distributed. Creative tasks? They’re next.


So what should you do?

Three things matter more than ever:

  1. Master the tools
  2. Stay flexible and experiment constantly
  3. Build moats around relationships, distribution, and trust—not code

Because the curve is still bending upward. And it’s bending faster than most people realize.


[1] Nestor Maslej, Loredana Fattorini, Raymond Perrault, Yolanda Gil, Vanessa Parli, Njenga Kariuki, Emily Capstick, Anka Reuel, Erik Brynjolfsson, John Etchemendy, Katrina Ligett, Terah Lyons, James Manyika, Juan Carlos Niebles, Yoav Shoham, Russell Wald, Toby Walsh, Armin Hamrah, Lapo Santarlasci, Julia Betts Lotufo, Alexandra Rome, Andrew Shi, Sukrut Oak. “The AI Index 2025 Annual Report,” AI Index Steering Committee, Institute for Human-Centered AI, Stanford University, Stanford, CA, April 2025. https://doi.org/10.48550/arXiv.2504.07139