Explore >> Select a destination
|
You are here 
|
www.code4it.dev | ||
| | | | |
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. | |
| | | | |
marksands.github.io
|
|
| | | | | Black and White When writing unit tests using mocks, it forces the developer into whitebox testing. As the tests are supposed to drive the design, one can ar... | |
| | | | |
matthiasnoback.nl
|
|
| | | | | ||
| | | | |
fuzzyblog.io
|
|
| | | Marketing 101 : Pricing Your Software | ||
