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.
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.
I kept noticing coding agents drifting into `pip install`, raw `python`, and hand-edited dependency files in Python projects. So I built a small repo with reusable `CLAUDE.md` and `AGENTS.md` guidelines that push both Claude and Codex toward a consistent `uv` workflow.
The first part of a series on engineering effectiveness anti-patterns, focused on how constant context switching quietly erodes focus, depth, and overall effectiveness in day-to-day engineering work.
A reflection on territorial behavior in engineering teams: why it shows up, why it hurts collaboration, and how to catch it in yourself before it damages trust.
The show must go on in the AI era. The responsibility - and the opportunity - for experienced software engineers to help grow the next generation is still here. Sharing knowledge and supporting early-career talent is something AI did not and could not change.