Popular advice says to review the intent and stop reading the lines. The lines are where agent-written code goes wrong: N+1 queries, swallowed errors, and tests written by the same model that wrote the bug.
Available for interesting problems
Hi, I'm Mustafa. Software engineer building reliable systems.
I design and ship distributed systems, data pipelines, and AI-augmented tooling. I write about the engineering tradeoffs behind them, what works, what breaks, and why.
Recent writing
All posts →Code Review in the Age of AI: You Don't Get to Skip the Lines
The Blast Radius of a Technical Decision
The decisions that get six weeks of review are rarely the ones that bind an organization for years: measuring a choice by who it binds, for how long, and what undoing it costs, and matching review effort to that reach instead of to how big the decision looks.
The AI-Assisted Development Lifecycle
A spec-driven, review-heavy workflow for shipping real features with Cursor, built around one idea: build the feature twice.
Idempotency in Practice, Part 3: Idempotent Consumers and Pipelines
The idempotent consumer pattern implemented (processed-message table in the same transaction), dedup identity for events, Kafka's exactly-once machinery taken apart honestly, offset-commit ordering, and the series-capstone retrofit checklist.
Airflow on Kubernetes, Part 4: XCom on Object Storage, Secrets, and Slack Alerts
Moving XCom payloads to object storage instead of bloating the metadata DB, managing secrets and connections the isolated-worker way, and wiring up Slack notifications for failing DAGs.