I was at a small roleplaying convention last week. It was great to meet the others again after about a year and game with them. Unfortunately someone was rather generous with their flu viruses and I got my personal helping. So I’m on sick leave for the second say but luckily, according to the test it’s just a flu and not the big bad C. On Monday I clobbered together a small template for my sister to build fake computer screens as props for TV shows… All in all a mixed bag of some good stuff and some annoying things…

The “gut” might not be an organ but I can’t see a microbe letting go of some tasty piece of food just because it happens to pass from the small incestine to the colon… (wrong terms can safely be attributed to my translation tool)…

Several times, sometimes to find out when an incompatibility was introduced in an upstream dependency to find the maximum compatible version, but usually to find the commit that introduced a strange bug.

The process is always the same… Write a unit test, start bisect, check test select next bisect step, repeat. If your last-known-good and first-known-bad are correct, it always worked for me.

I’ve seen the fun of “prints everywhere” in production when a colleague forgot to remove a “Why the fuck do you end up here?” followed by a bunch of variables before committing a hot-fix… Customers weren’t to amused…

Edit: That was a PHP driven web shop and the message ended up on to of the checkout page