The developer tools market has a blind spot. There are tools for writing code (Copilot, Cursor), tools for searching code (Sourcegraph, grep), tools for testing code (Jest, Playwright), tools for deploying code (Vercel, Railway), and tools for monitoring code (Datadog, Sentry).
There is no established category for understanding code before you write it.
The Gap
Look at a developer's workflow on a complex ticket:
- Understand the requirements and codebase context (30-40% of time)
- Plan the implementation approach (15-20% of time)
- Write the code (20-25% of time)
- Test the changes (10-15% of time)
- Review and ship (5-10% of time)
The tools market has optimized steps 3-5. Step 1 — the largest single time block — has no dedicated tool category.
Developers cobble together understanding from: grep, IDE navigation, Slack questions, reading old PRs, and staring at unfamiliar code until it makes sense. This is the Understanding Tax, and it accounts for 20-35% of total engineering time.
What Pre-Code Intelligence Includes
Pre-code intelligence is everything that happens between "ticket assigned" and "developer starts coding":
- Codebase mapping: Which files, functions, and features are relevant to this task?
- Dependency tracing: What will be affected by changes in this area?
- Tribal knowledge surfacing: What does the team collectively know about this code that isn't written down?
- Historical context: What past changes in this area caused problems?
- Complexity assessment: How hard is this actually going to be, based on structural analysis?
- Build planning: What's the optimal order of changes to minimize risk?
Why Now
Three market shifts created the need for this category:
- AI tools made writing faster, shifting the bottleneck to understanding
- Remote work eliminated ambient knowledge, making context-sharing async and expensive
- Codebase complexity is growing, driven by microservices, AI-generated code, and faster shipping cycles
The teams that solve the understanding bottleneck will ship 3-4x faster — not because they type faster, but because they start coding with full context instead of spending hours acquiring it.
Glue as Category Creator
Glue is the first tool built specifically for pre-code intelligence. Not code search (that's Sourcegraph). Not code generation (that's Copilot). Not code documentation (that's Swimm).
Pre-code intelligence: paste a ticket, get a battle plan. Every function traced, every dependency mapped, every lesson from git history surfaced — before you write a line of code.
Originally published on glue.tools. Glue is the pre-code intelligence platform — paste a ticket, get a battle plan.
Top comments (0)