Discovery vs Tokenmaxxing

May 28, 2026 · Note · 2 min read · 100% human

Most current AI coding tools are steering users into tokenmaxxing and re-generating software from scratch, in complete ignorance of the vast amounts of publicly available, human-validated software that can be combined and modded in powerful ways to address 99% of use cases.

Yes, AI tokens are relatively cheap, but it's still cheaper to split the cost amongst many. More importantly, saving up mental cycles on what makes your solution truly unique has significantly higher ROI. You built your own CRM? Great. So can everyone else. Maybe you should focus on proprietary mechanisms for sourcing instead.

Part of the problem is perception. AI has muddied the waters for what is considered reasonable to build in-house. Most sensible people will agree that building infrastructure primitives is a waste of time. Need a custom UI component for reporting? Vibecode it. Everything else that falls somewhere in the middle of the spectrum? Less clear cut. More often than not, builders fall into the trap of false feasibility assumptions and decide to build it, blind to the number of edge-cases that make validation, maintenance and extensibility too big of a burden.

The other problem is customization. This is the now well-known problem with no-code software, opinionated frameworks and platforms like force.com. Everything is easy until it isn't. The effort spent on the last 10% dominates the costs of a project to an extent that initial savings become irrelevant.

There is also a third problem that gets little mention in this discourse: discoverability. Forget about SDKs and libraries, navigating the swath of publicly available software is impossibly difficult. Most users are simply unaware of the building blocks that could make their own implementation easier, which also makes it difficult to assess the marginal utility of requirements that require customization.

The abundance of AI-generated code is going to further exacerbate the discoverability problem. Yet even if we solve it, there is a much bigger problem waiting around the corner. How do we reward software creators, whether it's agents or humans? A system that doesn't reward visibility will naturally gravitate towards opaqueness. This feels like a fork in the road with a one way door that will have profound implications on the software industrial complex.

So how do we navigate this new world? We have a huge wave of token spend allocated towards sloppy, ephemeral software without clear ROI. At the same time we have a discoverability problem that is making it less and less possible for builders to collaborate on common, curated building blocks that stand the test of time and increase productivity.

All notes