I wrote Multi Underscore Tag Naming Convention Analysis which describes the Ontology & structure of the naming convention.
TODO: I will latter post how & why the "Multi Underscore Tag Naming Convention" can assist in creating simpler software that scales with complexity. Also, I will explain how this naming convention makes it easy to find abstractions in a codebase with confidence, across any number of software & data layers.
I also have a previous post with a quick introduction to the Multi Underscore Tag Naming Convention .
I redesigned my site. This is my microblog, where I will be posting ideas, news, etc. It is archived. There is also a blog blog which contains longer articles. This site is also a proof-of-concept of a person-centric "social network" profile. While I'm working on making this process smooth for me, as a programmer, I would also like to extend this experience for non-programmers after the proof-of-concept is solidified. I believe there are certain workflows that are productive & encourage flow of expression for people with or without technical persuasion.
Here's the source code for this site.
I've been experimenting & making progress with Naming Conventions. Naming conventions for immutable entities has proven to reduce incidental complexity. I'm working on fleshing out the last details & a whitepaper. Please stay tuned. This practice has helped me remove incidental complexity from my codebases.
I'm also a fan of Svelte (v3) & Sapper. Svelte is provides truly reactive stores & html components. Html components mean it's easy for programmers & non-programmers (e.g. designers) to work with. Svelte is compiled, resulting in a payload that is small, fast, & memory efficient.
I've read through:
I encourage you to read these papers, as they explain the state of distributed networks & the innovations that Holochain & the Holo currency bring.