Menu

Decision Records So AI Context Doesn't Rot
πŸ“°

Decision Records So AI Context Doesn't Rot

DEV Community: laravelΒ·Muhammad Ali MughalΒ·about 16 hours ago
#KKPeEMfZ
#devtolaravel#devto#dev#decisions#code
Reading 0:00
15s threshold

On one client project, an AI assistant helpfully "fixed" our queue setup three times in two months. Each time, a developer asked it to speed up a slow job, and each time it suggested moving the work from our dedicated Redis queue back to the database driver, because the database queue was simpler and the assistant saw a stray QUEUE_CONNECTION=database in an old .env.example . Nobody on the current team remembered why we had moved to Redis in the first place: a deadlock storm during a Black Friday import, two years earlier. That reason lived in a Slack thread and one engineer's memory. The code did not explain it, so neither the new developers nor the assistant could respect it.

I wrote this with help from AI tools and checked every example against Laravel 11, Node 22, GitHub Actions and the adr-tools and MADR conventions.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.