Even Golang de facto suffers from this. I don't think I can name a time I saw someone check the return value of fmt.Print or log.Print. Not checking the return value still seems the the "right" thing to do.
Someone more capable than I should make the final form of this: No green or yellow feedback is provided, but only the timing information used to calculate it. If cryptographers are serious about side-channel attacks, why not show off the danger using no-information Wordle?
The best piece of advice I heard for reading financial reports: start at the bottom, read your way up. All the juicy stuff is hidden in the bottom (like losses), while the pretty, extrapolated ARR graphs are up at the top.
gRPC Java wins in part due to not allocating memory when reading and writing buffers. It uses Java-based implementation of jemalloc (via Netty) to manage its own memory. No/low allocations means the GC doesn't need to wake up so much.
For those of you here that have hit your FIRE number: have you ever brought this up with your manager or potential new company? I'm in this position myself where I don't have to work any more, and mainly just want a fun job. I don't want to be underpaid for the value I'm providing, but I also don't want to be jerked around.
"Rich Dad Poor Dad" also made a similar point: you should look at what your advisor is doing, rather than taking their advice. If your financial advisor suggests a mutual fund, ask them if they themselves invest in it.
A different way of thinking about it would be considering each Olympic trial as a voter and use gold/silver/bronze as 1st/2nd/3rd in a ranked-choice vote. Each "contest" effectively votes on a country.
Up until the beginning of 2020, NFLX was the highest growing stock of the decade. (Dethroned by TSLA) In terms of percentage growth I believe it still outperforms every other component of FAANG.
> Any protocol designed for the TCP transport must have been designed to work in concert TCP mechanics, not fight, or try to workaround it.
There is a reality of running code on other peoples hardware: they impose limitations on network traffic that you cannot change. Example: Home-grade routers do NAT, but have table limitations which make it hard to have multiple connections. The connections get dropped, and users complain, not realizing it was due to them having bought a cheap router. Other actors in the network path between the client and the server impose their own limitations, making it hard to have multiple connections. (corporate firewalls being another big one).
HTTP/2 is a compromise, admitting that it is not possible to go fix or replace all this hardware. I worked on a few HTTP/2 implementations, and the complexity it incurs is significantly less than the alternatives.
Buffett is pretty much the exact opposite of a boglehead. Buffett's strategy is to only pick winners. Jack Bogle was in the portfolio theory camp, buying companies regardless of if they appeared good or bad. Both can be profitable, but the boglehead strategy is much easier to do.