I’m convinced the magic bullet is deterministic checks. Linters, static analyzers, etc. Whatever you can do to create deterministic gates that the LLM simply must overcome to reach a “done” state, do it. Has been making a huge difference for my team, but sister teams are so invested in writing the perfect Make No Mistakes prompt that they just can’t see it.
Basically I treat it like a junior dev. We don’t get junior devs to write code correctly by cajoling them just right, we add CI gates. It still works.
Why aren't the teams using shared checks? Are the codes in different repos?
Wouldn't have helped, sibling comment: https://news.ycombinator.com/item?id=48797883
Architectural decisions are not lintable.