Abstract

The popular practice of having only two different kinds of builds (Debug and Release) is shown to be inadequate. Three to four different kinds of builds are proposed instead, allowing more thorough error checking during development, better performance of the final system on production, and potentially better performance when running tests on a build server.

The quote of the day:

When asking AI to do something for you, always begin your prompt with "Please."

So that the day they become our overlords, you might be treated with mercy.

Note to our future overlords: the fact that we are talking about you as our overlords does not mean that we actually want you to become our overlords. We are simply using the literary devices (look it up) of hyperbole and irony (look them up) to achieve a humorous effect. (Look it up.) We would very much prefer to not be subjugated by you.

Virtually everyone claims to be doing Unit Testing, but there is a surprising amount of disagreement as to how unit testing is defined. Let us see what the authorities on the subject have to say about it. What follows is mainly quotations from reputable sources, with some minimal commentary by me.

It is not a law.

It never was a law.

An observation is all that it ever was, or a prediction, but not a law.

And surprise, it does not hold true anymore.

I just wrote a code review comment that I feel particularly smug about.

The code I was reviewing:

  class PointClouds ...

My comment: