Return to site

🤖🪙 SMART DEVELOPERS WILL NOT WASTE AI TOKENS ON EVERYTHING

June 29, 2026

AI is transforming how we build software; but that does not mean every developer task should become an AI prompt.

In this Stack Overflow Podcast episode, Java Champion Trisha Gee discusses the evolution of IDEs, developer workflows, and the importance of using AI where it genuinely adds value.

The future is not about replacing our existing tools.

It is about combining them intelligently. 🧠

🔸 YOUR IDE ALREADY SOLVES MANY PROBLEMS

Modern IDEs can already:

▪️ Navigate code instantly.

▪️ Rename symbols safely.

▪️ Find usages accurately.

▪️ Generate standard code.

▪️ Detect common mistakes.

▪️ Run tests and debug applications.

Asking an AI agent to rediscover information already available through deterministic IDE features can waste tokens, time, and money.

🔸 DO NOT SEND THE WHOLE CODEBASE

More context does not always produce a better answer.

Sending thousands of files to an AI model may:

▪️ Consume unnecessary tokens.

▪️ Introduce irrelevant information.

▪️ Make the model lose focus.

▪️ Increase response time and cost.

▪️ Produce a less precise answer.

Select the smallest relevant context: the failing method, its dependencies, the error message, and the expected behavior. 🎯

🔸 USE THE RIGHT TOOL FOR THE TASK

Use the IDE for deterministic operations:

▪️ Navigation.

▪️ Refactoring.

▪️ Static analysis.

▪️ Symbol search.

▪️ Compilation errors.

Use AI for tasks requiring reasoning or exploration:

▪️ Explaining unfamiliar code.

▪️ Suggesting alternative designs.

▪️ Generating test scenarios.

▪️ Investigating complex failures.

▪️ Reviewing trade-offs.

AI should complement the IDE—not reproduce it through expensive prompts.

🔸 MUSCLE MEMORY SAVES TOKENS

Experienced developers know how to move quickly through their tools.

Shortcuts, inspections, debugger usage, and refactoring commands are not obsolete skills.

They allow us to solve simple problems locally and reserve AI tokens for situations where deeper reasoning is genuinely useful. ⚡

🔸 PROMPT WITH INTENTION

Before calling an AI assistant, ask:

▪️ Can my IDE already answer this?

▪️ Can a compiler or test reveal the problem?

▪️ What is the minimum context required?

▪️ Am I asking a specific question?

▪️ Will the answer provide more value than the tokens consumed?

Smart AI usage is not about generating the most code.

It is about obtaining the highest value from the smallest useful context.

The best AI-powered developer will not be the one who consumes the most tokens.

It will be the one who knows when a token is worth spending. 🚀

#ArtificialIntelligence #AI #GenerativeAI #SoftwareEngineering #DeveloperProductivity #DeveloperExperience #DevTools #IDE #IntelliJIDEA #Java #JavaChampion #PromptEngineering #AgenticAI #SustainableAI

Go further with Java certification:

Java👇

Spring👇

SpringBook👇

JavaBook👇