OhNoMyqueen

They're still singled homed, right?

They just added redondancy to in/outbound routes.

He's not oversold. His major feat (breaking enigma using a computer) is miscategorized into Computer Science, where it should be classified into Computer Engineering and Software Engineering, alongside other stars like Charles Babbage and Ada Lovelace. His second major feat (the Turing Machine model) is one stone among the many foundational stones of Computer Science.

It's worse than that. The body doesn't like to lose supplies, so any calories burnt by exercise will be reclaimed by the body, which means that in any case (exercise or not) you'll need to eat less than what your body asks of you.

For some people this is cancelled by the virtuous side-effects of exercising, most notably sleep quality and low stress levels, as sleep and stress are the two most important levers on hunger/self-indulgence. For some others this is compounded by a conscious decision to allow oneself to eat sizable portions (or snack) to make for the effort, which immediatly cancels the calories deficit induced by exercice, most probably with compensation, considering how few calories are burnt by standard exercise durations.

The Spotify API doesn't support private API keys, so you need to create your own OAuth App and then authorize it for yourself.

I believe that face-to-face physical interaction is a way more determinant criteria than slacking off for making those moments productive.

> Cloud backup is a stupid idea.

I don't know what you mean by "cloud", but an off-site backup is essential. Your home can be burglarized, or burnt down, or flooded. Basically anything you insurance covers for your home you should cover regarding your data.

> At any moment it could go dark, for any reason, and you have no recourse.

There is no difference between your backup going dark or your main data source going dark. The whole point is that the data is duplicated and the odds of both of them going dark at the same time is low. This only means that you should check your backup regularly.

The most painful mistakes beginers endure with git are irrevocable code removal from the current working directory because of bad usage of `git clean`, `git reset` (or `git merge` if you're brutish enough). This problem cannot be solved by using git, because git doesn't have any reference to such code.

Bargaining power is mainly dependant on offer and demand; it can be low, or it can be high, depending on how valuable you are to the company. Pay transparency will simply increase the number of employees who will try to bargain. I guess that if you're not valuable enough that could backfire for everyone. If you do are valuable the company will just need to pay.

Great article. The only nuance it misses is that not everybody is aligned with the "desired project outcomes". From a business (and often management) point of view, the "desired project outcome" is a product that works according to the company's established standard, delivered in a timeframe that is reasonable according to the company's standard. There are some other outcomes' properties that are hidden by that, such as: How better could the product work? How faster could the product be delivered? How satisfying is it for people to create the product?

All those people with their wishes and throughts which bloat one single project usually have precious insights on how to unbloat the overall processes of creation and maintenance. It's of course impossible to fix it all in the span of a single project, but managing every project with the "it works and was delivered on time" mindset is the best way to tank the overall productivity of the company and lose developers, because you missed the insights they had about to improve what they do, and do it well, and do it efficiently.

The issue with this argument is that a significant part of the "bigger picture" is artificial bloat which emerges from the fact of having layers of management. Managers spend much time actually managing themselves. It's of course not all black or white.

This is exactly how FLoC is supposed to work, and this is exactly what privacy watchdogs have criticized about it.

The proper headline should be "Ad tech films test FLoC".

Thanks. TL;DR: chess.com is closer to FIDE than Lichess.

Thanks for the explanation. Do you know which one would be closer to FIDE or club ratings?

I'm shoked by Lichess ratings. The graph indicates that 1380 Elo ranks you above 36% of Rapid players. On chess.com, 1200 Elo ranks you above 80% of Rapid players.

That's also not specific to non-profits.

I think it was bad wording. Those salaries are sky-high, but they're about average for those kinds of positions.

I love their philosophy of ever improving performance and memory usage. Sublime is one of the last gem resisting Wirth's Law.

> When watching the WC games, I've seen it happen that a move wasn't considered as a top move by the engine, but once played the engine realizes it's actually crushing.

You don't need to watch WC game to witness that. Any position sharp enough will have swinging evaluations at the search horizon, and even amateurs can find a twist in their favor if they're lucky enough (to have their 8-moves ahead flash of genius actually work 20 moves ahead by complete chance).

In decent engines the heuristics used to prune the search tree range from exact (e.g. alpha-beta prunning) to conservatively innexact (low chance to actually miss something), and unless you find a systematic winning or drawing pattern (like the examples in OP's article), you can't beat the engine with your "intuition".

Was it actually configured with "no draw" policy? The chess.com explains that Rybka thinks it's winning because of material advantage.

My experience to increase book bandwidth is to read more, not to read faster. That is, allocate more time of the day to reading.

They could do the equivalent of those images comparing Full HD and 4K side-by-side, by having a button "with MightyApp" which reduces CPU load and makes your fan stop.

It's not necessarily true. Some people are conservative and have forgotten the reason why.

> Nearly everyone I've spoken to has reported that WFH productivity has been equal, if not better than pre-pandemic.

Labor productivity there is no doubt. Overall productivity is something else entirely, since it is optimized by reducing the amount of labor needed. I've seen projects being spared what would have been _months_ of useless labor because the right person was walking back from his coffee break and overheard some discussion he had an insight about.

It's just an annecdote of course, but it's hard to evaluate the evolution of overall productivity when WFH. Especially since it depends on the existing culture of the company, so even success stories like Gitlab can't be used as a proof of anything.