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

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.

hello.

It's already been three months since I started teaching for the first time.

It seems like a boring topic from the very beginning

I had a lot of worries,

Still, many people showed interest

Thank you very much.

Due to job change, etc...

There are various changes in my appearance,

Preparing for the next lecture

It's taking a little while, but

We will actively consider your various feedback.

The weather is getting quite chilly now,

Everyone, take care of your health.

thank you