강의

챌린지

멘토링

로드맵

커뮤니티

Legacy Java Refactoring: From Deciding What to Change to Hands-On Practice in IntelliJ IDEA

When fixing legacy Java code, determine what to change and which behaviors to preserve. In the existing IntelliJ IDEA hands-on exercises, you directly review code changes, while in the 16 newly added theory lessons, you learn about names, functions, duplication, responsibilities, calling contracts, and validation criteria.

(4.7) 6 reviews

122 learners

Level Basic

Course period Unlimited

Java
Java
IntelliJ IDEA
IntelliJ IDEA
Refactoring
Refactoring
Java
Java
IntelliJ IDEA
IntelliJ IDEA
Refactoring
Refactoring

16 New Theories Added: Refactoring—First Decide What to Change and What to Keep

Hello, this is Hancorp.

(Previously, it was called “Rice Maturing Humbly,” but I changed it because the name was too long. 😅)

We’ve added 16 theory lectures to the existing IntelliJ IDEA refactoring practice course.


If the existing hands-on exercises showed you how to change code using Rename, Extract Method, Change Signature, and more, the new theory covers what you need to determine.

• Decide which behavior to preserve and establish an order for small changes and verification

• Determine the boundaries of names, functions, duplication, data, and responsibilities

• Preserve how callers use it, make only the necessary changes, then stop.

• Examine duplication and conflicts in AI instructions using the same criteria

If you have already taken the practical course, you can continue with the new lessons in sections 7–12 of the curriculum.

If this is your first time taking the course, start with the first three lessons on the new theory to establish criteria for changes and verification, then apply them in the practical exercises.


Please leave a question about which judgment was the most difficult for you while taking the course, and I will use it to inform future content.

I’ll refer to this when refining the explanation.

Thank you.

Comment