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

推荐订阅源

S
Schneier on Security
Security Archives - TechRepublic
Security Archives - TechRepublic
T
Threat Research - Cisco Blogs
G
GRAHAM CLULEY
P
Privacy & Cybersecurity Law Blog
C
CXSECURITY Database RSS Feed - CXSecurity.com
Cisco Talos Blog
Cisco Talos Blog
The Hacker News
The Hacker News
L
Lohrmann on Cybersecurity
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
C
Cyber Attacks, Cyber Crime and Cyber Security
Security Latest
Security Latest
Know Your Adversary
Know Your Adversary
P
Palo Alto Networks Blog
C
Cisco Blogs
AWS News Blog
AWS News Blog
T
Threatpost
L
LINUX DO - 热门话题
Simon Willison's Weblog
Simon Willison's Weblog
Scott Helme
Scott Helme
C
Cybersecurity and Infrastructure Security Agency CISA
T
Tor Project blog
Cyberwarzone
Cyberwarzone
P
Proofpoint News Feed
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
T
The Exploit Database - CXSecurity.com
The Register - Security
The Register - Security
D
Darknet – Hacking Tools, Hacker News & Cyber Security
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
罗磊的独立博客
云风的 BLOG
云风的 BLOG
V
Vulnerabilities – Threatpost
N
News | PayPal Newsroom
Project Zero
Project Zero
NISL@THU
NISL@THU
博客园_首页
MyScale Blog
MyScale Blog
V2EX - 技术
V2EX - 技术
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
F
Full Disclosure
T
Troy Hunt's Blog
Recorded Future
Recorded Future
N
Netflix TechBlog - Medium
P
Privacy International News Feed
H
Hackread – Cybersecurity News, Data Breaches, AI and More
A
Arctic Wolf
C
Check Point Blog
W
WeLiveSecurity
Apple Machine Learning Research
Apple Machine Learning Research
C
CERT Recently Published Vulnerability Notes

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
The Man Who Summoned Ghosts | Coda: The Next Five to Ten Years
Lei Hua · 2026-05-14 · via DEV Community

The Man Who Summoned Ghosts | Coda: The Next Five to Ten Years cover

What the next five to ten years ask from anyone trying to stay useful in the AI era.

Originally published on Lei Hua's Substack.

This coda follows the four-question template from references/future_projection.md:
(1) the enduring core → (2) current pressures → (3) 3–5 likely decision points → (4) the questions facing this archetype.


Honest Disclaimer

This section is structured extrapolation from public materials — not prediction. If you re-read this in two years, some of these projections will not have happened — that's expected. The purpose of this book is not to bet on the future, but to give you a lens for watching change.
Treat this as a meditation, not a forecast.


I. The Core We Have Already Established

After chapters one through six, four things can be said with reasonable confidence to be Karpathy's true and stable core — they survived the entire 2022–2026 turbulence unchanged.

  1. Minimalism, readability, the demystification of the training stack. From nanoGPT to nanochat to microGPT — three generations of "the most complete thing in the fewest lines of code." It is a technical aesthetic and a moral posture: he refuses to let frontier models look like magic.

  2. The dignity of education. Across all of his public work, this is the most monotonically strengthening thread. Eureka Labs is not a business; it is the material form of this line.

  3. An allergy to hype. As early as State of GPT in 2023 he was saying "low-stakes + human-in-the-loop"; the 2025 "slop" and "march of nines" are the same caution at higher volume.

  4. A preference for open and pluralistic ecosystems. 2024's "coral reef" became 2026's "build RL environments in verifiable domains labs haven't claimed." The romance turned into tactics, but the anti-concentration, anti-monopoly underlay never moved.

Any projection about his next moves must respect these four. He will not suddenly join a frontier lab. He will not suddenly become a hype machine. He will not put down education to return to pure research. He will not sit quietly in a world swallowed by five mega-corps.


II. Forces Currently Pressing on That Core

In the last 12 to 18 months, he has been publicly responding to at least four specific pressures:

  1. The scaling problem of agentic engineering — agents now write 80% of code, but jagged intelligence makes the remaining 20% especially expensive. The trade-off between the quality bar and the speed bar is something he faces every day. This pressure was repeatedly touched on in Sequoia 2026.

  2. Productization pressure on Eureka Labs — the LLM-101-N course, announced in 2024, was still not widely launched by 2026. Education is slow; but slow and dead are separated only by a single string of product rhythm. As a founder, he must make Eureka a company, not just a mission statement.

  3. The cost of public language — the Dwarkesh episode positioned him as "the popper of the AI bubble," a label he explicitly rejected in his X clarification, but could not fully control. As a public thinker, he must choose: continue to speak sharply and accept being flattened, or soften the edge and lose the singular position of an internal critic.

  4. Further reshaping of his personal working style — he has already conceded "AI psychosis." As agents increasingly write code and conduct research, the pleasure of being an independent thinker is itself being altered. This is an existential pressure no one else can think through for him.


III. 3–5 Likely Decision Points in the Next 5–10 Years

Each decision point is anchored in the core + the current pressures above. They are not predictions. They are the choices people of his archetype are most likely to face.


Eureka Labs' shape

What it is: Eureka Labs aims to deliver "a 1-on-1 AI tutor for every student" — he learned Korean this way, he told Dwarkesh. To turn that experience into a scalable, durable company, he must choose among three shapes: a B2C mass product, a B2B school/enterprise sale, or a high-end tool around his own course content.

Why it's likely: The unresolvable tension in the business model of education companies is something every education founder faces. His expressed preference leans B2C, but B2C education's customer acquisition cost is notoriously high.

