cvik

I agree with everything you say.

Good teams don't blame individuals. You can praise individuals, but you take blame as a team.

Hopefully at least two people reviewed the commit before it was put into production. Someone set up the post-launch smoke-tests/api-test-suits. Someone built the CI/CD-system. Etc etc.

My point is, it is rarely a single individuals fault when something at this scale goes down.

>I think we should also start with 6 hours work days or 4 days 8 hours.

I hope you are not alluding that Sweden has 6 hour work days? That is not true. It has 8 hours, like most other countries.

Nah, It's Meta (source: https://en.wikipedia.org/wiki/Standard_ML).

SideNote: I have a friend though, who used it for almost 15 years and thought the M stood for Math before we spook about this.

Philae did send data for three days (unless i miss-remember). Knowing where that data was taken helps put it into context. So quite important for the mission.

Human language is basically a very lossy compression algorithm. It can never convey in full what your brain is experiencing

Why do you assume this was illegal in Sweden in the late nineties? In Sweden, downloading of IP was illegalized 2005-06-01. Before that it was only illegal to spread digital IP...

Surprise! Serverless runs on... gasp servers!

OCaml, like SML, have the syntax for defining their own operators. |> is defined, to my knowledge, both in the standard prelude and in core.

Does this in any way handle the 16KB limit on user-data on AWS? (i assume not)

Great job in any case!

To my knowledge, Erlang uses a cooperative scheduler. The process itself counts downs its reductions and yields when it is time. The programmer can call erlang:yield() to do this before time if he wants. Calling something like receive will also yield. I guess it comes down to definitions, but since Erlang is said to have only soft real-time (as opposed to hard real-time) properties, this makes more sense. The schedulers doesn't give any guarantees as to when a process gets to run and the scheduler never really preempts a process. Again, to my knowledge.

Great article though!