/explore
|
You are here 
|
trishkhoo.com | ||
| | | | |
agentultra.com
[AI summary] A guide offering practical tips for conducting informal code reviews, focusing on specifications, communication style, and team trust. |
|
| | | | | ||
| | | | |
blog.cleancoder.com
[AI summary] Robert C. Martin discusses specific scenarios where Test Driven Development is impractical, such as when software controls physical devices or requires manual visual adjustment, arguing that applying the methodology to these layers constitutes a misuse of the practice. |
|
| | | | | ||
| | | | |
blog.cleancoder.com
|
|
| | | | | ||
| | | | |
purplesyringa.moe
A few days ago, I stumbled upon a Hacker News discussion about the expression problem - a conundrum that occasionally arises in software design. Some of the commenters noted that Rust completely avoids this problem thanks to trait objects, and initially I agreed with them, but I'm now realizing it's not at all as straightforward as it looks. The goal of this post is to explain what the expression problem is, how Rust seemingly avoids it, why this solution doesn't actually work, and what a Rusty solution might look like. |
|
| | | |||
