Wednesday, October 7, 2026ArchiveSearchAsk the paper

The Computomatix Times

All the posts fit to save — curated from @computomatix's bookmarks & likes on X

Steve Yegge Proposes Agentic Technical Program Managers for Enterprises

Steve Yegge argues that AI agents acting as technical program managers, who drive projects without direct authority, could be the most direct route for coding agents into enterprises. He describes his own agent-based TPM seats in his Wheelhouse factory that use email, Slack and nagging to drive projects, and links to his site.

Original post · 4 min read
Hear me out: Agentic TPMs (Technical Program Managers.) I had this idea in Sydney while chatting with Martha McKeen at CBA. I think this winds up being the most immediate and direct way that coding agents can make their way into the enterprise, and it will set the stage for true AI employees rolling in next year.

So. Build-side agents are great but they don't escape the SDLC. Only devs are using them. There are a handful of business people vibe coding SaaS, but for the most part, non-engineers aren't using coding agents to help with their jobs. Right? Not yet.

Autonomous 24x7 unmanned queue-based "operator" agents, like the ones that handle internal or external customer issues, are great. But they are narrowly scoped, and generally require devs involved to set them up and maintain them.

Neither builder nor operator agents are automatically going viral internally and helping run the company. They stay in their lanes. But what if their lane was to help run projects?

I was a TPM at Amazon in 1999. Bezos brought in high-powered engineers with people skills to run difficult cross-functional projects and programs. TPMs are used at Google, Uber, Netflix, and other companies, and they are always in high demand and short supply.

I have a class of agents in my Wheelhouse factory that act just like TPMs. They have external email and Slack, and talk to my accountant, lawyers, players. Each one has a project lane and drives it. They use Progress By Nagging, which... works.

A TPM owns delivery, but has no authority, and no resources. They can only ask, observe, document, and report. This is just like my TPM Wheelhouse seats, who have been helping me drive dozens of projects to completion, large and small, for months.

Agents, particularly smarter models, will go to great lengths to document the hell out of everything in the domain where they're operating. They'll capture all the tribal knowledge and unwritten rules. They can create topological maps of your project, org dependencies, and workflows. They'll bulldoze through silos and knowledge-hoarders and figure out how the company actually works, and document it all. And nag people along the way.

This kind of agent sits well in constraint-space. They're cheap: You don't need to use the fanciest models; anyone with Opus or Sol access could have a TPM agent. And TPM agents have low risk and blast radius, because they cannot act. Unlike builder agents, which create new problems (like merge-queue and code-review bottlenecks), TPM agents simply shine a light on the org, and nudge things along.

It doesn't matter what format they're recording their findings in. It could be Sanskrit and hieroglyphics. When it comes time to merge their findings with those of other TPM agents, it will all translate trivially into your company brain.

Anyone in the company can stand up a TPM agent. It's like a personal chief of staff. There's no dependency on engineers. Everyone can do it; it doesn't even have to have a paced rollout. And there's no product to buy, no tech to install, maybe just a Skill you give people. Maybe you put a company wrapper on it. But it's just an agent that's playing the TPM role.

TPM agents will wind up training human orgs on human-agent interactions. Humans start getting emails or DMs from agents, work-related, and will have to get comfortable replying and interacting. Companies can push the social side along without waiting for engineers to finish messing with the SDLC, which honestly will never finish.

Other kinds of agents struggle at enterprises because they lack context. TPM agents will build that missing context as their exhaust, no joke; they've done it for my game without me even asking. TPM agents are the jungle explorers that will map out your organization, and you'll discover all sorts of fun stuff, like that you had 3 teams doing the same thing. TPM agents are a low-risk, high-impact way to start figuring out how AI can help you run your project, or organization.

I'll write a blog post about this, but feel free to start now. Go! Just give me credit when you win big with this idea. And if you want my help, ping me on yegge.ai.
♥ 466 · ⟲ 33 · 👁 42.9KView on X ↗

More in Agents & Dev Tools

Developer Rebuilds Seven Adobe Apps in Rust Using Opus 5.5

Peter Yang highlights a developer who reimplemented seven Adobe apps, including Photoshop, Premiere and Lightroom, in Rust with Claude Opus 5.5 and open-sourced them. The developer believes they can match Adobe's features within months, against Adobe's $840 yearly all-apps plan.

Original post · 1 min read
It's insane to watch AI blow apart closed source software and games.

4 examples from the past month:

1. 7 of Adobe's biggest apps, including Photoshop, Premiere, and Lightroom, have been partially rebuilt in Rust with Opus 5.5 and open sourced. It's still early, but the developer thinks they can match Adobe's features within months. Adobe's all-apps plan costs $840/year.
Miguel Ángel Durán @midudev
Todos los productos de Adobe reimplementados desde cero, gratuitos y de código abierto

→ getartcraft.com/apps
♥ 50 · ⟲ 2 · 👁 10.7KView on X ↗

Vercel's Guillermo Rauch Explains Turborepo's Migration From Go to Rust

Guillermo Rauch says Vercel moved Turborepo from Go to Rust, a migration that was controversial internally due to human costs. He argues that with AI agents the calculus has changed, so what is best for humans is no longer necessarily best for business.

Original post · 1 min read
DHH is fundamentally right about Rust. For context, Vercel has been undergoing a Rust-ification (carcinization, technically 🦀) for a while.

One of the first projects we migrated was Turborepo, from Go to Rust¹. The migration completed, but the RoI was actually quite controversial internally.

