---
title: "Parsa Mohammadi (@tomosu) | Hashnode"
description: "Production Reliability Governance for the AI Era. Read the latest articles by Parsa Mohammadi on Hashnode."
url: "https://hashnode.com/@tomosu"
---

@tomosu

# Parsa Mohammadi

@tomosu · London, UK · Joined September 2026

Production Reliability Governance for the AI Era

### [Senior engineers aren't slow at code review. They're outnumbered.](https://tomosu.hashnode.dev/senior-engineers-aren-t-slow-at-code-review-they-re-outnumbered?utm_source=hashnode&utm_medium=feed)

https://www.youtube.com/watch?v=jrpAkZ9F6ao Every team with coding agents ends up with the same chart. Pull requests per week goes up and to the right. The hours senior engineers have for reading the

4 min read · [tomosu.hashnode.dev](https://tomosu.hashnode.dev/senior-engineers-aren-t-slow-at-code-review-they-re-outnumbered?utm_source=hashnode&utm_medium=feed)

[9h ago](https://hashnode.com/posts/senior-engineers-aren-t-slow-at-code-review-they-re-outnumbered/6afd8d068c5935293e3019d2)

### [Code Churn: Why the Files That Change Most Break Most](https://tomosu.hashnode.dev/code-churn-why-the-files-that-change-most-break-most?utm_source=hashnode&utm_medium=feed)

Code churn is how much a file changes over a period of time: lines added, lines deleted, and how many separate commits touched it. High churn concentrated in a small set of files is one of the more re

10 min read · [tomosu.hashnode.dev](https://tomosu.hashnode.dev/code-churn-why-the-files-that-change-most-break-most?utm_source=hashnode&utm_medium=feed)

[Nov 10](https://hashnode.com/posts/code-churn-why-the-files-that-change-most-break-most/6af394ab62b23cd06187233e)

### [CodeRabbit vs Tomosu: Code Review and a Reliability Gate on the Same Pull Request](https://tomosu.hashnode.dev/coderabbit-vs-tomosu-code-review-and-a-reliability-gate-on-the-same-pull-request?utm_source=hashnode&utm_medium=feed)

Written by the Tomosu team, so read it as a vendor's comparison. CodeRabbit details come from CodeRabbit's public pricing page and docs, checked November 2, 2026. CodeRabbit runs a review workflow. A

10 min read · [tomosu.hashnode.dev](https://tomosu.hashnode.dev/coderabbit-vs-tomosu-code-review-and-a-reliability-gate-on-the-same-pull-request?utm_source=hashnode&utm_medium=feed)

[Nov 4](https://hashnode.com/posts/coderabbit-vs-tomosu-code-review-and-a-reliability-gate-on-the-same-pull-request/6aeb3b7ec0deda1c04e05957)

### [Change Risk Management in Software Engineering](https://tomosu.hashnode.dev/change-risk-management-in-software-engineering?utm_source=hashnode&utm_medium=feed)

Learn how change risk management works in software engineering, from pre merge analysis and dependency context to deployment controls, runtime signals, and incident feedback.

2 min read · [tomosu.hashnode.dev](https://tomosu.hashnode.dev/change-risk-management-in-software-engineering?utm_source=hashnode&utm_medium=feed)

[Oct 26](https://hashnode.com/posts/change-risk-management-in-software-engineering/6adf8380ced913dfcfc6f6c1)

### [Why requests.get(timeout=5) can still hang, and how to set a total deadline](https://tomosu.hashnode.dev/why-requests-get-timeout-5-can-still-hang-and-how-to-set-a-total-deadline?utm_source=hashnode&utm_medium=feed)

If you call an HTTP API from Python with requests and pass timeout=5, a slow server can still keep that call open for much longer than five seconds. This post reproduces it with a small local server a

5 min read · [tomosu.hashnode.dev](https://tomosu.hashnode.dev/why-requests-get-timeout-5-can-still-hang-and-how-to-set-a-total-deadline?utm_source=hashnode&utm_medium=feed)

[2](https://hashnode.com/posts/why-requests-get-timeout-5-can-still-hang-and-how-to-set-a-total-deadline/6ade99556123af80316ccc42) [Oct 26](https://hashnode.com/posts/why-requests-get-timeout-5-can-still-hang-and-how-to-set-a-total-deadline/6ade99556123af80316ccc42)
