My interview performance actually got better once I stopped overdressing. I got more offers wearing a grey hoodie and jeans. And this was at big tech (not just startups).
The FIU bridge is truss bridge, not a cable-stayed bridge, see this NTSB update [1]. The bridge collapsed because it relied on a single truss with no backup to support the weight if it failed. This created a single point of failure where the collapse of any member (diagonal segment) would collapse the entire bridge.
There is no indication that ACB contributed to this collapse, rather, this was a faulty design that would have also posed a risk using traditional construction techniques.
There's a lot of talk here about TCP vs UDP vs SCTP vs x protocol.
It's important to keep in mind that this is all optimization. Don't lose sight of the big picture.
On one RTS we ended up just serializing world state over a TCP socket. If you can get away with the brute force approach then just do it. Don't optimize until you have a measurable performance problem.
Yep. The WHATWG recommends just using the term URL instead of URI.
> Standardize on the term URL. URI and IRI are just confusing. In practice a single algorithm is used for both so keeping them distinct is not helping anyone. URL also easily wins the search result popularity contest.
The biggest thing for me is that you can use secure WebSockets (wss://) without having to setup TLS on your origin server. This greatly improves the ability to establish WebSocket connections across proxies.