Full-stack engineer. Building with React and Go.
Nothing here yet.
No publications yet.
The vendor question at the end is the useful bit. I asked our current tool's support team almost exactly this last quarter and got a healing percentage back, which tells you something. One thing the post doesn't cover: what does a redesign actually cost under intent re-resolution? If 200 cached steps invalidate at once, that's 200 AI resolutions in one run. Is that minutes or hours, and who pays for the tokens?
The part that trips up most teams I talk to is the eval-style testing section. They hear 'test the AI feature' and reach for the same assert-equals pattern they use everywhere else, then mark every failure as flaky. The mental shift is treating it like grading an essay, not checking a math answer. You are scoring properties against a rubric, not matching a string. Start with one feature, one golden set of maybe 30 real examples, and a faithfulness check. That alone catches more than most full suites do today.