Husband, dad of 2 boys | AI Whisperer and all things Agents and AI | Founder of https://xitter.cf/t.co/obEl8IsEIP and https://xitter.cf/t.co/0JqxGEw6rx

Texas / Remote
Joined July 2025
My wife just offered to be the PM on my household AI projects. First one is taking over PM'ing for the video game I made for my son, Space Pup. space-pup-sigma.vercel.app
4
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.
19
3
85
6,355
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.
57
6
7
217
14,816
AI makes it tempting to toss one more thing into the ticket. Big tickets become big PRs, and big PRs become the bottleneck. Here's how I right-size work for my agents:
1
38
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.
22
6
58
5,825
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…
56
27
4
513
38,056
Welcome back! 🙌🏻
Plot twist: I’ve moved 80% of my personal coding over to claude code + opus-5.5 why? - cc projects is goated - I can’t press “steer” anymore in codex - code is good? - less front end slop but tbh: opus 5.5 creative abilities was the gateway drug to taking back my coding work
14
Patrick Robinson retweeted
Your prompt isn’t bad. Your ticket is.
16
3
3
30
7,256
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.
22
5
60
7,016
Can't say how many times in the last year or so I've said, "Have you asked AI?" More recently, "Have Claude do it."
8
Value = Why / How Dude's Law Keep that how small, y'all. (i.e. reduce complexity)
4
Patrick Robinson retweeted
"Smaller things get through the pipe faster." - Plumber Good advice for devs too.
10
7
66
6,067
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.
21
10
4
185
9,144
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.
21
3
2
40
5,889
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.
27
1
49
6,989
You can see when I started using my personal GitHub to do things... and when I created my factory
i wanted to visualize what my github history looked like before and after the AI inflection point. see yours here - mo.rgan.co/gh/ i've looked at a few friends, eng and design, and it's really interesting to see the patterns.
20
I've never been on a team that struggled with tickets being too small. What's your team's right-sized ticket? If you respond in story points, tell me why you use points.
7
Hit weekly limit on Grok @bot Also noticed additional usage option was gone 👀 What's everyone up to these days?
1
38
Did the mega.dev assessment today. Had it evaluate me and my factory sessions. My factory won. Not sure that's good or bad? @kentcdodds what do you think?
1
1
16