/explore
|
You are here 
|
matthiasnoback.nl | ||
| | | | |
php-and-symfony.matthiasnoback.nl
[AI summary] The author advocates for the principle of 'don't mock what you don't own' by designing application interfaces for side effects like persistence and time, thereby improving architecture and removing brittle test dependencies. |
|
| | | | | ||
| | | | |
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. |
|
| | | | | ||
| | | | |
8thlight.com
[AI summary] The article by Robert C. Martin (Uncle Bob) discusses the strategic use of mock objects in software testing, advocating for a balanced approach where mocks are used sparingly across architectural boundaries to improve test speed and isolation while avoiding design damage. |
|
| | | | | ||
| | | | |
www.abubalay.com
[AI summary] This post discusses the complexities of creating safe Foreign Function Interface (FFI) bindings in Rust when calling C++ code, examining tools like cxx and strategies for maintaining Rust's memory and thread-safety guarantees despite the inherent unsafety in such interactions. |
|
| | | |||
