This was a very helpful course for someone aspiring to be a backend developer. While studying development, you come across object-oriented programming, but as a learner, it was really difficult to know how to write code, what code is object-oriented, and what code is good for collaboration. In that regard, this course scratched those itchy spots for me. Of course, I think the content is difficult for aspiring developers (junior developers) to fully digest. However, I believe that the various refactoring techniques and mindset I learned from this course will gradually help me grow as I write code going forward. Thank you to the instructor for creating such a great course. Today is December 25th, and I hope everyone has a joyful Christmas and a happy end to the year. Thank you.

Thank you for the great education

The point that refactoring should be centered around the flow of thought that arises while reading code is extremely impressive. As a junior developer, when I first encounter code that needs refactoring, I often think 'Where on earth should I even start touching this...', but through this lecture, it feels like my perspective on viewing code is broadening, which is so great!!

This was a lecture that allowed me to think for the first time about what readable code is and what clean code is. Thank you!

This was a lecture where I learned many aspects about readable code that I had been missing. It's a lecture that's helping me more after getting a job than when I was preparing for job interviews.

This was a lecture that helped me get started with TDD I don't think there's a better lecture than this if you're starting TDD I highly recommend it, truly

I'm getting into test code and writing it while looking up parts I don't understand as I go, and it seems to be very helpful 😊😊

I encountered many problems while trying to write tests on my own. Should I create unit and integration tests for all layers? If so, integration tests would end up performing all the roles that unit tests are supposed to handle - what about this aspect? Another question is, there are really various cases - does creating more of these cases lead to a more robust test design? Countless questions like these arose, and this lecture seems to be one that can solve these questions. For people who can simply write APIs with controller - service - repository structure and want to study testing, starting with this lecture would be a good starting point. It was a great lecture where I could gain perspective on testing. Thank you so much!

Many developers emphasize the importance of test code. However, when explaining why test code should be written and how to write it to fulfill its role as test code, they often explain through abstract content or short examples. But this course provides relatively practical examples of test code in various contexts, along with practical content based on the instructor's experience, making it a really helpful course. For those who understand the importance of test code but are still wondering why and how to write it, I think this course would be of great help as an introduction.

Great for getting started with test code!