gregorymfoster

I’m working on https://screenplay.dev, where test every change against a battery of open source iOS apps (Wikipedia, signal, etc). We started on GitHub actions, but found it much cheaper to buys ~4 Mac mini’s and run them in the office. It takes a little love to keep them up to date and stable (maybe an hour a week), but in return we get cheap, debuggable Mac computer. I like that more offerings are appearing, but at this price, we’ll stick to our furnace of Mac mini’s for now.

I've played a few sessions on this platform, including a session across the country with my sister for her birthday. Big fan - if you find a solid DM, this can make quarantine a lot more fun.

Are you assuming men can’t wear earrings?

Incidents _requiring_ rolling forward are extremely rare. In the cases you have to, just build the image and deploy to your cluster with a high max-surge configured.

If you image has correct caching, rebuilding it shouldn't take much time. Most of your time is likely spent in CI and rolling deployments, both of which you can manually skip.

At Airbnb, we built an internal tool called Deployboard which made it easy for engineers to promote deployments across environments. Then we transitioned over to Spinnaker in order to codify deployment processes and help automate the analysis of canary metrics.

Being able to hold up my watch and say “set a timer for 30 minutes” is significantly better than fumbling through menus.

Thanks!

Co-author here :) In response to dead-reckoning: https://medium.com/@gregorymfoster/how-any-app-could-track-t...

I agree completely with your thoughts on this. So many times things start out as a small rebellion against a norm, become cool, and then eventually become the standard.