Readable Code: Mindset for Writing Readable Code

From the test lecture to this lecture, it was a really good lecture that felt like it was taught by a really good developer and a close older brother. I am a non-major (liberal arts major), but I always remember what the professor said in college about what makes a good article and a good answer. It was that it should be written from the perspective of the reader, not the writer. I always wanted to incorporate this principle into my code while studying development and preparing for employment. This lecture seems to have acknowledged that my thoughts were not wrong. At the same time, it is a really clear lecture that clearly shows me what I need to improve in order to become a better developer. This lecture is highly recommended to those who simply use Java, Kotlin, or other object-oriented languages and use Spring and think, "I'm developing in an object-oriented way." Or, if you feel that the SOLID principles and object-oriented principles that you studied before are not well applied to your code, I dare say that this lecture will really open your eyes. Not only the object-oriented part, but also the lecture title clearly answers what kind of code is easy to read. It contains a lot of helpful content for the collaboration process and the process of rereading previously written code. After listening to the lecture, I think I understand a little why developers have such a hard time naming. If you find naming too easy, you should listen to this lecture! ㅎㅎ The content covered in the lecture is, of course, excellent, and the explanations in each chapter are also very neat and easy to understand without any unnecessary details. I think it is a really, really good lecture. I highly recommend listening to it!

Following the last test code lecture, I feel that it is a composition that increases understanding with clear explanations without unnecessary details and examples appropriate to the place. I gave up several times while reading Robert Martin's Clean Code, but after watching this lecture, I am motivated to read it again. Thank you. Please continue to give good lectures!

I've always been interested in clean code and have tried to write readable code. However, after listening to this lecture, I realized that I've only just begun to dabble in clean code. From the test code lecture to this lecture, I've really been able to improve my skills. Based on what I've learned, I'm going to try to refactor a previously completed project and learn from it. Thank you for the great lecture! I'm looking forward to the next lecture!

I got angry when I saw the code I wrote when I was a new employee 2 years ago and tried to refactor it, but I couldn't figure it out. So I watched the test code lecture and was impressed and started studying with confidence, but I regret not seeing it sooner... I've been burned out lately, but thanks to this, I've been enjoying developing lately while refactoring. When I looked back on myself simply defining functions at a specific level, I felt ashamed of myself thinking, `I'm pretty good at this, aren't I?` I'll just start studying from now on with the mindset of a 0-year employee and erase my career. Thank you. Please let me know when the next lecture comes out, whether it's a notification or something. Please, please.

While watching the previous lecture, I got the feeling that you write code very cleanly and well, but I had no idea you would prepare it like this! It goes without saying that your explanations are simple and clear. This is a lecture that really scratches that itch for those parts that anyone who writes code has probably thought about at least once. While refactoring side projects and company projects, I had been focusing on writing code that "looks clean," but it was all an illusion. I was repeatedly doing completely groundless refactoring 🫠 But since I've learned it now, all that's left is to put what I learned here to good use! Thank you so much for the great lecture 👍

The lecture content is great and everything is good, but... you type so fast. While I'm typing, it suddenly jumps to another place, so I have to keep pausing and typing along. It feels like it's progressing too quickly, and I don't really grasp what I'm doing.

educate, beyond education, educare, a lecture that brings out the power to think for yourself

I bought several courses from Inflearn, and they were as high-quality as Toby and Kim Young-han. When I learned object-oriented code from a book, I didn't understand it well, but when I performed the refactoring process one by one through practice, it seemed easier to understand. There are still some difficult parts, so I think I need to practice by repeating them until I can refactor without looking at them... The course was really helpful after I took it. I liked it so much that I bought the 'Test Code' course in advance, and I plan to take the test course after I finish the refactoring practice. Thank you for providing such a good course.