Effectiveness anti-patterns — part 6: YAGNI: don’t abstract before the second use case
A practical YAGNI story from data engineering: keeping a CI workflow intentionally narrow until the second real use case appeared.
Career notes
Tags
6 pages
Effectiveness Antipatterns Series
Effectiveness anti-patterns — part 5: when good work is invisible work
A reflection on invisible work in platform and data engineering teams: why success often looks like silence, why the work-speaks-for-itself instinct breaks at the senior-to-staff transition, and what I have tried to make my work more legible to people I don't sit next to.
Career notes
Effectiveness anti-patterns — part 4: meeting overload
A reflection on meeting overload: why every invitation deserves real scrutiny, why three to four meetings a day make focused engineering work much harder, and why leaving the room when I cannot contribute can be the responsible move.
Career notes
Effectiveness anti-patterns — part 3: knowledge silos feel efficient until they don't
A reflection on knowledge silos in engineering teams: why they often start as responsibility rather than ego, and what helps spread context before one person becomes the queue.
Productivity
Effectiveness anti-patterns — part 2: technical debt denial
The second part of a series on engineering effectiveness anti-patterns, focused on what happens when we keep postponing system health in favor of short-term feature delivery.
Productivity