Explore >> Select a destination
|
You are here 
|
www.fluentcpp.com | ||
| | | | |
tenthousandfailures.com
|
|
| | | | | I had watched a wonderful video series of Object Oriented Design Patterns on Lynda.com called "Foundations of Programming: Design Patterns" by Elisabeth Robinson and Eric Freeman. In their series, they go through some of the ideas in "Design Patterns" and have very concise code examples that illustrate specific Design Patterns. | |
| | | | |
blog.cleancoder.com
|
|
| | | | | ||
| | | | |
retro-style.software-by-mabe.com
|
|
| | | | | ||
| | | | |
jmmv.dev
|
|
| | | Dependency injection is one of my favorite design patterns to develop highly-testable and modular code. Unfortunately, applying this pattern by taking Rust traits as arguments to public functions has unintended consequences on the visibility of private symbols. If you are not careful, most of your crate-internal APIs might need to become public just because you needed to parameterize a function with a trait. Let's look at why this happens and what we can do about it. | ||
