Continuing the discussion from Maledetta Sera? No! [Accidental Catharsis : Preemptive Grief] : [Reusability : Multiusability]: ← Example of Horizontal Layout of abstraction
In the technical sense (or perspective), I meant this as an example of the physical layout that I intended with this Tython Idea of using code as a pseudo-surrogate (add-on) for legislation.
I point out that a better layout (compared to what I originally posted) would be one in which the literal component (i.e. Legalese #bonusshow ) is on the left side whilst the pseudo-code component is right next to it, on the right. each portion separated either by colors or a subtle dashed line (- - - - taking into account color-blindness) or maybe both.
Now, it’s been two paragraphs and I still haven’t mentioned reusability nor multiusability:
-
Reusability: when using the same abstraction (sometimes with minor/aesthetical changes) within the same area: translation, in this case (for songs and reused for Legalese Vs pseudocode)
-
Multiusability: In a more far-fetched example that I would prefer (that one is saved FCEO) but staying on the lane of Tython*, the broader idea of laws being the code for humans (this is something that Cenk has alluded and that is one of the points made on Eric Liu’s analysis of power dynamics). This could be taken to an advantageous place, if well directed, we could:
- Lower/eliminate ambiguity via closure and opening symbols analog to those of programing
- Make sure that the result (return value) of law provision(s) do(es) not deviate from a baseline via annotations/strong_typing_of_return_values
- Use more abstractions like Decorators / Wrappers in a way that laws are better understood / applied
*I’m not married with the name, I use python terminoligy as default, but the abstractions i use as examples apply to a broader set of programming languages. I just replaced the first P with a T because it then forms tyt.
