Tokenmaxxing Is the New Stopwatch: Why Your AI Policy Needs to Be Coherent

Brian Meeker, a veteran engineering manager, draws a direct line from Taylorism with a stopwatch to today's "tokenmaxxing" leaderboards. His argument: any metric will be gamed, and AI token counts are no exception. Engineers already create loops to waste tokens and climb leaderboards, divorcing usage from actual productivity. Meeker's response is a coherent AI policy for his skeptical team.

The Four-Point AI Policy

• No AI mandate — Engineers won't be reviewed on how much they use AI tools. Tokenmaxxing is explicitly rejected.
• Understand what your AI generated code does — Blindly accepting LLM output is not allowed.
• Be able to do your job if AI tooling disappears — Skills must remain independent of crutches.
• Care about your teammates and customers — The ultimate goal is helping people, not maximizing tokens.

The article also skewers the AI booster contradiction: if everything you know will be obsolete in six months, why can't you just wait six months and use better models? Senior+ engineers are encouraged to use AI in whatever way works best for them—from daily driver to occasional proof-of-concept tool—without pressure to adopt immature workflows.

Meeker notes that many developers he speaks with have no such document at their workplace, leaving teams with the vague mandate to "AI as hard as possible." His post is a practical template for teams wanting a principled stance against metric gaming.