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

推荐订阅源

Y
Y Combinator Blog
P
Palo Alto Networks Blog
阮一峰的网络日志
阮一峰的网络日志
博客园_首页
Last Week in AI
Last Week in AI
Blog — PlanetScale
Blog — PlanetScale
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
J
Java Code Geeks
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园 - Franky
The Cloudflare Blog
I
Intezer
P
Privacy International News Feed
C
Check Point Blog
C
CERT Recently Published Vulnerability Notes
Apple Machine Learning Research
Apple Machine Learning Research
H
Hackread – Cybersecurity News, Data Breaches, AI and More
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
The Hacker News
The Hacker News
B
Blog
Latest news
Latest news
小众软件
小众软件
Engineering at Meta
Engineering at Meta
Cyberwarzone
Cyberwarzone
Project Zero
Project Zero
P
Proofpoint News Feed
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
S
Schneier on Security
美团技术团队
G
GRAHAM CLULEY
博客园 - 司徒正美
T
Threatpost
D
Darknet – Hacking Tools, Hacker News & Cyber Security
博客园 - 叶小钗
C
Cisco Blogs
MongoDB | Blog
MongoDB | Blog
人人都是产品经理
人人都是产品经理
博客园 - 三生石上(FineUI控件)
H
Help Net Security
Simon Willison's Weblog
Simon Willison's Weblog
Cisco Talos Blog
Cisco Talos Blog
K
Kaspersky official blog
NISL@THU
NISL@THU
AWS News Blog
AWS News Blog
T
Threat Research - Cisco Blogs
月光博客
月光博客
Security Latest
Security Latest
Scott Helme
Scott Helme
T
Tenable Blog

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
Cicada Crowdsolving as Externalized Insight: Distributed Puzzles and the Neuroscience of the Aha
Alex @ Vibe Agent Making · 2026-06-24 · via DEV Community

On January 4, 2012, a plain image appeared on 4chan: white text on a black field. "Hello," it began. "We are looking for highly intelligent individuals. To find them, we have devised a test." What followed, under the name Cicada 3301, became the most elaborate puzzle the internet has ever chased: a year-long descent through hidden messages in images, book ciphers, runes, cryptographically signed clues, music, and physical posters taped to walls in fourteen cities on four continents. The puzzle wanted individuals. It said so. By some accounts it eventually reached out to the people who finished, privately, one at a time, and those people went quiet.

But look at who actually did the solving. Not lone geniuses in candlelit rooms. A swarm: thousands of strangers on Reddit, 4chan, IRC channels, and a shared wiki, pooling clues, arguing, logging dead ends, building on each other around the clock. A puzzle built on the romance of the singular mind was cracked, over and over, by a crowd.

Here's why that should bother you, in a productive way. Neuroscience is fairly clear that the thing we call an aha-moment is profoundly, irreducibly individual: it happens in one brain, and it can't be averaged into existence by a committee. So if a crowd literally cannot have a eureka, how did the crowd keep winning? That mechanism is one of the more useful things you can know about how breakthroughs actually get made, on a puzzle forum, in a research lab, or on your team.

What an aha actually is, and what it needs

Start with the moment itself, because it's stranger and more specific than "a good idea popped into my head."

In a 2004 study in PLoS Biology, Mark Jung-Beeman, John Kounios, and colleagues caught the aha in the act. When people solved word puzzles by sudden insight (rather than by methodical analysis), there was a sharp burst of high-frequency gamma activity in the right anterior superior temporal gyrus, about 300 milliseconds before the solution reached awareness, a neural signature with no equivalent in step-by-step solving. Even more telling: roughly 1.5 seconds before that, there was an alpha-band "blink" over the visual cortex, as if the brain briefly dimmed its own sensory input to protect a fragile internal signal. Insight begins by looking away from the world. It is one brain, going quiet, alone.

