Even with perfect naming and perfect code, it is hard to read the story of your domain straight out of it. You can be certain that you’ll have forgotten of the nuances about the code the next time you see it. Or someone else sees it, because very few of us live our professional coding lives in an area where it’s only me ever handling the code. Someone is going to come back to your code – in five days, three months or five years. Luckily, if you write your tests the right way, they can tell the story of your domain in a way your production code can't. Let us show you how to create your tests so you can get rid of your stale documentation.
Surviving a National Blackout with Offline-First Architecture | Emilio Carrión
We design for high availability assuming connectivity is always present. But what happens when a nationwide power outage leaves warehouses in the dark and cloud systems completely unreachable? During a major blackout that impacted most of Spain’s power grid, Mercadona...
