eep_social

Both missing companies were included recently, suggesting to me that the author used an older dataset.

At a glance, I think the author used S&P sector categorizations. They were set in 2018 and intentionally split the mega caps/FAANG/MAG7 across multiple sectors based on some hand waving about “primary” revenue source at that time.

From a finance perspective I think they’re a _little_ weird but functional (NVDA moves with semis, MSFT with software, etc) whereas from a tech perspective I’d say very weird until you learn about the backstory and what motivated it.

I think you’re responding to “gaming” and thinking of AAA titles which are flashy and splashy but are a smaller market than mobile games. I guess gp might have been thinking of mobile or casual where Apple does have a significant stake and interest but no appreciable focus.

you most likely have an Abe in your contacts, I don’t have an Abe but have a similar issue with a last name from mine. the behavior sort of makes sense if I squint and crane my neck around a bit but I have no idea how the weightings are so bad.

Not that he got it all right or anything like that but it’s amazing how much of the current macro discussion around AI capabilities is covered in the Foundation series which was published over many years, 1942 to 1993.

I definitely do not know the feeling you’re describing.

My favorite quirk of mine is aphantasia but kids are more entertained by ear wiggling.

> when Amazon was first established, one of the largest loopholes that they had used..

I thought for sure you were going to mention USPS “media” rates which allowed Amazon to ship books very cheaply.

Interop standards for this like Open19 are not widely deployed and without interoperability it’s a dead end since you need the hosting provider to give you the drop to your rack or cage. Hyperscalers I don’t know, but I’d guess they don’t deploy rack density that calls for liquid cooling yet.

What you said is not what the linked video says, so at best this is terrible advice piling onto terrible advice.

Phone numbers have become the unique identifier used to build profiles of people and the providers can still claim “security” when they change it to pursue that revenue stream.

“great UI” and “burned to death because the door handle wasn’t” is a bold juxtaposition

My understanding is that as people age their skin stays drier and causes this issue.

The parent post is a chef’s-kiss-perfect illustration of the problem with modern tech.

which is why you went with Delta and not Nocturna I would think? Deltas are fine in an otherwise noisy environment but they’re misery in say a bedroom at night.

I have also flown out of that airport. The early flights maximize viable onward connections but the logistics are a real pain.

He’s a hack, now you know.

If you tap into the address bar, start typing your search, type enough for it to be specific enough that autosuggest crap clears, and “On this page” appears. Wildly undiscoverable in practice.

In a similar vein, I remember encountering a site where the frontend enforced basic complexity requirements ala “use at least one number and one symbol” but the system would silently drop all non-alphanumerics when it saved (presumably in some kind of failed conversion on the way into the backend DB). So setting a password like “foo_bar4!” would become “foobar4” which was surprising. What blew my mind though was when I figured out the stripped password worked to log in, which was how I eventually figured out what was happening, escaped the reset flow, and generated a compliant password.

Unlike equity options, commodity future options are typically written with european style exercise rules.

based on my experience, I suspect the latter

similar, user-hostile behaviors I have found include:

- wifi network passwords are persisted through a system wipe and reinstall in recovery mode - a phone home is required by an activation step during installation - bluetooth is always re-enabled after an upgrade

US dollars or equivalents mostly, money market funds, treasuries, sgov, etc

as an american I might call those “local ordinance” when they come from a smaller rulemaker like a town

edit: op also has this, disregard

hugged but someone caught it: https://archive.is/VrEtg

A company I worked for used start date anniversaries rather than birthday for a variety of reasons.

> bottom management

“line management” is the term I am familiar with

in high scale stateless app services this approach is typically used to lower tail latency. two identical service instances will be sent the same request and whichever one returns faster “wins” which protects you from a bad instance or even one which happens to be heavily loaded.

surely gp was referring to HD ;)

I wasn’t in C++ style land but my recollection is that distilled experience would be backed up by extensive mailing list discussions. in case of contention the discussion might extend into case studies or other quantitative techniques atop google3. It’s difficult for me personally to describe the impact (outsized)of a super-resourced monorepo for this kind of thing. also as gp mentioned, it was sometimes possible to automate changes to comply with updated guidelines.

My understanding is that the hardware is always installed but the dealer will not fill the liquid reservoirs unless the customer specifically requests (and pays) for it.

Not sure what you mean. His legacy to date is ruining the iphone because he couldn’t think of anything to do beyond “thinner”.

I think six dev teams is small in terms of kube. I wouldn’t be surprised if that’s close to the perfect size to move onto kube and create and adopt a standard set of platform idioms.

at orgs significantly larger than that, the kube team has to aggressively spin out platform functions that enable further layering or risk getting overwhelmed trying to support and configure kube features to cover diverse team needs (that is, storage software doesn’t have the same needs or concerns as middleware or the frontend). this incubator model isn’t easy in practice. trying to adopt kube at this scale is very challenging because it requires the kube team to spin up and out sub-teams at a very high rate or risk slowing the migration down to a crawl or outright failure and purchasing e.g. off the shelf AWS because teams need to offboard their previous platform.