강의

챌린지

멘토링

로드맵

커뮤니티

Practical Harness Engineering for Senior Engineers at Korea’s Top Tech Companies: Claude Code in a Real-World Spring Boot Environment

This is the definitive course on Claude Code. We’ll delve into how and why Claude Code works all the way to the end, teach you how to apply the components of harness engineering yourself, and even dissect publicly available production code firsthand. Take the know-how of a developer with 10+ years of industry experience and become a key talent in the age of AI agents.

(5.0) 43 reviews

553 learners

Level Intermediate

Course period Unlimited

Java
Java
Spring
Spring
software-design
software-design
AI
AI
AI Agent
AI Agent
Java
Java
Spring
Spring
software-design
software-design
AI
AI
AI Agent
AI Agent

[Claude News] Opus 5.5 Released! It’s Better Than I Expected!

Hello, students!
Claude’s new model, Opus 5.5, has been released, and we’re excited to share the news :)

Have you ever worked with Claude Code, supplemented your explanations several times, but still failed to get the desired result and ended up finishing the task yourself?

With this model, it would be a good idea to have it tackle tasks that didn’t go well before and compare the results.

And the speed has become noticeably faster. I’ve also switched everything I was running on fable 5.1 at work over to opus 5.5, and it feels much smoother. The quality of the answers also feels clearer and cleaner.

There are three changes worth noting in Anthropic’s official announcement.

  • Improved performance on complex coding tasks: It is said to have improved on lengthy, multi-file tasks such as migrations that modify an entire codebase and large-scale code reviews.

  • Speed and cost improvements: Compared to Opus 5, output generation is reportedly more than 30% faster, and execution costs for typical tasks with the default settings have decreased by approximately 40%.

  • More readable explanations: It is said to have been improved to present important information first and explain the results and reasons for changes in an easy-to-understand way.

스크린샷 2026-09-24 오전 9.24.29.png

When trying it yourself, start with a task whose outcome you already know. Give it a previously fixed bug or a feature that took several requests to complete, under the same conditions.

Comparing whether the results are correct, how much intervention is needed along the way, and whether it explains the reasons for its revisions convincingly will help you assess how useful it can be in your work.

You could also redo the exercises from the course using Opus 5.5. Try applying the process of organizing requirements, defining the scope of the work, and verifying the results as well :)

Then, I wish you all the best on your learning journey.
Thank you!

Comment