CTO & Co-Founder @ConductorOneInc
Portland, OR
Joined July 2007
- Tweets4.3K
- Following866
- Followers2.2K
- Likes6K
Pinned Tweet
I believe:
1) Corps will use 100s of different SaaS products (10x-100x from today)
2) New Arch required to enable #1: A fabric between companies, humans, and SaaS
3) Identity is going to become about Automation, Orchestration and Delegation -- the fabric between the parties
Paul Querna retweeted
we did invent it and it's called OIDC federation
vercel and github actions do it:
- each deploy gets a short-lived signed token
- AWS/npm/other services verify it via trust policy
- you get temporary creds
no keys to paste
the problem is not enough APIs and services accept it
The training data we as a society are creating in porting software to Rust might mean Rust is humanities last programming language - it’s a self reinforcing loop
Paul Querna retweeted
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
Paul Querna retweeted
100%. They 2010s were all about market and execution risk, with near-zero technology risk. Now we're in the era of taking technology risk, which is actually way more exciting.
So many venture investors are used to the last decade of underwriting where the main risk was the ability to capture demand - find pmf, scale sales etc…
For many of the new businesses being funded today demand is no longer the issue - if you can make low cost reliable ballistic missile interceptors or high bandwidth low cost memory then ya obviously you will have insane demand.
The risk moves to supply - ‘can you actually make the thing’ - a question literally no one asked in the era of HRISs & Neobanks - feels like a lot of faces will get ripped off people pricing ‘demand’ for magic beans that will never be delivered.
Paul Querna retweeted
"The last year in the technology industry has felt like 100 years all happening at once. Our industry is destabilized in a way nobody’s experienced since the advent of the personal computer. Every limit AI runs up against collapses within a month. Everything we do with frontier models today, in a few years we’ll be doing instantaneously and for free."
Today I'm parting ways with Fly.io. It's been a privilege. I'm off to tilt at a big old windmill with Kurt, again.
sockpuppet.org/blog/2026/09/…
it told me i had a "Novel architecture" and I'm not sure if that's a compliment or a passive aggressive nag. We truly have arrived at AGI.
We adopted Bazel in our Go monorepo... and I'm speaking at GoSF this Wednesday about it: meetup.com/golangsf/events/3…
I can have Mythos generate vulnerability reports, but have to use open models to build systematic fixes. It all makes sense.
recursive self improvement, depends on self modifying, but then depends on making good modifications.
unless you just try all possible modifications.
