Unusable Chameleon

Amazing!!! the huge number of ways one can write the simplest of classes, and the huge number of 'seemingly' good ways that are in fact very limiting ...

basically, coding is choosing from the infinity of theoretical 'code solutions' one and materializing the chosen one into high level language text. imagine the sheer number of equally good or better solutions u have left out, how good solution is can be determined by current requirements but also depends n the future, so its an optimization problem, how far and how hard will u look into the future (which could also be a waste if done out of proprtions) to choose thet code u will materialize? how detailed will ur thinking be, to choose between the equally infinite amount of detailed ways to materialize the code which would make it best usable? u could even choose to code mulitple versions, (inline / not inline controlled by a #define per exmaple, with more or less control), if u do that how willu optimize the effort of trying to make those versions as similar as possible ( for obvious reasons) while as different as possible (fucntionality and usefullness wize) ... its all a nice huge optimization problem.