Engineering-practice

Inconsistency from duplicated code and format assumptions at layer boundaries are two recurring classes of bug. Their common thread: both can be blocked before you start, with a single pause. A breakdown of searching for reuse and drawing the data flow.

The most common cognitive bias in frontend quality is treating a max-warnings ceiling as an allowance and carrying test leniency into production. Starting from what the thresholds actually mean, a breakdown of what each tool is really defending.

The entire value of a modular monolith rides on that one boundary. A first-principles look at the EF/Dapper read-write split, why endpoints must stay thin, and the repeatedly-overlooked design point of least-privilege cross-module endpoints.

Reframing "calling a hook in an async function always crashes" as a render-time contract problem, "the giant configurable component" as a composition-vs-configuration tradeoff, and accessibility as a testing contract.

Directory rot and state rot are the same problem underneath: a boundary that stopped being held, a source of truth that got copied. A first-principles look at feature-based structure, the forces on three kinds of state, and why the auth boundary must clear the cache.