I agree with most of these but there’s another missing benefit. A lot of the time my colleagues will be iterating on a PR so commits of “fuck, that didn’t work, maybe this” are common.

I like meaningful commit messages. IMO “fixed the thing” is never good enough. I want to know your intent when I’m doing a blame in 18 months time. However, I don’t expect anyone’s in progress work to be good before it hits main. You don’t want those comments in the final merge, but a squash or rebase is an easy way to rectify that.

Yes.

I also do this.

It wasn’t fun however when one of the companies I transact with required me to answer one of the questions over the phone as a means of authentication.

I could tell the customer service guy was just as tired when I finally finished responding. :)

Just beware of their reclamation policy:

https://docs.oracle.com/en-us/iaas/Content/FreeTier/freetier_topic-Always_Free_Resources.htm#compute__idleinstances

The US seems to have this weird obsession with SMS and iMessage.

I’m curious as to thoughts regarding documenting intent which cross over with what in my opinion.

Regarding self documenting: I agree, but I also think that means potentially using 5 lines when 1 would do if it makes maintenance more straightforward. This crazy perl one liner makes perfect sense today but not in 3 years.

They also seem to mostly navigate on the same 2D plane of space, given the ships usually encounter each other the “right way up”.

Thanks for taking the time to respond.

I appreciate the info, but I am not a patient man. :)

Where on earth are you buying HP Mini machines for so cheap? Even the older gen seem to be 5 times as expensive as your estimate.