This what we should strive for with our tests. I like how he keeps it flexible though, again it's likely a trade-off so you can't have all the properties fully all the time. Still you need to know what you give up, how much of it and why.

Excellent piece, looking back to history to justify why microservices are mostly a fad. Check what your needs really are and depending on them pick the right way to decompose the problem or organize your teams.

A bit old but interesting finding. Kind of confirms my own view about it: it's best when everyone (not just designers) can interact with the users of the system you're building.

A little reminder that those too often forgotten execution policies for C++ algorithms actually exist and can give interesting results nowadays.

Very interesting model, I didn't know about this one. As pointed out you can't really base policy decisions upon it but that's still powerful since it explains some of the phenomena at play in the real world. In this way it is enough to debunk some of the assumptions taken a bit too much for granted.