Illustrated with Rust in this case, but definitely one of the big advantages of having type systems. Adding constraints (even runtime ones) to your types make it harder for bugs to hide.

Nicely explain how to secure your webhooks step by step.

Very good advice. Don't waste time believing false business claims and trying to replicate them. Easier said than done though, most people don't have the privilege of insiders knowledge.

Excellent points. Don't be fooled by alluring architecture changes. Always keep the complexity in check and favor tuning what's already here or changing your use patterns to meet the performance you need.

A good reminder on how the "five why" are just a starting pont. For proper investigation and risk management you need to go deeper.

Beware of the problems coroutines might bring. Some are "obvious" and related to concurrency in general, but some are running deep in their design in C++.

Those who listen (not mandate) to their employees and hire whatever the location will come out on top. It'll require planning real estate ahead of course but the writing is probably on the wall.

Good reminder on how the W3C works and what it evaluates. If Web Environment Integrity would become a "standard" it'd likely be more of a "de facto" thing because a major player shoved it everyone's throat.

Not as detailed as I would like on the proposed solution. A good starting point for inspiration though. Should help with geospatial and fleet management problems.

Doesn't go much in depth, but this is a nice resource with interesting references to follow to dig deeper and learn mDNS.

I admit I'd love it if it made a come back. That'd be a big boost to self-hosting websites for people. Our infrastructures are not quite ready for it though.