惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

罗磊的独立博客
G
Google Developers Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
腾讯CDC
有赞技术团队
有赞技术团队
Vercel News
Vercel News
MongoDB | Blog
MongoDB | Blog
M
MIT News - Artificial intelligence
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
B
Blog RSS Feed
I
InfoQ
Blog — PlanetScale
Blog — PlanetScale
博客园_首页
The Cloudflare Blog
B
Blog
C
Check Point Blog
Stack Overflow Blog
Stack Overflow Blog
IT之家
IT之家
U
Unit 42
D
Docker
月光博客
月光博客
aimingoo的专栏
aimingoo的专栏
博客园 - Franky
A
About on SuperTechFans

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
My Thoughts on Token-Maxxing: A Call for Learning, Creati...
Konrad Kraje · 2026-05-18 · via DEV Community

Konrad Krajewski

OpenIA generated image
Tokenmaxxing is an example of how a single parameter can push organizations toward either positive outcomes or harmful behavior.
How does the bad path begin? It starts very innocently. At the beginning, there is always a company-level initiative. Leaders and managers try to find the best way to optimize processes and boost company development. After 2025, there is mostly one direction - introducing AI tools.
So companies spend a lot of money introducing these tools, adapting them to their profile, and maintaining them. It is a significant investment. Over time, however, some disappointment may appear. There is neither massive optimization nor a visible boost in productivity. Of course, there is always some scale of improvement, as well as some scale of disappointment. Up to this point, there are no errors — this is simply reality.
The real problem may start afterward. At that stage, investigations begin to find where is the issue? Usually, the culprit is identified quite quickly — people who do not use the tools enough, or do not use them widely enough.
What happens next? Pressure to use AI as much as possible. And this is where tokenmaxxing begins. Managers can easily see who uses AI tools the most. They may not check what kinds of problems people are solving; instead, there is only one visible parameter: token usage. The more, the better. But is it really?
As a result, people start burning tokens everywhere simply to avoid negative consequences — even for tasks where AI is unnecessary or where the AI-generated outcome is mediocre.
This is the perfect recipe for disaster. And later it does not help when managers say that employees will not be judged by token usage. The show has already started, and stopping this snowball becomes very difficult. And from the employee’s perspective, there is always some kind of uncertainty: What can I do? How can I use it? What if I make mistakes? How will I find time to experiment? There are many more doubts, and it ultimately depends on the company culture how everything turns out.

I’m glad that the company I currently work for chose an experimentation-driven approach instead of simply following the tokenmaxxing approach.
During one week, we had an opportunity to experiment with AI tools at different levels and across different layers. We could split into different squads. There were no rigid rules regarding squad size or the types of employees involved. The idea was simple: experiment with AI tools as much as possible — but truly experiment. Define friction points, identify what works well and what does not.
From my engineering perspective, it was a great approach, and inspiring experience. In the team I was part of, we tried to implement a product-owner-defined concept starting from design and using spec-driven development. We used AI tools at every stage of the process.
The high-level idea was to create a top-level specification with interfaces, while each developer in the squad could introduce their own sub-specifications for the area they were responsible for.
We ended up with the first draft of an MVP for our feature, as well as many AI-agent-related skills that can now be developed, improved, and used more broadly in our engineering work. At the company level, we could see how other teams approached problems and what they experimented with. Basically, we could learn from each other at both the squad and company level.
But what was most inspiring, paradoxically, was that we cooperated as a squad more closely than we normally do. I could say that AI brought people closer together. And I think that should be the real idea. Inspiring, isn’t it?

AI tools should not separate people from the squad or team, pushing them toward working independently together with AI agents. The goal should be that AI tools help people collaborate more tightly, because we all know that AI still cannot replace human judgment, emotional intelligence, and creativity — at least not for now.
Could there be a future where the product of a single human brain working with AI becomes better than collective human collaboration? Maybe. We will see. But that is a story for another time.
My main takeaway is that AI tools are great. We should use them, and we need to use them more. But nothing is better than collective human work. Instead of forcing people to use AI tools and judging their engagement based on a single parameter, it is far more important to create space for experimentation and making mistakes. Because only in that process, there is a space for improvement, development, and real growth.