Harness Engineering, Part 1: The Model Is Not the Agent
An agent is a model plus a harness. Part one of a three-part tutorial: what the harness is, the seven parts every one is built from, where the loop should stop, and which tools to give it.
Senior Data Engineer · 6+ years
I'm Oguzhan Ozturk. I design real-time pipelines, cloud-native architecture, and AI that earns its keep — for teams at Garanti BBVA, FREENOW, and Huawei.

Shipping data platforms at
A PostgreSQL listings ETL took 16 hours to backfill one large brand against a 4-hour SLA. The real problem wasn't the engine — it was running an OLAP workload on an OLTP store. A primer on the option landscape and a two-horizon path from quick win to platform.
Mirror a multi-tenant MySQL source into a queryable analytical store in under 5 minutes — built lean for a startup (~$200/mo) but designed to scale from 150M to 1B+ rows. CDC architecture, data modeling, failure handling, and the trade-offs.
Audit pipelines, modeling, and warehouse design — get a concrete, prioritized roadmap.
Kafka, Flink, CDC. Low-latency pipelines that hold up under real production load.
Legacy batch to cloud-native, Spark, and lakehouse — with a quantified business case.
LLM + vector search over your data, plus AI-augmented engineering practices that ship.
An agent is a model plus a harness. Part one of a three-part tutorial: what the harness is, the seven parts every one is built from, where the loop should stop, and which tools to give it.
A Telegram bot that turns a ticker into a full research pass: live news, analyst sentiment, and a technical read with an enforced risk:reward, then lets you interrogate the report instead of just reading it.
A map of the eleven open-source repos behind the way I work with coding agents now — grouped into the three things they actually fix: how the agent works, what it knows, and how much of the loop you have to crank yourself.