First of all, I really enjoyed Toby's session. While watching the lecture, I think I looked back on not only clean code but also my life. First of all, I remember that the book Clean Code was popular in 2019, and the job postings also included information about clean code. I read Clean Code back then. I blindly followed it. I even thought that writing comments meant that my code wasn't clean! However, thinking back now, it seems that writing perfect (clean) code at once is very difficult for me, even now. And I also started to think, is it right to blindly follow the contents of Clean Code 100%? Reading the Clean Code book and memorizing it all? Is that really clean code? Then, how should I solve examples and cases that don't appear in the book? I think that's what I'm thinking now. In the end, I think that clean code is something that is easy to maintain and easy for everyone (team members) to read. In some ways, I thought that even though it is not perfect for me, code that is readable enough for the team level could be clean code. I also think that I am worried about how to maintain clean code continuously. When maintenance is done, new code comes in, and that code that comes in could ruin the clean code. In order to change that broken clean code back into clean code, I would have to spend time refactoring, and I felt once again that test code is needed. And after seeing the lecture content, “Code that is friendly to fellow developers who write, read, and change code together,” I thought that clean code should also become a team culture. Lastly, as Toby said, I thought that I was carrying too much burden and worrying alone. I thought that I was lacking and that I was living like this. If I worry and talk with my teammates, not only will the time I suffer alone disappear, but my teammates will also grow together. I reflected on this. And I began to wonder if I was really kind to others. It was a time when I looked back on myself and thought, “Haven’t I been too unkind by not understanding me?”