Türker Yıldırım

system-design

  • Docker Compose in production, and why it is still here

    Deep dive10 min read

    Six years of Compose on a VPS, and an annual conversation about orchestration. Nothing is wrong, which is why the conversation keeps happening.

  • A year of an assistant in the editor, measured

    Deep dive14 min read

    A year of using a model-backed assistant, and an attempt to say something specific about it. Every claim about this is a demonstration or a complaint.

  • Managing WordPress entirely through Composer

    Deep dive15 min read

    turkerdev/wp-composer, and an install where nothing is committed except a lock file. Core, themes and plugins as dependencies.

  • A build with no bundler

    Deep dive9 min read

    A site with 18 KB of JavaScript and a build pipeline sized for something larger. What a bundler provides, listed, and which of it is needed.

  • Two years of query logs, read once

    Deep dive10 min read

    A slow query log rotating for two years and never aggregated, and performance work driven by whoever complained loudest.

  • Reading a codebase in a language I do not write

    Note2 min read

    A supplier’s open source client library, read to answer one question, without learning the language first. Reading unfamiliar code for one specific question is a different and more…

  • A licence that came back, and the migration we had prepared

    Deep dive9 min read

    The first of May, an AGPL release, and a decision from April 2024 that can finally be closed — in the direction nobody planned for.

  • A package I published, and the API design I got wrong twice

    Deep dive16 min read

    turkerdev/php-figma-api, a typed client for a third-party REST API, and two design mistakes that only appear once somebody else uses it.

  • A decision record for something we did not do

    Note2 min read

    A record of a rejected proposal, which is the kind nobody writes and the kind that saves the most time. The same proposal arriving twice in two years…

  • A dashboard rebuilt from the questions people ask

    Note2 min read

    A dashboard of fourteen panels, replaced by six, chosen by reading a quarter of incident messages. A dashboard built from available metrics answers what is measurable and a…