hn_go_brrrrr

> I often wonder how much of their tech stack made it into the larger Google org.

Very little, though that may be changing. Most of YouTube was written in Python, which is essentially unknown for a production system at Google.

> Example; for the longest time when you'd log into gsuite via a SAML IdP you'd notice a youtube url in the login flow.

This was just to set the YouTube "logged in" cookie.

You're dead wrong on Pixar being in #2. Cars is an absolute money printing machine.

He can change his middle name again. It's not like the government will require him to produce the private key to do so

Your unit was undersized for the load. It's no different than having a too-small furnace.

Could you install the ones that come with precharged linesets?

Absolutely. A mini split system is perfect for this use case.

Good observation. I had assumed each company had their own instance, but that's not necessarily true.

It could also be a legacy of a lot of the team coming from Google, which statically links everything except glibc.

You should use a local-storage password manager, like KeePass.

> Never trust any company with a PR department at all

So you're saying we should trust Twitter? :)

We're missing the time component right now. It's still recent tragedy.

I don't get it.

Vint Cerf

No, C++ has nothing better.

"Undocumented" is the current preferred euphemism for "illegal immigrant".

You're describing a prescriptive vs performance certification route. The former gives per-component minimums, the latter whole-assembly minimums. Most codes allow both, but most builders choose prescriptive because it requires less thought.

Mistakes due to ignorance, presumably?

I think you'll find implementing a type-safe print function in C++11 very challenging. What you could do in constexpr was very limited, type deduction was less powerful, and it didn't have fold expressions. I'd say this really only became feasible since C++17.

I don't like Init methods because they permit the creation of invalid objects. Instead, either throw an exception from the ctor or use a factory function that can either return a T or an error.

I'm curious what weaknesses of shared_ptr you've found. With the addition of weak_ptr and enable_shared_from_this, they're a pretty versatile tool.

Normally I don't comment on typos, but RIAA instead of RAII is a pretty funny one.

Disagree, unless we're including Rust's unsafe. Excluding that, you need to understand what the Rust compiler is able to prove is safe. In C++, you "just" need to prove to yourself that it's safe. It's a very different experience writing code.

In lawyer's fees or in damages?

...what happened here?

I've never been asked to sign an updated contract for a job.

They've already considered that and come back with a resounding "yes".

At which point Musk wouldn't own Twitter anymore, like he wanted. It sounds crazy, but is this his exit strategy?

I hope in a few years we'll be able to add Pat Gelsinger and Intel to that list.

And if you can only do one, air sealing is almost always preferable.

I read that, having received a similar recommendation, but after I finished it I had no idea how to translate that into my own job (I do not manage a factory).

Not even once.