That's a good call out. The reason I'm doing this as a website and not a book is that this stuff changes all the time and I want to update it, so one of the things I'll try to do is add notes about when and where each pattern works as those constraints become clear.

I work as a consultant so I navigate different codebases, old to new, typescript to javascript, massive to small, frontend only to full stack.

Claude Code experience is massively different depending on the codebase.

Good E2E strongly typed codebase? Can one shot any feature, some small QA, some polishing and it's usually good to ship.

Plain javascript? Object oriented? Injection? Overall magic? Claude can work there but is not a pleasant experience and I wouldn't say it accelerates you that much.

"...typescript to javascript"

Country AND Western!

We are going to start seeing that be the primary selection criterion. Pick a stack that agents are good at.

Agreed. AND some are universal -- right now, agentic workflows benefit from independent source-of-truth checkins A LOT.

A lot of Simon's tools are making harnesses for this so it can get integrated:

showboat - create a demo, validate the code generates the demo. This is making a documentation source of truth

rodney - validate visually and with navigation that things work like you expect

red-green tests are conceptually the same - once we have these tests then the agent can loop more successfully.

So, I think there are some "universals" or at least "universals for now" that do transcend team/deployment specificity