Cory House

I help dev teams be insanely productive with AI.
Courses: &
Consulting: ⚛️

[Cory House @housecor]

10 lessons I've learned about handling React state over the last 7 years...

(thread)

#react #reactjs

[Cory House @housecor]

@EmilioSchwaiger Some PRs have no security implications (doc change or variable rename for instance)

[Cory House @housecor]

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

[Cory House @housecor]

@dschewchenko Not sure - haven't seen that yet

[Cory House @housecor]

Woah, this is gonna be handy.

New "Watch and fix" button just showed up on GitHub PRs.

[Cory House @housecor]

@akoskm fair point

[Cory House @housecor]

@xabzxbt You don't have to hand it over, but you should get the AI's help

[Cory House @housecor]

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.

[Cory House @housecor]

@avindrafernando Yep, a factory is basically skills that call skills, and is triggered via a ticket instead of a human.

[Cory House @housecor]

@oleksantoniv They do phased releases, have good monitoring, and quickly patch or rollback

[Cory House @housecor]

Starting to hear of more teams skipping PRs and doing true trunk-based dev.

The argument: PRs make less sense in the age of agentic coding.

The agent is the author, not me. So I, the prompter, am the first reviewer. One or more AIs operate as second reviewer.

Eliminating PRs unlocks radically more throughput - At Amp they do over 100 releases a day.

[Amp @AmpCode]

21 people, a single meeting a week, no quarterly goals, no pull requests, no mandatory code review, no titles (except one dictator), a hundred releases a day, bugs fixed in minutes, famous for killing features.

@sqs and @thorstenball on how the Amp team works:

[Cory House @housecor]

@ByJavidShaikh Yep and only 21 employees

[Cory House @housecor]

@devteamcoach Absolutely

[Cory House @housecor]

@ScottForsyth Ephemeral environment per branch

[Cory House @housecor]

True, but before AI trunk based dev meant we had to pair program constantly (to replace the PR review).

Most devs aren't willing to pair all day.

Now I can "pair" with AI all day on both dev and review, so trunk based dev is more practical than ever.

[Paul Hammond @citypaul_uk]

@housecor Trunk based dev was far superior before AI came along as well.

[Cory House @housecor]

@devteamcoach Yes maturity is a necessary precursor

[Cory House @housecor]

@videvjs Probably not. All this experience combined with agents feels like superpowers

[Cory House @housecor]

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.

[Cory House @housecor]

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.

[Cory House @housecor]

"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.

[Cory House @housecor]

If the prompt “implement ticket 123” leads to a bloated context or giant PR, then the ticket is probably too big.