Ironically Workday is the worst product to use as a job seeker to upload your resume.

It was always there. Just don't train the model with data that you don't like.

It can't fall out of favor if it was never really in favor to begin with. GraphQL was a quite brief hype then a big technical debt.

You can even do neat things like having the revalidate fetch tell your backend “I served this object out of cache 1100 times since last fetch, maybe consider putting a few extra cpu cycles into the compression on this one”

Ok I'm going to come out and say it because I think multiple people in this thread have hinted at the same confusion: What bloody kind of oil are we talking about here? Whale oil, that somehow was captured in the bones? Petroleum oil from the whale's encounter with the tanker? They basically buried the lede on this story and nowhere appear to explain why this particular whale is dripping some kind of "oil" that seemingly other museum example don't experience. So - anyone got any insight here?

> I won’t fall into the trap of trying to define Monads in this post. Instead, let’s talk about monadic-style APIs – that is, APIs that allow you to do a bunch of things one after another, with the ability to use the result of a previous computation in the next computation, and also allows some logic to happen between steps.

Am I crazy, or did he just give a really good definition of monads in programming? I think that it benefits by not letting itself get bogged down in Category Theory nomenclature which doesn't actually matter when programming.

Fixed installations don't need more efficiency. We have plenty of room as is. The price per watt is more relevant and even that has become trivial, as installation costs trump panel cost. We mostly need more panels installed everywhere.

When you sit down at the dinner table, do you have your own fork or share one with the guests?

Exact same logic applies.

I hate that with passion. Though I don't know the technical reason behind this workflow.