Unfortunately, there is some urgency to this effort. As Shashi Tharoor writes in his book Inglorious Empire (2018), over the past 30 years, there has been a tremendous bout of collective amnesia, espeically in the UK, about the history of empire and its consequences. Into this vacuum, revisionist historians of the worst kind like Niall Ferguson have capitalized on historical blind spots of people living today to make an absurd case for the benefits of empire. This cannot be allowed to happen. Tharoor believes that one of the best bulwarks against this erasure is to do the work of inquiry and to make the history of empire accessible and apparent to the widest audience. It is into this effort that I submit my work. John Company is an unsparing portrait that hopefully will give its players a sense of the nature of empire and the long half-life of its cultural production. It is certainly not the only way to make a game about empire, but I hope that it does its part in adding to our understanding of that subject and its continued legacy.

As a result of all this in a couple of weeks I had a working version of empty (http://www.sourceforge.net/projects/empty) which allows to start interactive programs and communicate with them using FIFO-files

Around &Bigger the box is bigger: 75mm high instead of 45mm or so.That was the main reason for the name &Bigger. The first edition does fit in its box but very tight. Because the first factory used bigger cardboard than planned. They told me about this "upgrade" after they produced the game. The thicker tiles (about 2.5mm) did feel good for the game so the &Bigger edition has the same

Enter 2020: Matt and Jordan managed to scrape together some illustrations for playtesting, but they weren’t up to the bar of a production game. Fortunately, we connected through friends with Jaehee, and she cautiously listened to the pitch for the game. Once she decided to join the team, the artwork and designs quality improved by orders of magnitude, to the point where we had an experience we felt was worthwhile sharing publicly.

Originally he had used the terms usage scenarios and usage case – the latter a direct translation of his Swedish term användningsfall – but found that neither of these terms sounded natural in English, and eventually he settled on use case.

I have proposed a new word for this quality: onceability.

One day last August 2018, I stumbled upon an online petition that sparked my curiosity - We Want Serverless Ruby. At that time, none of the major cloud providers had first-class support for Ruby in their serverless products. There were ~1400 devs signing that petition, and I wondered if there was something about Ruby that made it unsuitable for FaaS. I decided to roll the sleeves and start building what would be the first PoC of faastRuby.

Good intentions, but I doubt there's any relation of the origin of the terms blacklist/whitelist to race. There are many idioms and phrases in the English language that make use of colours without any racial backstories. I haven't met any black person (myself included) who was ever offended by the use of "blacklist".

Railway Oriented Programming comes from functional programming, so it is tightly related to the usual FP concepts like monads, composition, and many others.

I started this project in order to Materialize Tunnelgram.

I came upon a great idea that would put an end to these ceaseless interrogations by my comrade. 'We are five or six friends', I told him some time later, 'who are in charge of the same mathematics curriculum at various universities. Let us all come together and regulate these matters once and for all, and after this, I shall be delivered of these questions.' I was unaware of the fact that Bourbaki was born at that instant.

Seneca Creation Story

The First Book of Moses, Called Genesis

As soon as computer data entry moved from punch-cards to online files (in the mid/late 1960s) there were "commands" for accomplishing this operation.