Book Review: Clean Code: Chapter 8. Boundaries

This is review of the 8th chapter from the book-”Clean Code: A Handbook of Agile Software Craftsmanship” by Robert C. Martin

Boundaries are the points when your code meets with code written by others- where you have little control on what they deliver. e.g. when you use a third party software like PCMiler for distance time lookups.

It’s good to buffer these boundaries with Adapters so that your dependency on third party software isn’t widespread and when the third party software changes- you have one place to go and make the change.

Robert also talks about “Learning Tests”- these are special tests written to test the third-party software. They can be used to validate later releases.

Also boundaries are not limited to third-party software - they can also refer to sub-components developed by an independent and a separate team.

For reviews of other chapters- please see this post.