Concerns Part 2 #48
Open
Concerns Part 2 #48
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
April 28, 2023 15:50
tradesmanhelix
force-pushed
the
asmith/concerns-part-2
branch
from
4f0b325 to
64f4f78
Compare
|
Hi @stockandawe - part 2 should be ready for review. Thanks! |
stockandawe
reviewed
May 23, 2023
| excerpt: Pitfalls and best practices for using concerns in Ruby. | ||
| --- | ||
|
|
||
| Welcome back! [Last time]({% link _posts/2023-04-24-concerns-in-ruby-part-1.md %}), we discussed the basics of concerns in Ruby and saw a few examples of how to use them to share code across otherwise-unrelated sets of classes. We then took a detour with the goal of understanding, not just what concerns are, but also how to use them well. As part of that detour, we defined good software as, "software that can change inexpensively." We said that the concept of "inexpensive" encompassed a myriad of factors including time, money, and effort. |
There was a problem hiding this comment.
You could use {:target="_blank"} so that the link to post 1 opens in a new window and the reader can continue reading this post .
stockandawe
reviewed
May 23, 2023
| #### Visualizing Class Relationships | ||
|
|
||
| The following provides nice visualization for inheritance, composition, and polymorphism: | ||
|
|
stockandawe
reviewed
May 23, 2023
|
|
||
| Classic! Steve can help us out here too: | ||
|
|
||
| [TODO: image here] | ||
|  | ||
|
|
||
| So, next time you sit down to write some code, consider chanting, "Messages, messages, messages," as a way to remind yourself of good software design principles. | ||
|
|
||
| ### The Story so Far |
There was a problem hiding this comment.
Good idea to include a summary of "the story so far"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part 2 of the "Concerns in Ruby" blog post series.