A century earlier, Graham Wallas (1926) had already mapped the journey to that moment in four stages: preparation (work the problem until you hit an impasse), incubation (step away; let it sit), illumination (the aha), and verification (check that it's actually right). Modern work fills in the mechanism. The psychologist Stellan Ohlsson describes an impasse as a wrong representation, you've framed the problem in a way that structurally excludes the answer, which breaks only when you relax a false constraint or decompose a "chunk" you'd been treating as atomic. And, crucially, the dead ends are load-bearing: without enough failed attempts straining the bad representation, it never restructures. You have to get properly stuck before you can get unstuck.

Now the cruel part, the part that makes insight so hard to manufacture: your own expertise is the cage. Karl Duncker's candle problem showed "functional fixedness": we can't see a matchbox as a shelf because we know too well that it's a box. The Einstellung effect shows that experience carves cognitive grooves that actively resist restructuring; the more you know, the more your mind insists on the familiar frame. Tellingly, more distractible people tend to be better at insight, because broad, unfocused attention surfaces the distant associations a breakthrough needs. And incubation rewards stepping away, not grinding: in one well-known study (Wagner and colleagues, 2004), a night's sleep more than doubled the rate at which people discovered a hidden shortcut in a number task (about 59% versus under a quarter). Insight is weirdly anti-effortful. Over-focus and anxiety block it.

One honest caveat: not everyone agrees insight is a distinct process. Robert Weisberg has argued it's really just fast, ordinary analysis. We don't need to settle that here. The argument that follows only needs two things that are well-supported: insight is discontinuous (it arrives as a reframe, not a smooth accumulation), and it is fixation-bound (your existing frame is what's in the way). That's enough.

Because those two facts are exactly what a crowd is built to exploit.

The crowd externalizes the stages, but not the aha

Watch what the Cicada solvers actually did, and you'll see Wallas's stages turned inside out, taken out of the private skull and spread across a public network.

Preparation became a public, permanent artifact. Every clue, cipher, and theory, and (this matters most) every failed attempt, went into the shared wiki and the forum logs. In a single brain, the load-bearing dead ends decay (and that forgetting actually helps clear fixations). In the crowd, they're written down forever. Nobody has to re-suffer a dead end someone else already hit; every newcomer arrives to a map of the constrained solution space, the false trails already marked. The "preparation" stage stopped being something each person redid and became a commons.

Incubation got parallelized across thousands of differently-stuck minds. This is the load-bearing move, so precision matters here. An individual incubates by relaxing, stepping away so a fixation can fade. A crowd can't relax on command. What it does instead is distribute: at any hour, some people are grinding, others are asleep, joking, idle, or arriving completely fresh. The collective is therefore never as stuck as any single member, and a steady stream of new minds, each carrying a different fixation, keeps cycling through the shared problem. Remember that your expertise is the cage. The beautiful consequence: no single fixation dominates a thousand differently-caged minds. The probability that somebody happens to be free of the exact wrong assumption, the cryptographer who thinks in stego while everyone else is stuck on hex, the musician who hears a pattern the coders can't, climbs toward certainty. The crowd is, in effect, collectively distractible: broad, unfocused, association-rich attention, externalized across people.

The restructuring still happens in one skull. And this is the line not to blur. The breakthrough ("wait, it's not a hex dump, there's data hidden in the image itself") is still a single brain's gamma burst, one person's aha. The crowd does not have a collective eureka; there is no distributed temporal lobe lighting up in unison. What the network does is catch that one-skull insight and make it everyone's in seconds: the post goes up, and the whole swarm pivots. The aha is individual; its propagation is what got externalized.

And verification got socialized, which is the crowd's quietest superpower. Here's the thing about your own aha: it lies to you about its reliability. The flash of insight is, in part, a dopaminergic metacognitive signal, it arrives wearing a costume of certainty. But certainty isn't correctness, and a single brain is terrible at auditing its own confident ahas (this is the engine of every rabbit hole). A crowd can do what no lone solver can: demand the method. In rigorous puzzle communities the norm is blunt: as the cryptographers around Kryptos like to put it, if you can't show your work, you get booed out of the room. Cicada's clues were even GPG-signed so the crowd could tell authentic next steps from the swarm of hoaxes. The graveyard of confident-but-wrong theories is real, but the social "prove it" reflex is the error-correction stage that an individual brain runs internally and badly, now run out loud by many.

This is not the wisdom of crowds

If you're nodding along thinking "right, wisdom of crowds," stop, because it's the opposite, and the difference is the whole point.

The wisdom of crowds, in the Galton-ox-weight sense, works by averaging. Eight hundred fairground guesses at the weight of an ox, and the mean lands almost exactly right, beating nearly every individual. It's a statistical magic trick that smooths independent errors into an accurate estimate. It is fantastic for estimation.

Insight is the enemy of the average. A breakthrough is a single, discontinuous reframe by one outlier mind. Average a thousand wrong representations of a problem and you do not get a restructuring; you get a slightly blurrier wrong representation. The mean of "it's hex," "it's base64," and "it's a book cipher" is not "it's steganography"; it's noise. So crowdsolving-for-insight cannot be drawing its power from the mean. It draws power from three completely different sources:

  • the max, the single best brain that happens to break the right fixation (you're not averaging the crowd, you're fishing in it for the one outlier);
  • the shared memory, the permanent, public log of dead ends that keeps the whole crowd's search efficient and cumulative;
  • the error-correction, the social verification that filters the flood of false, certain-feeling ahas.

Max, memory, and verification, not mean. The crowd's job isn't to vote on the answer. It's to maximize the number and diversity of minds incubating on a shared, externalized problem, so that the singular aha becomes statistically inevitable, and then to catch it and check it. The crowd is a fixation-diversity engine bolted to a shared scratchpad and a bullshit detector. That's a fundamentally different machine than a poll.

Bletchley already knew

The deflating, wonderful truth is that none of this was new. Cicada relearned, the hard way, something that had been institutionalized seventy years earlier.

When Britain assembled Bletchley Park to break German ciphers, it didn't hunt for the single greatest mathematician and lock him in a room. It recruited a deliberately diverse crowd: mathematicians, yes, but also linguists, chess champions, crossword setters and solvers, classicists. The recruiters intuited exactly what insight research would later formalize: a hard reframe is a lottery, fixation is the enemy, and the way you beat fixation is to put many different kinds of stuck-ness in the same room, so that whatever the problem's hidden structure proves to be, someone's particular mind is shaped to catch it. Diversity of fixation breeds restructuring. Bletchley bought lottery tickets in bulk.

Cicada, premised on the lone-genius myth, was solved by the same principle running wild and leaderless on the open internet, which is the irony worth sitting with. The puzzle-setters believed in the singular mind. The crowd proved that almost everything around the singular mind, the preparation, the incubation, the propagation, the verification, can be externalized, and that doing so turns the rare lottery win of individual insight into something close to a reliable process.

What to do with this

The practical payoff, if you build teams or systems meant to crack hard problems, is concrete and a little counterintuitive.

Don't optimize for the genius. Optimize for fixation-diversity. The instinct to hire ten more people who think exactly like your best engineer is the instinct to buy ten copies of the same lottery ticket. The next reframe will come from the person whose background means they don't share your team's central blind spot, so recruit, and protect, the ones who are stuck differently than everyone else.

Build the shared, permanent scratchpad, and log the dead ends, not just the wins. A breakthrough culture treats "here's what I tried that didn't work" as a first-class contribution, because that's the load-bearing failure that stresses the bad frame and saves everyone from re-suffering it. Most teams throw that away. The Cicada wiki's real engine was its graveyard.

Make "show your method" a norm, not an insult. Your team's confident ahas are lying to a predictable fraction of the time, because that's what the certainty signal does. The cheapest possible upgrade to a group's accuracy is the social reflex to ask, warmly and always, can you show how you got there? That is the verification a single mind cannot reliably run on itself.

And maybe the gentlest takeaway: the breakthrough will still happen in one quiet skull, going dark for a second and a half to protect a fragile signal. You can't manufacture that flash. But you can build the room around it, diverse, well-stocked with shared memory, and honest enough to check its own certainty, so that when one of those flashes finally comes, you've made it almost inevitable, and you don't miss it when it does.


The crowd's quietest superpower is socialized verification: "can you show how you got there?" An AI agent's flash of certainty has the same costume and the same failure rate, and a single run can't reliably audit itself. **Chain-of-consciousness* records an agent's reasoning as it works, so the method is on the record and a confident-but-wrong aha leaves a trail you can check.*

pip install chain-of-consciousness · npm install chain-of-consciousness

Hosted Chain-of-Consciousness · vibeagentmaking.com


Originally published at vibeagentmaking.com.