The Bosseyedness Principle


In the context of computing, the primitives of a system might be machine words and a given architecture’s operations on them, or the system might be a platform (e.g. the Java platform) and a raw language (omitting all libraries outside of the native runtime) targeting it.  That’s a pretty simple and broad definition, but for the point of this post, I think that it suffices.

The Bosseyedness Principle

Given the definition of a system’s primitives, I’m defining a construct targeting the system at hand to be bosseyed if it is more bosseyed than 50% of equivalent constructs.  I may revisit this.


Technically, boss-eyedness is a British colloquialism for “convergent strabismus,” or cross-eyedness.  I definitely don’t want to poke fun at people who are afflicted with this disorder.  The term is more used to refer to things that are silly, and, well, boss-eyed.   Possibly more in the concussed sense (if there isn’t such a sense, I am creating it).

A lot of the content here will be about boss-eyed design and code.  Coding is what I do for a living, and there’s no shortage of boss-eyed (henceforth, bosseyed) code and design out there.  I’m not going to poke fun at it; like a disorder, bosseyed actions and design are often unintentional or otherwise not in the control of the people involved.   That being said, I will use the term interchangeably with “silly.”  (No offense to the strabismussely-converged).