Pinned Tweet
The @ServiceTitan S-1 filing is >300 pages.
Their customers are my customers’ customers (I work with wholesalers/distributors), so understanding the $1.5T trades industry is part of my job.
Here’s what I learned (a 🧵)
3
3
1,651
Nick Pericle retweeted
I've been working with a few orgs with 700+ engineers to redesign their sdlc. they are confused. they've rolled out claude etc., engs are more productive, but they're not seeing almost any of the "speed" startups are feeling right now. i keep telling them, the software part is easy(er). you've got to reorganize people.
read some research today that I think nicely illustrates this. SWE-CoWork (will drop link) found that frontier models completed *less than 8%* of their assignments when they had to track down requirements spread across a 26-person org of AI-simulated colleagues.
Anyone working with an agent day to day can tell you that an agent doing less than 8% of anything is virtually impossible. but also that asking 26 people for requirements is insane (but common).
agent improved when given all requirements up front, but still struggled on changes that touched 60+ files.
so, some of the speed will be realized when models get better at highly distributed implementations. big labs will do that for you. but the real key to moving faster is redistributing ownership to be narrow and deep, only then followed by said "software factory."
Yet.
Replying to @primeindiia
Rockstar’s GTA 6 took roughly 8–11 years and an estimated $1–1.5B (they denied anything over $1.5B).
With 2026 AI tools for assets, animation, dialogue, environments, code and testing, costs could drop nearly 50% per Morgan Stanley. A comparable-quality open-world game would still need a large experienced team for design, systems, polish and QA.
Realistic range: 3–5 years and $300–700M. Full GTA-level fidelity and Rockstar polish isn’t a solo AI job yet.
22
Nick Pericle retweeted
imagine telling someone from the 80s that one of these guys was a socialist and the other one was the capitalist
Nick Pericle retweeted
Replying to @conconconling
It’s deployment all the way down
Nick Pericle retweeted
I regret to inform you that you need to do uncomfortable things sooner. The delayed conversation gets harder. The ignored problem expands. The minor repair becomes a major one. Peace isn’t found through avoidance. It’s earned through early action. The recipe for a good life.
Nick Pericle retweeted
The more I deploy AI in enterprises, the more I realize that the biggest productivity gains come from decoupling AI from existing human workflows entirely.
In our work at The GCC, I keep coming back to one question: "If you were to rebuild a bank in 2026 to be AI-native, what would still need to be true?"
And quite frankly, once you stop designing around human workflows, you realize that much of an enterprise can be broken down into a few hundred discrete systems that can operate independently and coordinate when needed.
We're starting to explore this more deeply with some of our customers.
But I'm increasingly convinced that the future of enterprise AI isn't about augmenting how humans work but about building organizations that no longer need to work the way humans do.
I can already see some interesting new human roles come out of this at FIs.
Last year over the holidays, Claude Code escaped containment beyond engineering.
@lennysan, @TheStalwart, @bcherny all said some variant on: "it's not for writing code, it's for anyone who uses a computer all day, and here are 50 cool use cases."
Over the break, non-engineers jammed on personal projects, saw how powerful coding agents were, and came back with a mandate to adopt at work. One year later, the majority of non-eng use is still contained to one person's local setup, learning isn't scaling, improvements aren't compounding.
This holiday break, I predict non-engineers will test moving beyond solo projects, and figure out the team infra: the software factories, sandboxed agents, context layers, multiplayer workflows that let teams collaborate.
They'll come back on Jan 4th with a mandate to improve how their team works with agents.
Nick Pericle retweeted
The few software consultancies I talked with are all pivoting (or have pivoted) to building as AI-native + helping companies become AI-native.
Reminds me in the 2000s when top software consultancies did TDD + taught their customers TDD
Nick Pericle retweeted
A new faux pas I’m seeing: dismissing a teammate’s well-structured, probably decent agentic output as “AI slop” because you don’t want to read it.
If a teammate (or agent) has skillfully prompted and carefully edited something to solve a problem or communicate with the business, it isn’t automatic slop just because AI generated it. There’s often good stuff in there... if it’s long or you're multi-tasking, feed it to your agent.
Don’t overuse the term "AI slop" for any AI output. Save it for the actual sloppity slop, ya know?
The leading observability platform wants $83,700/yr just to monitor your app and catch issues.
So Replit Missions built DataCat: github.com/replit/datacat
100% free.
This isn't a prototype. Agent swarms explored thousands of workflows in the leading observability platform and rebuilt its features 1:1.
Nick Pericle retweeted
The most difficult thing to explain to people is that AI is actually underhyped
Nick Pericle retweeted
your job as a software engineer in 2026 is to scroll twitter for useful things to send to your agent
you can now test Artifacts repos locally!
- create, fork & import repos with wrangler dev
- clone & push without impacting what's in production
- repo events (repo.forked) can trigger your workflows locally, so you can test them before you deploy
big shoutout to @leostera for shipping this!



























