Explore >> Select a destination
|
You are here 
|
adamstorr.co.uk | ||
| | | | |
www.devjoy.com
|
|
| | | | | Site template made by devcows using hugo | |
| | | | |
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. | |
| | | | |
darekkay.com
|
|
| | | | | Pitfalls with partial unit test assertions. | |
| | | | |
lisacrispin.com
|
|
| | | The Twitterverse and other social media continue to host many discussions on topics such as "Do testers need to code?" As Pete Walen points out in his recent post, the "whole team" approach to delivering software, popularized with agile development, is often misunderstood as "everyone must write production code". The "Whole Team Approach" in practice [...] | ||
