DAY 13

🔖 오늘 읽은 범위 : 7장

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

</aside>

• Use Exceptions Rather Than Return Codes
• Try to write tests that force exceptions, and then add behavior to your handler to satisfy your tests. This will cause you to build the transaction scope of the try block first and will help you maintain the transaction nature of that scope.
• If you throw a checked exception from a method in your code and the catch is three levels above, you must declare that exception in the signature of each method between you and the catch. This means that a change at a low level of the software can force signature changes on many higher levels.
• This is called the SPECIAL CASE PATTERN [Fowler]. You create a class or configure an object so that it handles a special case for you. When you do, the client code doesn’t have to deal with exceptional behavior. That behavior is encapsulated in the special case object.
• Returning null from methods is bad, but passing null into methods is worse. Unless you are working with an API which expects you to pass null, you should avoid passing null in your code whenever possible.
• Clean code is readable, but it must also be robust. These are not conflicting goals. We can write robust clean code if we see error handling as a separate concern, something that is viewable independently of our main logic

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

</aside>

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

</aside>

<aside> 💡 소감 3줄 요약

</aside>

• Returning null from methods is bad, but passing null into methods is worse. ➡️ never thought about it because I see it very often, everywhere.
• Try Catch rather than console.log(error)
• Try to write tests that force exceptions, and then add behavior to your handler to satisfy your tests. ➡️ TDD. I’ve never tried this so far mainly because I don’t see a very clear benefit of it. 🤔