Who He Is
Steve Newman has been writing code since 1985. He built Writely (later sold to Google, becoming Google Docs), and has lived through every cycle of the internet from dial-up to generative AI. In 2026, at over 60 years old, he appeared on the Cognitive Revolution podcast and was asked how he uses AI for coding. His answer caught the host off guard:
> "The agent's not important. I'm important."
He wasn't speaking in clichés. He is one of the few people who, when discussing how to use AI, opens not with "productivity gains" but with "who am I."
---
Six Judgments
Below are six takeaways—not platitudes, but a 40-year veteran restructuring his workflow with unusual clarity.
1. AI should first filter the input, not take over your life
Steve's first tool is called the Attention Firewall. Its single job: before he starts working, separate "what should be seen" from "what shouldn't." Not a recommendation algorithm guessing what you like, but filter rules he defines himself—deciding what isn't even worth entering his attention. This is the opposite of "AI helps me do more." It's "AI helps me not do."
> Core insight: In an information flood, deciding what NOT to receive matters more than deciding what to receive.
2. Don't turn yourself into an AI attendant just to max out tokens
Steve explicitly opposes tokenmaxxing—a term he coined for endlessly tweaking prompts, stacking context, and pushing models to output more in the name of "squeezing out model capability." He compares it to staring at the calorie meter on a treadmill: you're moving, but you've forgotten why. He doesn't know TypeScript and never reads AI-generated code. He only makes high-level decisions: framework, direction, boundary conditions. If the AI gets something wrong, he senses it and redirects. He is not AI's "supervisor"—he is AI's principal.
> Core insight: Tokenmaxxing is an anxiety-driven behavior pattern; at its root, it's doubt about one's own value.
3. Real AI-assisted coding starts with small tools
Steve doesn't use one "super agent." He built over a dozen bespoke tools:
- Attention Firewall → filters his attention input
- Reading App → a reader for surfacing new ideas
- Coding-Agent Dashboard → monitors AI coding tasks
- Chrome Extension → browser-layer assistant
- Universal Logging → logging across all tools
- Mirror → unified view aggregating 7+ data sources
- He doesn't believe "AI will do everything for me"
- He doesn't believe "more complex prompts are better"
- He believes: AI is a resource that must be managed, and the person managing it must have clear self-boundaries.
- Cognitive Revolution podcast: "Vibe-Coding an Attention Firewall, w/ Steve Newman" (2026-04-19)
- Steve Newman's site: secondthoughts.ai / the "Hyperproductivity" essay
- Jesse Vincent: Superpowers (compounding teams / TDD for skills)
- Liu Xiaopai vibe coder case (generating 10,000 domains)
None of these tries to "disrupt" anything. Each solves one specific problem, and together they form a complete personal operating system.
> Core insight: Not "find one universal tool" but "give every fragment a clear owner."
4. Creators need a topic radar, not auto-writing
Steve's Reading App exists not to "read faster" but to find topics worth creating. His logic: generative AI can package junk beautifully, but it can't come up with genuinely valuable ideas for you. Topic selection—knowing "what is worth doing"—is the creator's last moat.
> Core insight: The bottleneck in content production isn't writing ability; it's judgment.
5. Automation can be fast, but the evidence chain must stay intact
Steve runs a universal logging system plus a methodology he calls TDD for skills. When AI completes something, you must be able to trace every step—not out of paranoia, but so that when AI screws up, you know where. Applying TDD to skills: he first writes an "expected result," lets the AI attempt it, checks the gap, and repeats the loop until the AI handles that specific task reliably.
> Core insight: Trust has limits. Trust presupposes verifiability.
6. The people who thrive will build themselves a personal operating system first
Steve writes in his essay "Hyperproductivity":
> "The bottleneck isn't AI capability; it's human imagination in how to use it."
His personal OS isn't one piece of software—it's the combination: attention management + anti-tokenmaxxing mindset + a matrix of small tools + topic radar + evidence chain + continuous iteration. Jesse Vincent's (author of Superpowers) Compounding Teams—using tools to improve tools—describes the same idea. Liu Xiaopai's case is more extreme: a vibe coder generating 10,000 domains with AI and then picking among them—a "mass generation + human filtering" pattern that is becoming a new paradigm.
But Steve is honest about one thing: this way of working is exhausting. "You can never settle into a routine."
> Core insight: A personal operating system isn't a productivity tool—it's a way of being.
---
Why These Judgments Matter
What makes Steve Newman special: he's not an AI practitioner, not a prompt-engineering influencer, not selling courses. He's someone doing real work with AI, after four decades in tech. His words carry no hype:
"I'm important" isn't ego—it's a validated observation: when you turn yourself into an AI attendant, you eventually lose both your work and yourself.
---