The save that refuses to fail with its side effect
A Google Reviews listing-confirm route taught me that 'it saved' and 'everything it triggered afterward also worked' are two different claims, and a response body should never merge them into one.
#nextjs
3 posts tagged this topic.
The upload limit that mattered wasn't the one in my code
AIDA's public intake route checks content length, per-file size, a running total, and byte-sniffed MIME type before saving an attachment. None of that mattered once Next.js's own proxy layer silently truncated the request body first, with no error back to the client.
My E2E suite caught a wrong AI diagnosis — then it caught mine too
An AI agent blamed a failing Playwright test on Next.js response caching. I traced the code and blamed middleware. We were both wrong about the observation: the test's "anonymous" context was quietly authenticated. Two stacked bugs, two confident stories, and the re-run as the only reviewer that counted.