DAY 10

🔖 오늘 읽은 범위 : 5장 ~ Conceptual Affinity

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

</aside>

• Code formatting is about communication, and communication is the professional developer’s first order of business.
• Nearly all code is read left to right and top to bottom. Each line represents an expression or a clause, and each group of lines represents a complete thought. Those thoughts should be separated from each other with blank lines.
• If one function calls another, they should be vertically close, and the caller should be above the callee, if at all possible. This gives the program a natural flow.

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

</aside>

If it’s easy for me to read, it’s probably easy for others too. Don’t make readers to hop around between files to find where the function is.

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

</aside>

<aside> 💡 소감 3줄 요약

</aside>

• Formatting is even more important than the functionality that might change in the next release. Formatting continues to affect maintainability and extensibility long after the original code has been changed beyond recognition.
• Formatting is a rule you set and follow in the team. “Communication is the professional developer’s first order of business”
• Keep the related variables, functions close to each other while giving some room(new line) to breathe between different group of thoughts(code block).