That's what the diff tool is for.

I am so confused by this whole interaction.

Zalando explicitly forbids it in their RESTful API Guidelines, and I would say their argument is a very good one.

Basically, if you want to provide more fine-grained semantics, use dedicated types for that purpose, rather than hoping every API consumer is going to faithfully adhere to the subtle distinctions you've created.

Databases aren't related to VMs or containers.

https://en.m.wikipedia.org/wiki/Database does a good job of describing what a database is. That page also has a lot of examples of uses of databases.

To answer your question about MySQL: in my experience it's rarely used outside of classrooms or archaic systems. Postgres is a much better general-purpose option for SQL. Sqlite is also nice for different use cases (such as a database on a mobile device).

Briefly glancing through your code there's a typo on line 37:

outlives_parsed = parse_trail_outlives(bouds.fetch('outlives', nil))

Of course this wouldn't be an issue had you actually implemented it in Rust since such a thing wouldn't compile. Not really a good reason to be using ruby for this.

Could you not have a hashmap keyed on matches pointing to vectors of strings for the players in each match? Basically modeling the data how you want rather than relying on indexing.

I don't use teams, but hard disagree. My team screenshares all the time for pair programming, and even for regular meetings, screen sharing a slide deck or basic agenda is helpful for focusing conversation. I have presented before without sharing a screen and things go off the rails really quick. Focusing attention on the topics being discussed helps keep things as brief and efficient as possible. Presenting an agenda and topics also shows professionalism and that you are trying to respect people's time by keeping things focused.

If it's an actually useless meeting... Just don't go? It's not that hard.

I know how to use git. It's not that hard.

This true, though Republicans have gerrymandered the districts so bad that it almost always ends up as all Republican anyway. Look at how crazy this looks: https://en.m.wikipedia.org/wiki/Nebraska%27s_congressional_districts#/media/File%3ANebraska_Congressional_Districts%2C_118th_Congress.tif.

For some fucking reason, Lincoln (a liberal city that's the second largest in Nebraska) is in the same district as a bunch of rural towns that I would have to drive for hours to get to. Sarpy county, which most consider to be a part of Omaha (and again, is about an hour-ish drive from Lincoln, was recently switched to our district because they are largely conservative, and they redrew it just before we were supposed to be electing our new congressperson (which, by the way, was a special election because the previous Republican congressman was convicted of felonies relating to lying about foreign campaign contributions, go figure). A democrat swept Lincoln, but lost because they piled on enough rural counties in the fucked up map. Republicans have no respect for democracy.

It's because they want to incentivize long-term, stable relationships and households because doing so statistically leads to better outcomes for society. The barrier to entry for getting divorced is quite high, so in general people tend to stay together more often if they are married than if they are not.

That all being said, the system is far from perfect for sure. Incentivizing marriages also incentivizes people to stay in bad marriages, among other issues

(It's definitely not.)

JavaScript promises are not monads: https://stackoverflow.com/questions/45712106/why-are-promises-monads

They're close, but not quite. then can shift semantics from under you depending on what's supplied.

It should also be added that monoids require the type to have an identity or "empty" value (which is the empty array for arrays).

The explanation is pretty off in general, since it implies that any type that's both a functor and a monoid is a monad, which is simply not true. A good example is a ZipList (like lists, but with an applicative instance based on zipping). It's a functor and a monoid, but definitely not a monad.