---
title: "Comment by Parsa Mohammadi on \"AI-Driven Development Is a Diagnostic for Your Organization\" | Hashnode"
description: "Spotify’s two incident questions are the best part. the first one is harder than it looks though, you need to know which change caused the incident, and most te"
url: "https://hashnode.com/posts/ai-driven-development-is-a-diagnostic-for-your-organization/6ad8710cc077907c524a2e52/comment/6ad8e3ecbe72bf71319b757a"
---

[Discussion](https://hashnode.com/posts/ai-driven-development-is-a-diagnostic-for-your-organization/6ad8710cc077907c524a2e52)

Comment [AI-Driven Development Is a Diagnostic for Your Organization](https://hashnode.com/posts/ai-driven-development-is-a-diagnostic-for-your-organization/6ad8710cc077907c524a2e52)

[Parsa Mohammadi](https://hashnode.com/@tomosu)

[Oct 21](https://hashnode.com/posts/ai-driven-development-is-a-diagnostic-for-your-organization/6ad8710cc077907c524a2e52/comment/6ad8e3ecbe72bf71319b757a)

Spotify’s two incident questions are the best part. the first one is harder than it looks though, you need to know which change caused the incident, and most teams figure that out by hand. we looked at a Spotify outage from that angle at Tomosu, whether the risk was visible before it shipped. the PR looked reasonable on its own, the risk only showed up in how it interacted with the rest of production. that’s the gap we’re working on [https://tomosu.ai](https://tomosu.ai/)

[Shota Yamazaki](https://hashnode.com/@simukappu)

[Oct 22](https://hashnode.com/posts/ai-driven-development-is-a-diagnostic-for-your-organization/6ad8710cc077907c524a2e52/comment/6ad8e3ecbe72bf71319b757a#reply-6ad9bdbe6ab9d811800bb7b1)

Agreed, the first question is the harder one, because it needs the change behind the incident. The second is easier to start with. A team can ask whether the volume of change put pressure on review, testing, rollout, or observability without pinning the incident on one change.
