Professional Antipatterns
Things I have lived through in real engineering organizations. No coworkers are named and no company is identified: the point is the pattern, not the people.
// 4 entries, in order
Professional Antipatterns: reprimanded for not committing enough // In 2025 I was reprimanded because my commit count on the company's KPI dashboard was lower than other people's, while I was the lead architect and team lead. How an agent skill that split my work into more commits made management believe I had improved, why commit count fails as a KPI, and what a healthy alternative looks like. Professional Antipatterns: the CTO who chose agentic development over agentic development // A colleague presented GitHub's Spec Kit and spec-driven development with Claude Code and Cursor in an internal workshop. The CTO's verdict was that we would go with agentic development instead. Why answering a topic you do not know with something irrelevant costs a leader more than asking a question would. Professional Antipatterns: the promotion that was always one year away // Seven years at Senior while leading Staff-level work, a promotion promised for the following year that never came, a request to align level with scope that was called blackmail behind my back, and an email nobody answered. Why a permanent veto and the silent treatment cost an organization its engineers. Professional Antipatterns: the manager who committed the team overnight // One evening my manager announced in chat that he would commit the team, by email that night, to delivering the next day a customer extension that needed at least three weeks of several senior engineers. The deadline was missed and the team was blamed for committing. Why commitments made upward and blame sent downward drain a team, and what asking first looks like.