Hello, a lecture covering Claude Code commands has been updated in the Standard Guide to Claude Code! 😀
Since it covers almost all commands, the volume has increased significantly, leading to the creation of an entirely new section. (As a result, the subsequent sections have been pushed back by one.)
Section 2. Claude Code Core Commands
Approximately 1 hour and 40 minutes of content has been added, and the latest updates as of August 2026 have also been reflected. In the lecture, we will practice by running key commands together in the terminal. (& All were filmed using the latest version)
You might be worried about whether you need to memorize all these commands, but of course, you don't have to memorize them all. I have specifically pointed out the commands I frequently use in practice, so please refer to those sections.
I have also attached the lecture materials as a PDF file, so please feel free to download and use them!
In addition, Claude Code is currently undergoing rapid changes. To prepare for these fast-paced developments, I plan to use Claude Code in practice every day to research and share standard, effective methods.
So, with the standard practices of Claude Code, I will continue to support your learning journey and return with more helpful update news.
Hello! The "Mastering Claude Code" course has been updated with the Advanced Feedback section on Telemetry Monitoring!
This section covers the essentials for transitioning Claude Code from a personal tool to one used by a team or organization. This falls under the domain of observability, which involves transforming the logs streaming on your personal screen into queryable data for the organization.
This update includes the following three lectures.
OTel Concepts and Ecosystem
Enable Claude Code Telemetry
Collection Stack Hands-on - Setting Up otel-collector, Prometheus, Grafana, and Loki with Docker Compose
The final lecture includes the hands-on materials. It contains the docker-compose.yml and configuration files for the collector, Prometheus, Loki, and Grafana, so all four containers spin up with just a single command. You can use it to verify the overall setup on your local machine before integrating it into your company's environment. All you need is Docker Desktop running.
Give it a try, and when adopting it for your team, use it to help establish criteria for how much data to collect :)
Then I'll be cheering you on in your learning journey!
I'll be back next time with more useful updates.
Thank you.
Hello, a new section "Interview Preparation" has been updated in the Standard of Claude Code!
Have you ever experienced this? That feeling of being lost and not knowing what to believe or how to prepare after hearing things like, "AI will replace junior developers," "They don't look at algorithms anymore," or "It's okay to use AI during interviews these days."
However, we must first clear up one of the biggest misunderstandings here.
When it comes to interviews in the AI era, it is easy to assume that you need to "show off a flashy command of AI tools." However, flaunting your tool proficiency can actually act as a negative signal.
What companies look for is how you OO the results produced by AI, OO them, and OO those decisions yourself.
The updated content is a lecture covering how developer recruitment is changing in the AI era and what you need to prepare.
(I may provide additional updates for interview preparation at a point when I deem further updates are necessary.)
Please give them a listen and try applying them to your actual interview preparation :)
I will be back with more practical lecture updates.
Thank you.
Hello, the second series of the Claude Code practical tips lecture has been updated!
This topic covers Claude Code's new Agent View feature. I have summarized how to work in parallel by gathering multiple Claude sessions on a single screen.
I've tried various tools to run multiple sessions at once, but after switching to Agent View myself, I've put together some practical insights on which situations actually speed up your workflow and what points you need to be careful about.
(Practice screen within the lecture)
Have you ever experienced this? When using Claude Code, you eventually reach a moment where you think, "I wish I could run several of these at once." You want to have one instance fixing a bug, another reviewing a PR, and yet another investigating a failing test. So, you open two, three, four terminal tabs. Before you know it, this happens: Which tab was finished? Which one is waiting for my response? Is this tab still running or has it stopped? You end up clicking through the tabs one by one to check.
Agent View eliminates that tab switching. It lines up all active sessions row by row and shows you what's in progress, what's waiting for you, and what's finished, all on a single screen. Just one claude agents command opens that dashboard.
But first, we need to clear up one misunderstanding.
It is easy to perceive Agent View as simply a "screen where you can view multiple sessions at once." However, the real core is not the screen itself, but the fact that it changes the way we approach work.
In the past, when I gave Claude a task, I would sit in front of that chat and wait until the answer arrived. Work progressed one at a time, and only while I was physically present. Agent View flips this. You can assign tasks to multiple sessions, let them run on their own, and then simply handle the ones marked "Input Required" in the list like notifications. The sessions don't stop just because you leave. The unit of work shifts from "a single conversation I'm tied to" to "multiple sessions running independently."
I have updated two lectures where you can experience both theory and practice. Please give them a listen and try applying them to your actual work :)
+As a side note, the Agent Teams Operation Manual lecture, which was scheduled for update within June, has also been updated!
I will be rooting for your learning journey.
I will be back with more helpful news next time.
Thank you.
Hello, the first series of Claude Code practical tips lectures has been updated!
It is about using Dynamic Workflows, and I have summarized how they can be used in practice.
I have included the best ways to use it, based on weeks of extensive testing in the field and spending a significant amount of money and tokens.
Have you ever experienced something like this? You ask to scan an entire codebase or give a massive task involving hundreds of files, and it starts off well, but at some point, it loses steam and says "I'm done" after only finishing about half. That’s not because Claude is lacking; it's because the task was simply too large to be handled in a single conversation.
Dynamic Workflows is a feature that takes that large task, breaks it down into small pieces using scripts Claude writes on the fly, and distributes them across dozens or even hundreds of agents. To put it in one sentence - "Turning plans into code."
However, there is one major misunderstanding that must be cleared up first.
It is easy to perceive Dynamic Workflows as a "feature that launches a massive number of agents." However, launching a hundred or a thousand agents does not necessarily improve the results. The number is not the core issue.
What really matters is how you structure that workflow. Even for the same task, the reliability of the results varies completely depending on how you break it down, what sequence you flow it through, and whom you entrust with the verification.
The point is this: the value of a workflow lies not in the number of agents, but in the ability to enforce procedures that produce reliable results through code.
I have updated two lectures where you can engage in both theory and practice. Please give them a listen and try applying them to your actual work :)
I also plan to update additional content regarding this dynamic workflow in the future.
I will be rooting for your learning journey.
I will be back with more helpful news next time.
Thank you.
