Problem I keep seeing: Teams with one product owner making tickets for 3-10 developers.
This doesn’t work anymore.
In the age of coding agents, one PO can’t create tickets fast enough to keep developers busy.
Code isn’t the bottleneck.
Requirements are.
Reorgs are coming.
#short topics
> I open a PR
Coworker uses Claude to review. It requests minor changes.
I fix the comments and request review
Coworker takes awhile to respond, then uses Claude to review again. It requests minor changes.
This loop has repeated for two weeks on a single PR.
#coding#ai
Opus is better than I ever was
#personal_growth#improvement
A software factory is basically 2 things:
-
A high-level skill that calls other skills (for example, implement-ticket or fix-bug).
-
It runs automatically when it sees new tickets or errors in a log (instead of being run manually by a human's prompt).
#ai agents#software factory#automation
For the first 25 years of my career, I worried that my job was too hard.
Now, I worry that my job is too easy.
#career growth#self-reflection#workplace perspective shift
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.
#ai#software engineering#team size
"Smaller things get through the pipe faster." - Plumber
Good advice for devs too.
#programming#software development#small batches
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.
#agile#task management#team efficiency
Just joined a team with nearly 500 .md files for AI.
Nearly half a million words.
Just reading all the AI related instructions, skills, hooks, etc would take me about 30 hours!
I keep seeing teams with elaborate setups like this.
I'm increasingly skeptical it's worthwhile.
#documentation#ai workflow#skepticism#team processes