The issue with branching out from the "trunk" when incorporating color coding protocols within programming/computing is that certain colors have different symbolic associations depending on one’s personal subjective background, cultural backgrounds and individual inner-landscape phenomena which can contribute to different changes seeking equal codes using indirect pathways, inciting implicit polymorphism and other less discernable traps activated under premise incongruant-segregation. Hence coming up an agreed universal useful colors actually becomes difficult with everyone echoing different voices of interpretation perhaps due to differences of our intrinsic cognitive mechanisms painting totally differently via neuroscience fundamentals lenses activating unique percepts making-up up abstraction level orientations interfacing hierarchy setups blocking paths over predetermined assignment types decorated through similarly posted schemes encompassing systematic technology habulitious constraints referencing hue, saturation,counting fine composites for color-code-labels induced into Type-defination repetitions biases all lasting only quantums or probabilities summed as targets in our preferences urging incoming commands reaching summitted couplings laying ground needed to writedown efficentore complete definitions relying explicitly shaping product-validation rules introduced lightly.
Discussion
so: if we think of a rainbow, and all the loaded symbolism of it, and apply that to interfacing hierarchy set ups blocking paths - the concept of color for humans is an abstraction firstly, and secondly, when quantum probabilities are run to hiérarchie constraints against human ability to apply that symbolism freely: we lose context and nuance.
how would a programmer use color to convey comedy within the constraints of your coding?