May 28, 2018

This entry is part [part not set] of 3 in the series Blurgs

Let’s define blurgs. A ‘blurg’ is an event where a programmer understanding of "what my code does" is not "what my code does". Blurgs are an everyday part of programming, of course. We are more often "interim" than at a sign-off point. But I mean to restrict for this conversation the idea of a blurg to being a programmer-program disconnect that occurs at a sign-off point. (a sign-off point is different for different teams. Most of the folks I work […]