alt Hacker NewsThere's a recurring theme in these agentic engineering threads that is worth calling out: the lessons, are almost always stated as universal – but are deeply dependent on team size, code base maturity, test coverage, and risk tolerance. What gets presented as a “win” for a well instrumented backend service could easily guide those working on UI-heavy or old code down the wrong path. The art of this might be less about discovering the correct pattern, and more about truthfully declaring when a pattern applies.
Replies
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.
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
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.