DAY 20

🔖 오늘 읽은 범위 : 10장 ~ Cohesion

<aside> 😃 책에서 기억하고 싶은 내용을 써보세요.

</aside>

• The first rule of classes is that they should be small. “How small?” We count responsibilities.
• The name of a class should describe what responsibilities it fulfills. The more ambiguous the class name, the more likely it has too many responsibilities.
• We should also be able to write a brief description of the class in about 25 words, without using the words “if,” “and,” or “but.”
• The Single Responsibility Principle: Class should have one responsibility.
• Getting software to work and making software clean are two very different activities. The problem is that too many of us think that we are done once the program works. We fail to switch to the other concern of organization and cleanliness.
• So the question is: Do you want your tools organized into toolboxes with many small drawers each containing well-defined and well-labeled components? Or do you want a few drawers that you just toss everything into?
• The primary goal in managing such complexity is to organize it so that a developer knows where to look to find things and need only understand the directly affected complexity at any given time.
• When cohesion is high, it means that the methods and variables of the class are co-dependent and hang together as a logical whole.

<aside> 🤔 오늘 읽은 소감은? 떠오르는 생각을 가볍게 적어보세요

</aside>

As the book is focused on Java specifically, I’m not sure to which level I need to follow the advice. I never write Class but I think this is a good learning for me to understand the backend code.

<aside> 🔎 궁금한 내용이 있거나, 잘 이해되지 않는 내용이 있다면 적어보세요.

</aside>

<aside> 💡 소감 3줄 요약

</aside>

• Class should have one responsibility. If you notice the Single Responsibility Principle is abused, it’s likely that the person didn’t come back to organize or clean the code after she got it working.
• You want toolboxes with many small drawers each containing well-defined and well-labeled components. This is easy for others to understand and use it too.