The goal of this category is 3 answers you can give on the spot in an interview.

• ▸✅ "Do you use Maven or Gradle?" → An answer backed by reasoning (speed, expressiveness, team context) — both are tools that bundle code into an executable
• ▸✅ One-line explanation for your IDE (Integrated Development Environment — a program that combines code editing, execution, and debugging) choice (Java/Spring → IntelliJ, JS/TS → VS Code — with reasons)
• ▸✅ The role of each of the 6 tools developers use every day (IDE, build tool, API tester, DB GUI, terminal (the black screen — controlling the computer via commands), Git)

Learning Order

1. IDE + Terminal — VS Code / IntelliJ shortcuts + shell (the terminal command interpreter) basics
2. Build + API — Maven/Gradle + curl (a tool for making API calls from the command line) / Postman
3. Vibe Basics — Reading errors + debugging + npm/pip virtual environments (isolating libraries per project)

At the end of each lesson, you'll find common interview questions and how to prompt AI for that topic.

In one line: The difference between writing the same code 10× faster lies in mastery of your tools.

Tool Mapping — The English in each cell is just the tool name; focus on the description beside it

5 Key Reasons

The bottom line: The gap between someone who knows their tools and someone who doesn't = doing the same work 10× faster through tool mastery.

Q: Do you use Maven or Gradle?

A: New projects → Gradle. The DSL (Domain-Specific Language — dedicated syntax for configuration) is more expressive and incremental builds (rebuilding only what changed) make it 3–4× faster. If the existing team uses Maven, stick with it — switching build tools is a high-cost decision. The official Spring Boot guide also recommends Gradle first.

Q: What's the difference between VS Code and IntelliJ?

A: Java/Spring → IntelliJ — static analysis, refactoring (restructuring code for clarity without changing behavior), and debugger quality are unmatched. JS/TS/Python → VS Code — lightweight with a broad extension (plugin for adding features) ecosystem. In practice, professionals use both (IntelliJ for backend + VS Code for frontend).

Q: Do you use curl or Postman?

A: curl for quick checks, Postman for a Collection to share with the team. For automated runs in CI (Continuous Integration — automatically testing on every code push), use Newman (the Postman CLI command-line tool). REST Client extension (VS Code) is also common — calling endpoints via a .http file right next to your code.

Q: Are you comfortable with the terminal? What commands do you use often?

A: grep · find · sed · awk — the four text-processing essentials. ssh · scp · rsync — remote work. ps · top · htop — checking processes (units of running programs). Git commands directly — beyond aliases (git log --oneline --graph, git rebase -i HEAD~5).

Q: What IDE extensions (plugins) would you recommend?

A: For VS Code: GitLens (blame — who wrote this line and when), ESLint, Prettier, GitHub Copilot, Error Lens, Path Intellisense. For IntelliJ: GitToolBox, Rainbow Brackets, Key Promoter X, .ignore. For both — a color theme (Dracula / One Dark Pro).

Knowing the concepts in this lesson lets you give AI specific instructions. It's the starting point for saving tokens (the unit of text AI processes at a time).

• ▸"Make a comparison table of 10 Git integration shortcuts between VS Code and IntelliJ."
• ▸"Convert this project's pom.xml to build.gradle.kts."
• ▸"Convert these curl commands into a Postman Collection JSON (a file that stores a group of requests) so they can be run with newman in CI (the automated build and test pipeline)."

Why This Reduces Tokens

Knowing the vocabulary for IDE, build, and API tools means you can receive AI responses directly as commands or config files. Without knowing the tool names, you have to start over with 'Which tool should I use?'