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,650
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!
Nick Pericle retweeted
📢 Meet Qwen4-Max, your new AI teammate for work, creativity, and discovery!
Qwen4-Max is built on a new MoE architecture with native vision and a 1M-token context window.
Highlights:
- Outperforms Qwen3.8-Max with up to ~50% fewer tokens, while average cost per task drops over 60% in our internal evaluation.
- Advances real-world productivity through greater proficiency with professional tools, stronger long-horizon execution, and higher-quality deliverables.
- Handles real tasks, including 3D modeling, game development, manufacturing, finance, law, healthcare, and frontier scientific discovery.
- $1.5/M tokens for input, $4.5/M tokens for output, and $0.075/M tokens for implicit caching — all lower than Qwen3.8-Max, with implicit caching down by 70%.
The API is live on QwenCloud. You can also try Qwen4-Max on Qwen Studio, QwenWork and Qoder.
Start building today! 🚀
- Blog: qwen.ai/blog?id=qwen4-max
- API: qwencloud.com/models/qwen4-m…
- Token Plan: qwencloud.com/pricing/token-…
More to come! The open weights of smaller Qwen4 models will be released. Stay tuned. 👀
Nick Pericle retweeted
“Don't worry, you don't need to learn how to write this. Your agents will. And we made them really good at it.”
Replying to @vercel
Nick Pericle retweeted
Thank you @JensenHuang for 33 years of bold leadership. You built a small startup into America’s most valuable company, with relentless improvement. Your grit and perseverance should always be remembered. Your personal generosity with time and advice to founders like me has secured a bright future for America and AI.































