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.
A practical YAGNI story from data engineering: keeping a CI workflow intentionally narrow until the second real use case appeared.
Why AI makes engineering fundamentals more important, not less, and how they shape real production decisions.
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.
A reflection on turning one AI-generated Python prototype into reusable coding-agent guidance: clearer implementation boundaries, stronger quality expectations, and a shared quality bar before prototypes become real tools.
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.