Possible directions: (a) B2C at mass scale, requiring a new teaching economics; (b) becoming a "tool company" for his own courses — small but durable; (c) selling to education departments or big platforms while retaining course IP.

Signals to watch: Does Eureka raise funding rounds? At what valuation? Does it begin hiring sales/partnerships staff beyond enrollment?


How to manage relations with frontier labs

What it is: He called frontier model code "slop" on Dwarkesh. But his own next-stage research (AutoResearch, microGPT) still depends on frontier models. As an independent educator-and-internal-critic, how does he handle his dependence on the very things he criticizes?

Why it's likely: OpenAI / Anthropic / Google are simultaneously his tools and his targets. The tension will keep accumulating.

Possible directions: (a) stay permanently independent, pay API fees, criticize publicly; (b) form a "critic-allied" relationship with one specific lab; (c) shift toward an open-source / open-weights model ecosystem as his working foundation.

Signals to watch: Does he start recommending open-weights models more explicitly? Does he join any lab's advisory board? How does he interact in public with Sutskever / Dario / other frontier lab leadership?


Whether to accept another "inside" role

What it is: He has left OpenAI twice. He probably believes he won't return — but the boundary between independent educator and frontier researcher is blurring. If a lab tomorrow offered him a senior role on education/alignment/interpretability research, while letting him keep Eureka Labs, what would he do?

Why it's likely: Historically he has done "in-out-in" twice (Stanford → OpenAI → Tesla → OpenAI → Eureka). The pattern is not definitively over.

Possible directions: (a) decline, citing Eureka's need for full-time attention; (b) accept a part-time / advisor role; (c) accept a formal role with the right to leave.

Signals to watch: Does his commentary on internal lab work change in tone? How dense is his collaboration with any specific lab?


Finding a sustainable work ethic at the cost of "AI psychosis"

What it is: He has admitted that "sixteen hours a day directing my will at agents" leaves him in a mild psychotic state. That state is not sustainable on a two- or five-year horizon. He must either find a new equilibrium with agents, or consciously slow down.

Why it's likely: Any way of working reshaped by a new tool needs a stable equilibrium. Otherwise the cost spills from the psychic into the physiological.

Possible directions: (a) discover a rhythm that alternates agent-driven work with deep human thinking; (b) push 16 hours back to 8, accepting less output; (c) publicize the question itself, making "human mental health while working with agents" a research theme inside Eureka.

Signals to watch: Does he start writing about work ethics in his blog or interviews? Does his own output rhythm visibly slow or restructure in 2027–2028?


How his judgment will change if AGI actually arrives

What it is: He currently says "AGI is still a decade away." If a genuine capability leap occurs before 2030 — say, a model that approaches human level across nearly all verifiable domains — how will he recalibrate? This is the harshest test for a public thinker: when your prediction is wrong, what do you do?

Why it's likely: Not because he is certain to be wrong — he might not be. But he must preserve a posture for elegantly admitting error.

Possible directions: (a) publicly acknowledge the timeline error in an "I was wrong" blog post (which fits his honesty); (b) redefine the term so he isn't "wrong" (which doesn't fit his honesty); (c) further split his judgment — "core intelligence has arrived, but AGI as economic impact is still in the march of nines."

Signals to watch: His first reaction, in any blog / X post in the first week after a major capability leap. That post will be the most important next primary source for this biography.


IV. People of His Archetype — And You

If you have read this far, this section is for you.

People of Karpathy's archetype share a recognizable pattern: technical insiders who refuse a purely technical identity; public speakers who refuse hype; one eye on the code, the other eye on education, ethics, ecosystem. This type will not disappear in the AI era — they will become more important, because they are translators.

But this type will also face, in the next 5–10 years, a handful of nearly unavoidable shared questions:

Question 1: When new tools invert your way of working, how do you keep authorship? Karpathy reported "agents write 80%" — that's a question about working style, but it's also a question about identity. Anyone whose self has been built on making things by hand must, once agents take over, answer again: "What am I actually doing now?"

Question 2: How do you hold the middle, between hype and denial? After Dwarkesh, Karpathy was pushed toward the "bubble-popper" label, which he himself refused. But holding the middle requires re-clarifying every few months — a continuous tax on attention. Anyone trying to be a "sober insider" will pay this tax.

Question 3: When your field moves faster than you, where does your dignity come from? Not from outrunning the tool — you can't. It comes from how you live with the tool — replaced by it, or extending yourself with it. Karpathy chose the second, at the cost of his own "AI psychosis." That path is yours to walk too.

Question 4: Will education really become "the gym"? Or will it disappear? Karpathy's core bet is the former — that post-AGI education resembles today's gym: for fun, for health, for self-dignity. But this bet might not hold. Education could also become a luxury good, a class marker, something out of reach for ordinary people. The fundamental question for educators of his generation is whether the "gym future" of education is actually an egalitarian future.


The Question Left on the Table

If only one question can be left at the end of this book, for you to carry back into your own life, it is this:

In a world moving faster than you, what kind of person are you willing to become?

Karpathy's answer is a specific posture — keep working, keep recalibrating, publicly admit what you got wrong, and don't surrender the core inside you that hasn't changed. That is not the answer. It is one version of the answer.

The point of this book is not to persuade you to agree with him. It is to invite you, with the same clarity — same lack of drama, same honesty, same refusal of both the hype glasses and the denial glasses — to think about your own next step.

May you, in this era, recalibrate gracefully.


Sources

This coda draws on all the materials cited in the previous six chapters. Its judgments are induced from those materials alone, with no new external sources introduced. For verification, see the sources list at the end of each chapter.