Changes and Dependencies

Notes after watching the following video. Nice one.

Dependency management is an important factor for writing stable codes. Just a complex implementation does not always cause bad dependencies. Knowledges communicated among classes through message, variables and namings are the factor for adding dependency. As long as complicated or unstable implementations are hidden within the class, it may not cause large problems and could be left alone.

[Points]
1. Exposing stable public APIs
2. Hiding private behaviors
3. Minimizing the codes unrelated to the class
4. Moving out the rest (unrelated and unstable ones)

Advertisements

Posted on February 11, 2013, in Ruby. Bookmark the permalink. Leave a comment.

Leave a Reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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 )

Google+ photo

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

Connecting to %s

%d bloggers like this: