Posted by: terryhowe | October 4, 2009

Clean Code: Boundaries

The boundaries chapter of Robert C. Martin’s Clean Code is one of the least interesting, but there are some points worth mentioning:

  • Using Third-Party Code: In some cases writing a wrapper for third party code can avoid dependencies in our code for the third party application.  It can limit the interface to that code to only the parts of the software we want to use making it easier to understand.
  • Write Learning Tests: Write unit tests for third-party code helps us learn that code.
  • Non-existent Code: Writing a mock for code that has not been implemented yet helps us understand what kind of interface we would like for that code.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s


%d bloggers like this: