design-patterns – Page 2 – Türker Yıldırım

Publishing a shared lint config for a team

Deep diveJanuary 22, 202610 min read

turkerdev/kbox-eslint-rules, and four repositories with four nearly identical configs that disagreed on eleven rules.

A plugin with no admin screen

Deep diveDecember 18, 202510 min read

A plugin whose entire configuration is a constant and a filter, on a site whose deployment is a pipeline.

A container query on a component nobody had placed narrowly

NoteDecember 4, 20252 min read

A container query written in 2023 for a case that had never occurred, exercised for the first time in December. A branch that has never executed is a…

PSR-18 middleware, and the order that matters

NoteNovember 13, 20251 min read

Four decorators around an HTTP client, composed in an order that is obvious once and unrecoverable afterwards. Signing inside retry is mandatory — a retried request needs a…

Boundaries drawn on a whiteboard, and the test that checks them

Deep diveNovember 4, 202510 min read

A module diagram from 2023 and a codebase that has moved since. A diagram everybody references and nobody has checked.

An interface extracted for a second implementation that arrived

NoteOctober 30, 20252 min read

An interface added in 2023 against the rule that says not to, and a second implementation in 2025 that vindicated it by accident. The rule about interfaces with…

A readonly class that needed one mutable field, and what that meant

NoteOctober 27, 20252 min read

A readonly value object that wanted a lazily computed cache, which is exactly what readonly forbids and is usually a signal. The wrapper is the textbook answer and…

Anchor positioning, read and not used

NoteOctober 9, 20251 min read

A CSS feature that solves a real problem, available in one engine, evaluated and deferred. The fallback syntax is the part that makes this genuinely better than the…

Ten years of a codebase, read in one week

Deep diveOctober 9, 202510 min read

A decade of an application, and a week spent reading it rather than changing it. Decisions re-litigated because nobody knows what is already there.

An exception hierarchy with one root and no depth

NoteOctober 9, 20251 min read

Eleven exception classes, all extending one application root, and no intermediate types — which turned out to be right. An intermediate class exists so a caller can catch…