The most useful exchange I had this week was with someone who has 7 followers

FarzamHabibi, a product designer with only seven followers and nine public repositories, shared a GitHub repository named pre-production-checklist on 2022-08-27. The repository, which is less than a week old, has already amassed 10 stars and one fork. Despite the lack of authority, the author decided to engage in an exchange with FarzamHabibi, as feedback is a crucial argument for taking suggestions seriously.

On 2026-08-30, the author opened issue #11 in FarzamHabibi's repository, pointing out the lack of regression and monitoring content in the post-launch section. However, FarzamHabibi declined the suggestion, stating that his checklist, which contains 322 items, does not name any products as ways to satisfy the checks and is instead stack-agnostic.

The author then replied on 2026-09-02, providing six items related to regression, smoke, synthetic, and end-to-end coverage. In response, FarzamHabibi added a new subsection to his post-launch/01-readiness.md file, titled "Will you notice before a customer does."

The author proceeded to point out two real bugs in FarzamHabibi's project, leveraging the new checklist. The first bug was the cancellation of Muraqib's nightly Playwright run 81 times since late June, which went unnoticed because GitHub Actions runner timeout produced a "cancelled" message instead of a "failure." The second bug was the lack of alerting for missing alerting credentials in the project's notification paths.

The author discovered that all three notification paths silently reported success in such cases. FarzamHabibi appreciated the author's feedback and praised it as "the best thing anyone has sent this project." He subsequently added six more items to his checklist, fixing the two bugs, and released version 1.17.0.