I found it interesting that the bettors who threatened the journalist accused him of being motivated to manipulate the market. The journalist was motivated to report honestly, the bettors were the one trying to manipulate the market by changing the reporting.
The prequel “Message Passing Is Shared Mutable State” makes the claim that highly scrutinized go codebases had just as many message passing bugs (using go channels) as shared memory bugs. But then this article claims the Erlang community has a record of higher quality and reliability largely through discipline and convention.
At another BigCo I am familiar with any external communications must go through a special review to make sure no secrets are being leaked, or exposes the company to legal or PR issues (for example the OP).
It raises an interesting point. Code review is as much about educating the author of the code as much as ensuring the quality of the code. Why invest time providing feedback to a brick wall? LLMs aren’t going to “learn” from your feedback.
It is a classic cooperation problem. Perhaps not prisoners dilemma. Perhaps not at individual scale. Probably tragedy of the commons.
Cooperation is not consuming fossil fuels. Defection is consuming fossil fuels.
If you cooperate and other defects you suffer climate impact and expensive energy (expensive everything, worse economic growth than others).
If you defect and other cooperates you suffer climate impact but at least you get cheap energy (cheap everything, more economic growth than others).
People, nations, corporations, etc don’t stop using fossil fuels because they incur a penalty against their competitors if they volunteer to and their competitors don’t.
I think a lot of web services talk about reliability in terms of uptime (e.g. down for less than 5 minutes a year) but in reality operate on failure ratios (less than 0.001% of request to our service fail).
Can you share more about education in the USSR? My impression is that for all its faults, education is one area where the USSR excelled, with very high standards and outcomes.
The distinction in the article really is between calling malloc for every added node in your data structure (“pointer”) or using the pre-allocated memory in the next element of an array (“index”).
California has the opportunity to be a beacon in North America for environmental and climate action e.g. by expanding solar production, finishing the CAHSR, and other projects like expanding and electrifying mass transit and commuter rail networks, but they are their own worst enemy.
A telnet terminal isn’t a terminal by this logic because the text isn’t rendered on the server. A telnet server sends data to your device and your device renders it.
I believe you are interpreting “business need” as “commercial need” when I think it’s more like “what is your business here?” Purely anecdotal, but when I visited Moffett Federal Airfield to visit the aviation history museum there I asked the security guard at the gate checking my ID if I could ride my bike around the base afterwards. He said I needed a business purpose to being on the base and that visiting the museum was a business purpose but biking around aimlessly wasn’t.
I have experience with token bucket and leaky bucket (or at least a variation where a request leaves the bucket when the server is done processing it) to prevent overload of backend servers. I switched from token bucket to leaky bucket. Token bucket is “the server can serve X requests per second,” while leaky bucket is the “the server can process N requests concurrently.” I found the direct limit on concurrency much more responsive to overload and better controlled delay from contention of shared resources. This kind of makes sense because imagine if your server goes from processing 10 QPS to 5 QPS. If the server has a 10 QPS token bucket limit it keeps accepting requests and the request queue and response time goes to infinity.