I was late to sleep because of this, thanks! One suggestion, allowing swipe on touch devices would feel a lot more natural than tapping each square, which was a bit error prone. Either that or make the hitboxes a bit bigger.

Thank you for the feedback! The hitboxes are already quite big on mobile (only a 2px gap). I have implemented swiping though, let me know how it feels :)

Swiping makes this much easier to use and even more addictive. Nice work!

This does deserve more recognition but unfortunately we don’t talk about Bruno

Haha sick reference.

This is like the Rosetta Stone between zoomers and us millennials

Ah yes I’m sure those scientists in Denmark and the UK will try to maximise coverage of this due to an election in some other country. Grow up.

Those were originally part of the GaaP (Government as a Platform) programme. The PaaS is explicitly just the Cloud Foundry-based deployment platform.

Monzo engineer here. 99.99% of changes don't require key ceremonies. When they do, we can usually book them with a few days notice. It's normally for things like onboarding big new systems and gets planned into a project from the beginning.

The people who implemented this process are the same type of "IT/devs" or "Devops" you mention. There isn't a whole lot of throwing things over the wall to Ops, or for that matter putting up arduous processes against "normal" engineers.

I'd love for it to work over NFS. It should be easily doable, but I guess it means adding another dependency to the boot2docker ISO.

We're mostly looking at supporting remote volume sync in docker itself, with a pluggable transport - could be smb, nfs, periodic rsync, sftp... bradfitz started an awesome contribution with a full remote-fuse-protocol sync :) pretty awesome but we haven't been able to merge it yet because the volume system needs to be made sufficiently clean and modular first.

The advantage of doing it in Docker proper is that it works in all distros without outside dependencies, instead of just boot2docker.

Note: we are looking for help on this, if you feel willing and able. Even better if you can invest some recurring time to maintain and help others contribute.

We haven't yet had the pleasure.

No, 99% of our devs run Macbooks

waves. We don't change anything in the Dockerfiles, it's more that we use the dependency logic in Make to ensure that x is done before y and before z. We also use it to actually run a lot of our containers with the ability to switch in configs for production-like databases if the developer needs it.

Make was the perfect tool for the task at the beginning, but it's getting a little unwieldy and will probably need rewriting in something else soon, probably Python.