I’m curious why you think Python is unsuitable. Both of my kids picked up Python pretty easily.

Meh. I lose power every 3 or 4 years on average. A UPS just doesn’t make sense for me. (When I lived in Virginia it was once a month on average, so for sure it made sense…)

https://www.google.com/intl/en/ipv6/statistics.html

I suppose it is possible to have two PR that have changes that depend on each other. In general this just requires refactoring… typically making a third PR removing the circular dependency.

It sounds like your policy is to keep PR around a long time, maybe? Generally we try to have ours merged within a few days, before bitrot sets in.

You can make a PR against your feature branch and have that reviewed. Then the final PR against your man branch is indeed huge, but all the changes have already been reviewed, so it’s just LGTM and merge that bad boy!

How is this different from creating a feature branch and making your PR against them until everything is done, then merging that into the main branch?

I reboot every box monthly to flush out such issues. It’s not perfect, since it won’t catch things like circular dependencies or clusters failing to start if every member is down, but it gets lots of stuff.

Emacs was the first bloated IDE!

I was at a party explaining that we were finishing up a release trying to decide which bugs were critical to fix. The person that I was talking to was shocked that we would release software with known bugs.

When I explained that all software has bugs, known bugs, he didn’t believe me.

I didn’t know there was a -delete option to find! I’ve been piping to xargs -0 for decades!

The article only covers unsigned 32-bit numbers, so floating point division would be fine.