Lectures

Tommy gets his first real assignment — to build a landing page for a client. But the stumbling block is not the landing page itself, it is WHERE to build it: it is time to move out of the familiar browser panel and into a real development environment.

Tommy discovers that building a page is only half the battle. The hard part is knowing WHAT it should contain. And that meaning is not in the code, but in people’s heads: the client’s and Tony’s. A lecture about how a question becomes a working tool.

One panel in the browser is not enough: Tommy moves to IntelliJ IDEA. We look at what a plugin is, why the Claude Code plugin is a bridge to the already installed agent and not a second agent, and why having two workspaces at once is perfectly normal.

Tommy calls the AI agent directly inside the IDE and sees for the first time how the edit appears live in the open file. We figure out that it is the very same agent as in the browser — just on a new surface.

Tommy asks Sam to write a 2048 game in one sentence — and runs into “No spec, no result.” We break down why an AI agent brilliantly writes code from instructions and stalls without them, and how a vague wish gets turned into a list of requirements.

How to work through JavaRush tasks right inside IntelliJ IDEA: where to find the task list and the requirements, where to write your solution, how to submit it for review, where to see the result and which plugin settings are worth knowing.