Someone may say that I am boring. I think it is difficult to find someone that likes to be boring. This is the reason why I put these code conventions and coding preferences as desirable and preferential things.
There may be someone that asks for another one that has gone to the school, that learning the format of the "a" letter, for example, would be unpleasant.
The conventions help the code readability.
The programming language poses its limits with the availability of its capabilities.
The conventions, specially the desired ones, helps reading, mantaining, reusing, rewriting code with much more ease, desirable characteristics in programming.
Nothing voids that you write a code of video decoding without obbeying any rule, but it will be used as it is, and little reused/rewritten it will be.
I sugggest that in codes that the desirable configurations cannot be applied, there be remarks like:

// a = bandwidth


Using the the applicable terminology, except that in view decoding presumably bandwidth is always called "a".

fluidbasis compatiblity verses:
The rules are mere rules. It works as source, mean and way to express Power and the rule forces and nature, as much as strong is the rule. If you love you can use rule to Love's favor. fluid-code, whose compliance ca2 API aims to adhere to, would install transparent code in every law and rule, as the own law and rule, or as source code based in other laws, or any other kind of building based in other laws... fluid-code is entirely Love by definition.