M. Semih Babacan

Series

Agentic Coding

Exploring AI-assisted development and agentic tools

9 postsAtom feedAll writing

I ship code with an agent doing most of the typing now, and I write this series because the tools change faster than anyone's advice about them. Most agentic coding content is either a vendor pitch or a doom post. I want the third thing: what actually changes how I work, tested against my own repos, not a demo.

The pattern across these posts is that the interesting decisions live outside the model. An identity file changes defaults more than a better prompt does. A hook that reinstalls rules after compaction matters more than a longer system message. Orchestrating five agents is a state problem, not a prompting problem, and I say so even while arguing that most teams reach for the heavy version too early. I also cover the boring stuff that gets ignored: agents authenticating as me instead of as themselves, and why cheaper, smaller models already beat the expensive ones on the benchmarks that matter for coding.

None of this is theory. Every post here comes from a tool I installed, read the source of, or ran against real work.

Start here

  1. I Stopped Writing Prompts and Started Writing Identity Files

    Start with the mechanism underneath everything else here: an identity file changes an agent's defaults, which does more than a better-worded prompt.

  2. The best prompting I've seen doesn't trust the model at all

    The same idea taken further — a rule system that assumes suggestions do nothing, with a hook that reinstalls itself after compaction.

  3. Get Shits Done, or how I stopped losing projects to context rot

    The day-to-day workflow this enables: a spec-driven loop built to survive context rot instead of hoping a bigger window fixes it.

  4. Ralph Loop: The Night Shift You Don't Pay For

    What happens once that loop is reliable enough to run unattended overnight.

  5. Why I treat agent orchestration as a distributed systems problem

    What happens once one agent isn't enough — coordinating several turns out to be a state problem, not a prompting problem.

  6. My agents are all logging in as me

    The operational risk that shows up once agents are actually running: none of them have their own identity, and the audit log knows it.

More in this series

January 2026