kjgkjhfkjf

It's very strange that Sundar refers to "Dr. Gebru" throughout his email. Google is generally a first-name company.

Software doesn't live forever. Good enough and soon enough is enough.

Yes, making security breaches harder for attackers at zero cost is obviously good. But obscurity does not have zero cost if it makes the system less efficient to operate. Having multiple cars in a presidential convoy is inefficient; using non-standard ports adds complexity; obfuscating data makes debugging harder; etc.

I didn't say that monads aren't useful; I said that the abstraction is unsatisfactory. The world needs a new clearer concept to use instead of the monad, just as raft can be used instead of paxos.

How many Monad explanations need to be written before we admit that the Monad is an unsatisfactory abstraction for practical purposes?

It's funny to see this in The New Yorker, because I was under the impression that The New Yorker was an elite publication where all writers aspired to be published.

Perhaps this is supposed to be the joke, since the article is labeled as humor, but I don't think that being a writer, even in the New Yorker, has the same prestige nowadays that it used to have before media became "democratized", so the joke is actually quite sad.

Realistically, the author probably should have been smart enough to realize that careers in the arts are the domain of the idle rich, and learned how to code.

You may think you're communicating friendly appreciation when you send a complementary message about someone to their manager with them cc-ed, but the message that you're also sending is that you're the sort of person who thinks it's okay to talk to people's managers about them, and you run a very real risk of losing your peers' trust.

This is not really very useful. How are we supposed to know what the companies' future growth rates will be?

Removing `const char* wuffs_base__note__i_o_redirect = "@base: I/O redirect";` removes not only the literal string, but also a global non-constant pointer. This perhaps affects various optimizations.

They should have used `const char* wuffs_base__note__i_o_redirect const =` or (preferably) `const char wuffs_base__note__i_o_redirect[] =`.

Comparing your inside with others' outsides will make you unhappy. It's important to learn not to do that, because it can happen in offline situations too.

Deleting Facebook etc. is not the solution; it seems like the author threw out the baby with the bathwater here.

Companies such as Uber tend to be biased towards growth rather than profitability, even at the time of their IPOs. Uber's layoffs are in part due to the coronavirus situation, but perhaps also due to their transitioning towards a profit bias.

It may seem counter-intuitive to invest in companies that are not biased towards profitability, as they tend to be risky and volatile, but portfolio management theory predicts that including some volatile assets in a portfolio makes it perform better. See e.g. https://www.investopedia.com/terms/c/capm.asp.

“In all likelihood, they probably don’t miss humans per se," [a dolphin expert] added. "They probably miss a free meal and the routine."

This describes my feelings about not being able to go to work exactly.

No, Niantic began as a "startup within Google". It wasn't an acquisition.

This is a nice demonstration of why exceptions, in particular untyped exceptions, are a major liability.

On-prem can make sense where your computing needs are constant and predictable. You can arrange to have exactly what you need, and the total cost of buying and operating it may be less than it would be to get comparable resources in the cloud.

If your computing needs vary over time, then provisioning on-prem for peak load will mean that some of your resources will be idle at non-peak times. It may be cheaper to use cloud resources in cases like these, since you only need to pay for the extra capacity when you need it.

No, you have misunderstood me. My point was that grandstanding posts from people who have recently left desirable positions should generally not be taken at face value. I was not arguing that his claims about Amazon's policies are questionable. This should be evident from my use of the language "well-known issues" in my original comment.

Is it not clear that I was speculating from language like "my guess is", and is it not clear that I'm not trying to cast aspersions on Tim's specific motives from language like "I don't mean to rag specifically on Tim"?

I don't mean to rag specifically on Tim here, but most posts like this one probably should not be taken entirely at face value. My guess is that he left Amazon mostly for other more mundane reasons, and he used the well-known issues with how Amazon treat their workers as a means to exit in a blaze of righteous glory.

Pick one of your unfinished projects, identify a way to make progress on it, and then make that progress. Repeat this process until all your projects are done.

Feature-wise, GCS is better. For example, it's much easier to set up a multi-region bucket with GCS.

No, it means that they will put their money into local economies other than those of tech hubs. A good thing, surely.

Working in the office has become frustrating and tiresome even for many non-introverts in recent years, due to the prevalence of open-plan offices.

What you say used to be true, but it isn't generally true any more. Conducting meetings over VC (e.g. Zoom, Hangouts) is the norm at many companies nowadays. Some companies' corporate campuses are so large that folks nominally in the same location use dial into meetings to avoid a long time-consuming walk to and from the meeting room.

k8s was actually developed in Washington.

If you ask a question at work, and the answer is in the first page of Google's search results, then you risk being ridiculed.

Saying "I looked on DDG" will not help you in this case; it will likely make the ridicule increase.

Even if we agree that the technical hurdles will eventually be overcome, I think that the problem will remain that a lot of people will want to keep their cars. Uber has provided a car-on-demand service for years, and yet in cities there is still congestion on the roads and cars parked wherever you look.

Once again, we must sadly admit that Google is a place where bad things occasionally happen, just like at every other company big and small.

Eventually git will be replaced by something better. It might not be replaced everywhere, but eventually it will be replaced in most places. This is true of almost all things in tech.

I expect that git's eventual replacement will initially boast compatibility with existing git repos.

Perhaps Google is less transparent than it once was, but once again it seems like people are lamenting the passing of a Google culture that never really existed. Parts of Google's monorepo were restricted to specific owning teams over a decade ago, and sending email to an executive would get you a talking-to from your manager if they didn't like the tone of it.

It's easy to get a job if you're ex-FANG, and often you can return to your FANG job easily (e.g. without having to interview).

I suggest you do some interviews and see how you feel about the opportunities that present themselves. Taking vacations to try doing your own thing is also a good idea.

FWIW I wish I had left my FANG job long before I did.