Husband, dad of 2 boys | AI Whisperer and all things Agents and AI | Founder of https://nitter.cf/t.co/obEl8IsEIP and https://nitter.cf/t.co/0JqxGEw6rx
Texas / Remote
Joined July 2025
- Tweets1K
- Following181
- Followers103
- Likes1.7K
Patrick Robinson retweeted
Now you’re basically a manager. So, AI should keep working while you’re away from the keyboard - just like you kept coding when your manager was away.
“Every engineer is now a team leader, a manager, and your direct reports are the models and agents you use...but a team of two people who always pair-programmed together would not be much of a team, nor would a team where no one worked when the team leader was in a meeting.”
Patrick Robinson retweeted
“Your job has fundamentally changed. It is no longer to write code, and LLMs are not here to help you write better code faster.
Your job is to help the LLM write better code faster.”
Bingo.
Patrick Robinson retweeted
Skills can call other skills. They're basically composable functions written in English.
So, like a function, I prefer naming skills with a leading verb:
/open-pr
/audit-instructions
/review-pr-comments
Patrick Robinson retweeted
In 2026, if I'm creating anything digital by hand from scratch, I'm probably doing it wrong.
Not just code.
Branches
PRs
Tests
Plans
Docs
Skills
Charts
Slides
Summaries
Visualizations
If AI can gen it, I let it.
Then I tweak it.
Patrick Robinson retweeted
Skills are relevant at different times. So I consider running these skills at different points in my day:
Before starting work, I validate my plan:
/grill-me
/audit-ticket
/deep-research
Before my PR, I ensure quality:
/security-review
/code-review or /ultrareview
/simplify
After getting PR comments, I respond to them:
/address-pr-comments
On a scheduled cadence, I check for opportunities:
/improve-codebase-architecture
/security-review
/audit-instructions
Patrick Robinson retweeted
You’re not being lazy enough.
Tickets
Code
Config
Tests
Branches
PRs
Docs
Reports
Requests
All of it should be generated by an agent.
Then, add your human judgement on top.
Patrick Robinson retweeted
I've been coaching on AI adoption for the past couple years now, so I'll be talking about that on Nov 10! Come check it out!
Join Lean TECHniques Staff Engineer and @Microsoft MVP @danielwarddev on November 10 as he discusses what works in helping teams build AI habits that stick. Daniel will draw on DORA research and his own experience coaching teams.
Register below 👇
hubs.li/Q04CtzXL0
Patrick Robinson retweeted
You can’t build a software factory unless your team first does at least some of its product engineering through a factory as opposed to local coding agents.
This means centralizing your agents into one shared configuration that the team can optimize together. Once work starts flowing through the factory infra, you’ll have a baseline to measure and improve.
Patrick Robinson retweeted
AI means a big team can’t possibly keep track of all the daily changes.
So, I suspect the ideal team size for 2027 is 1-2 people.
Any more than that and people can't keep up with the changes, so they don't understand the system they're building.
Patrick Robinson retweeted
"The first thing you need to do to make effective use of AI and autonomous AI is to improve your own process"
-Gartner
Totally agree. I keep seeing teams over-trusting AI. They lack the automated quality controls to safely move faster.
Patrick Robinson retweeted
Subagent overuse and abuse has been a problem since mid 2025.
There is a time and a place and they can be very high leverage, but the vibeslop dopamine casino + twitter hype machine has let the average user down by encouraging more and more parallelism instead of thoughtful context management
Anthropic is now recommending that companies REMOVE unnecessary subagents from their AI systems.
This is a pretty significant shift in agent architecture, with their team finding that a single agent equipped with skills can frequently outperform complex multi-agent systems, and one customer seeing roughly 2x faster execution.
The emerging rules of thumb:
→ Skills: Teach the agent HOW to do something, including procedures, expertise, and instructions.
→ Tools / MCP: Give the agent the ability to DO things through APIs, actions, and live data.
→ Subagents: Use for parallel work, isolated context, or tasks a single agent struggles with.
The interesting part is progressive disclosure. Instead of spawning specialized agents or stuffing everything into a giant prompt, one agent discovers and loads skills and tools as needed.
Their advice is to fold existing subagents into the main loop, turn their instructions into skills, expose their actions as tools, and run evals to see if performance holds up.
As models have gotten smarter, improving agent architecture is becoming less about what you can add and more about what you can delete.
claude.com/resources/article…
Patrick Robinson retweeted
Mistake: Creating a plan via AI that answers many ambiguities in the ticket.
Instead: Update the ticket with all decisions made in the plan.
This way, the ticket is a *permanent*, centralized, comprehensive record of *all* decisions that's easy to reference later.
Patrick Robinson retweeted
"Smaller things get through the pipe faster." - Plumber
Good advice for devs too.
Patrick Robinson retweeted
If you track software factory metrics, don't celebrate the wrong signals.
Bad: LOC written, tokens used
Good: Cost-per-PR, cycle time from conversation start -> merge
A factory leaderboard should take cost into account and champion shipped work, not token spend.
Patrick Robinson retweeted
Wonder if your tests are helping? Ask Claude.
Prompt: “Look through my past sessions. How many times did a test catch a bug?”
I just asked Claude and it found 5 recent instances where a test caught a bug.
Patrick Robinson retweeted
I’ve seen many teams struggle because their tickets are too big.
I’ve never seen a team struggle because their tickets are too small.
Patrick Robinson retweeted
This post outlines an interesting new approach that AI unlocks: Non-code automated tests.
For example, QA doesn’t typically have the tech chops to write and maintain code-based tests.
But they can certainly ask Claude to click around for them!
Before you launch anything, have Opus 5.5 send 5 subagents in as your first users.
Paste this into Claude Code:
"Act as my launch QA lead. Spin up 5 subagents, each a different first-time user:
1. The impatient one: skims, clicks the first button, quits at the first error
2. The skeptic: reads pricing, terms and privacy before signing up
3. The mobile user: does everything on a 375px screen on slow 3G
4. The non-native English speaker: only follows what the UI literally says
5. The breaker: pastes junk into forms, hits back mid-flow, double-clicks everything
Each one opens the app in a real browser, goes from landing page to first success, and screenshots every moment they get confused, stuck or annoyed.
Merge everything into one list ranked by how many users hit it. Fix it all in one pass, then rerun the 5 users to prove it's fixed."
Your first 100 real users won't tell you why they left. these 5 will.
(Works best with a browser MCP connected, Playwright or Chrome DevTools)