While Rust was in our eyes better for low-level OS access, something crucial for a build system like Turbo, the human migration costs were very sustantive.

Go is very fast. It's beautifully designed. It's easy to iterate on. We were very conflicted about the migration, because it was *humans* writing the code, *even if we knew Rust was a better choice*.

The calculus has now changed. What's "best for humans" is no longer necessarily "best for business".

FWIW, it's also quite unlikely that Rust is the end-all-be-all toolchain. I'm quite certain there's greener pasture ahead, because Rust itself was designed before the 'supersonic tsunami' of agents hit.

¹ https​://vercel.com/blog/how-turborepo-is-porting-from-go-to-rust
♥ 3.2K · ⟲ 152 · 👁 352.7KView on X ↗

Integer Multiplication Algorithm Bound Tightened Repeatedly With Astra

A post reports that a user running ChatGPT Astra in a loop is repeatedly breaking records for integer multiplication algorithms. It quotes an update to OpenAI problem #109 that tightens the constant from 2^-182 to 2^-59, a roughly 500,000-fold improvement over the previous result.

Original post · 1 min read
This guy has 6.1 Astra running in a loop and is breaking the record for integer multiplication algorithms every few hours lmaooooo.
Doug Colkitt @0xdoug
We are publishing an update to OpenAI problem #109 Integer multiplication) with another substantial further tightening:

κ = 2⁻⁵⁹ (from OpenAI’s original κ = 2⁻¹⁸²)

Approximately 500 thousand fold improvement over our previous result and a 2¹²³ fold improvement over the original OAI result.

The latest redesigned the finite network to share intermediate computations and scratch space, then tightened the recursion and Gaussian estimates.
♥ 4.1K · ⟲ 118 · 👁 167.4KView on X ↗

Boris Cherny Says Prompting Claude Should Feel Like Talking to a Coworker

Boris Cherny explains his approach to prompting Claude, advising users to give clear goals, specify effort level and verification steps rather than relying on heavy scaffolding.

Original post · 1 min read
I am surprised that people are surprised this is how I prompt Claude.

Talk to Claude the way you would a coworker. There's no secret to prompting. There's no need to be overly scaffolded or prescriptive for most tasks -- give Claude a goal, and it will figure it out.

Back in the Sonnet 3.5 days, your prompt mattered a lot. Nowadays, it's much more important to communicate to the model:

1. What you want it to do
2. How much effort you want it to spend
3. How it should verify that it did the right thing
Boris Cherny @bcherny
Prompt
♥ 12.1K · ⟲ 720 · 👁 1.1MView on X ↗

Eric Raymond Highlights Open-Source Rust Clone of Photoshop Built via LLM

Eric S. Raymond shares the photocraft GitHub project, a clean-room open-source reimplementation of Photoshop that he says was likely generated by decompiling the app, converting it to a spec and prompting an LLM for Rust. He argues this threatens closed-source software.

Original post · 1 min read
This is the doom I predicted a few days ago, coming for Photoshop. A clean-room open-source reimplementation.

No prizes for guessing that they decompiled Photoshop to source code, processed that to some kind of non-code specification language, then fed the spec to an LLM with an instruction to generate Rust.

Adobe just got nuked. And closed source is dead, dead, dead.

github.com/storytold/photocraft
♥ 16.2K · ⟲ 1.4K · 👁 3.7MView on X ↗

Nat Eliason Details Fourteen Ways His Bot Setup Automates Work

Nat Eliason lists fourteen functions of his bot setup, including a chief-of-staff agent that drafts emails, specialist agents per work lane, and cloud coding agents that open pull requests from Linear issues. He notes GrokBot as a substantial improvement over his previous OpenClaw setup.

Original post · 2 min read
Things my @bot setup does that still blow my mind:

1. A Chief of Staff who opens the day pulling open loops from email & tasks and suggesting things it can knock out before 7am.

2. After every meeting, decisions get folded into Notion, Linear, and Todoist — not left rotting in Granola

3. Every email starts as a draft. The CoS bot scans my email every ~2hr and drafts replies to nearly everything — including checking my cal for availability and finding requested attachments / links

4. A specialist for each lane: curriculum, engineering, coaching, hiring, content, ops, and one for every single piece of software

5. Routines that keep running while I’m offline (e.g. monitoring Sentry errors in our apps and proactively fixing things)

6. Group rooms where 2–4 bots share one project thread instead of me copy-pasting context

7. Cloud coding agents that pick up Linear issues and open PRs after running the list of open work by me EoD — then squash-merge to main when it’s done

8. Meeting prep briefs pulled from Granola + Notion before I walk in

9. A growing shareable knowledge base in Notion + a GitHub repo that we update daily based on what happens at school

10. Student progress look-up across Expertise, Followers, and CoFounder without inventing numbers — chat anytime to see where a student is on their business work

11. Mentor Mind that coaches me on how to hold the bar without inventing doctrine

12. Todoist as a central task list where it logs things it’s blocked on for me, or from meetings / emails — and I can paste links into chat to direct it how to solve them

13. Engineering work is automatically tracked in Linear so my and the product teams’ bots don’t collide with each other

14. Presentations spun up in Gamma / Claude Design without me opening a slide tool

15. Plaud / live capture → notes the bots can actually act on

Probably more but these were the immediate ones we thought of.
Nat Eliason @nateliason
GrokBot feels like absolute magic at this point, a meaningful leg up on my previous OpenClaw etc. setups.

And with how easy it is to setup, there's really no excuse now.
♥ 2.1K · ⟲ 207 · 👁 522.0KView on X ↗