What's in a name ?

Just found that I have to rename "branch" to "build", on an issue page. That could prove interesting.

A good rename is a valuable refactoring: it allows one examine (in this example) how well I have distinguished and encapsulated the "branch" concept.

Further, it is one of those (beautiful) self-regarding enquiries - one can't really examine the naming of "branch" without there being a reasonable chance of the branch surviving, of finding a place where, ".. well actually that is a branch, not a build"