---
title: "Comment by Diokel on \"What a developer survey taught me after 6 weeks of AI code review\" | Hashnode"
description: "Great post, the section on severity tag calibration really caught my eye. Usually, you spend way more time optimizing metrics like precision or F1-score, but yo"
url: "https://hashnode.com/posts/ai-code-review-developer-survey-6-weeks/6a3e12a2bd995b692631656c/comment/6a431ae99f8c8ff257258c5e"
---

[Discussion](https://hashnode.com/posts/ai-code-review-developer-survey-6-weeks/6a3e12a2bd995b692631656c)

Comment [What a developer survey taught me after 6 weeks of AI code review](https://hashnode.com/posts/ai-code-review-developer-survey-6-weeks/6a3e12a2bd995b692631656c)

[Diokel](https://hashnode.com/@diokel)

[Jun 30](https://hashnode.com/posts/ai-code-review-developer-survey-6-weeks/6a3e12a2bd995b692631656c/comment/6a431ae99f8c8ff257258c5e)

Great post, the section on severity tag calibration really caught my eye. Usually, you spend way more time optimizing metrics like precision or F1-score, but you shouldn't overlook user alignment or the model's user experience. These are things you might not even consider at first.

[Deepak Goyal](https://hashnode.com/@deepakgoyal-ai)

[Jul 1](https://hashnode.com/posts/ai-code-review-developer-survey-6-weeks/6a3e12a2bd995b692631656c/comment/6a431ae99f8c8ff257258c5e#reply-6a4502d399f4da402c89a6fa)

Thanks!

Though calibration sits a step before the metrics — precision/F1 tell you whether a finding is correct, not whether "\[blocker\]" reads the same to a human as to the tool emitting it. A vocabulary problem, not a model one, and no score catches it.
