refactoring – Page 9 – Türker Yıldırım

A JSON column that had become a schema

Deep diveSeptember 20, 20239 min read

A settings column with forty keys, four of which are queried, and a WHERE on a JSON path scanning two million rows.

Moving a fifteen-year-old site into the site editor

Deep diveAugust 21, 202315 min read

A theme first written in 2008, 61 template files, and an editor who cannot change a footer without a deploy.

A WooCommerce template override that had been unused since 2019

NoteJuly 19, 20231 min read

Nine template overrides in the theme, of which four had been superseded by upstream changes and were being loaded in place of maintained files. A template override is…

The state file two people wrote to at once

Deep diveJuly 14, 202310 min read

Two pipelines, one state file, and a plan that proposed deleting a database. A lock held by a run cancelled forty minutes earlier.

Container queries, and the component that stopped needing a prop

Deep diveJuly 7, 202310 min read

A card with a variant prop that exists only to describe its width, rendered wrong in a sidebar somebody added last week.

Patterns as a deliverable, and the editor who stopped asking us

Deep diveJune 27, 20239 min read

A request for a new landing page layout, for the ninth time. Every campaign page a developer ticket, for work that is arrangement.

The Webpack config we finally deleted

NoteJune 27, 20232 min read

A 340-line configuration accumulated between 2017 and 2021, replaced by a Vite config of 24 lines, and the deletion took longer than the replacement. Most of the file…

Two years of deprecations, and the upgrade we could no longer defer

Deep diveJune 6, 202314 min read

PHP 8.0 reaches end of life in November and the application is on it. 4,100 deprecation notices, and a log filter that had been hiding them.

A suite that runs in four minutes because it stopped touching the database

Deep diveMay 28, 202310 min read

1,400 tests, fourteen minutes, and 1,100 of them opening a transaction against MySQL for no reason anybody could name.

The anti-corruption layer we should have written first

Deep diveMay 9, 202310 min read

A supplier who renamed four fields in a minor release, without notice, and twenty-two files touched to accommodate it.