nxb

Talking about another country.

Regardless, US culture says that this sort of thing gives the employer far too much power over the employee, and that there are plenty of unscrupulous employers who use that leverage against the employees to make them do what they want, far beyond what the US considers appropriate.

EEU culture typically says the world is far worse without these books and that there couldn't possibly be any downsides that outweigh the costs, or that there are bandaids which could theoretically fix any problems with it.

Neither side will likely ever convince the other side on this topic, so no point in arguing about it :)

South Eastern Europe. I'm curious about how common it is elsewhere in Europe too.

No, we're talking about something vastly more invasive. Beyond a certain extreme, they become very different things.

But go talk to some people who've only ever experienced these types of business cultures, and they'll start listing for you a ton of reasons why it would be IMPOSSIBLE for the business world to operate as well or better, if it were any other way.

These slavery books are still pretty common in parts of Europe too.

It's a region-level culture I'm talking about. In this case, I was thinking of Eastern Europe culture.

You're in for a MASSIVE culture shock, if you ever get employed there. For this, and many other reasons. The cultural expectations in business are often the far opposite of that of the US.

Don't forget that individuals and group culture are two distinct things, but both are very real things. Let's be clear about which one of those we're talking about.

Worst is the whole country's cultures who really believe that each person can only be great at one single thing. Being great at multiple things? Impossible, right?

Is there a document that lists out Redis best practices like "Redis is very fast as long as you use O(1) and O(log_N) commands"?

Sure it's probably all obvious things, but it would be nice to have a checklist to skim over, to be sure I haven't forgotten any major consideration when designing a new system.

The top chart looks correctly formed, but you may be right about the bottom chart on that page: "Probabilities For Years Left to Live".

If I'm reading correctly, it seems they tried to deduce the bottom chart from the top chart, which is not appropriate for the reason you wrote.

The top chart only considers ONE year into the future from TODAY, based on someone's age TODAY. More specifically -- It's a chart for survival analysis (predict rate of failure, based on a certain fixed time period and a certain starting date) not life expectancy (predict the time period over which a certain fixed rate of failure occurs, based on any future date.)

The bottom chart though, should be far more influenced by the predicted increase in life expectancy -- since it would have to account for decades of predicted average life expectancy improvement, instead of just increase in average predicted life expectancy over one year, which probably has a negligible effect on the top chart.

Each fundraising is literally a mini-exit, especially B-series and beyond, where founders are often allowed to liquidate some of their shares.

The reality is more fluid and less black and white.

So what's the best OSS search autocomplete these days? Solr's, Elasticsearch's, Linkedin CLEO?

Someone pasting that template to a client is doing the opposite of "honest" communication :)

A moody client could see it as insulting to their plans or project.