Hu: Implications of the public.dash-paradigm have on my URL design<WP.MIC-H2S41> and access.manage-considerations<WP.MIC-H2S5>, so I need to determine # the direction of scaling before setting upon the course, completely, in what I build, right now.
H3S1: Designing a sample public-dash on wordpress.MIC:
Make category pages and display this as the blog home page, click into each one, only posts from that cat, reverse chron. Cats include: 1) WAMP programming tutorials 2) WordPress plugin build: p-dash, including all from 1) 3) Business logic x programming 4) Non.coding-WP,Tuts 5) Advanced.comp-sci,research<URL.setting-transfer, ghost.variable-management><make this one specific, linking to specific headers, investigate WP in-page links, r: H2S41-H3S5[meta!]> these will be my categories in WP also. Should be a straightforward tut search, w/ some p-dash design mindset, break into further 9s whenever necessary, think about expansion of application #, and I can create outlinks also. Yep just p-dash it, decision is whether manual, or full.plugin–implementation, see how much it increases usability, think Noder’s easy site, and link it; this is the dashboard for all WordPress possible usages and applications, I can even link it from my own p-dash, final solution. This will be the first example of a public dash. Becomes a social network. I can generate pages and also hard-code them in the initial phases. Write about dash-compatibility later.
H3S2: Meta-structure as pedagogy:
Transmitting the meta structure of knowledge is 50% of pedagogy, and personal-dash enforces the rule of 8 from chess, in order to provide the fundamental universal neurological structure for the presentation of the structure of knowledge.
H3S3: Data per page vs pages-allowed tradeoff:
Block icons for now, and instead allow users to color code a default icon, all icons will have colors, as well as up to a 4 char preview that can be set. V3: auto generate the preview using my notation system for English word starts, from Anki.and-write.
Personal and public-dash will also be the most data concise application of all time, and blocking images to start, will allow the creation of thousands to millions more dash pages.
H3S4: Considerations of URL.layer-design, in preparing for a public-market #
The URL layer is as mature as PHP, so I can spend as much time building this as I do the PHP layer.
Having an author tag in the dash will allow public authors, especially, to organize their directories, and more easily link to users.
H3S5: Considerations of access-management:
Access management immediately comes to the forefront if public dashes are introduced, because only that logged.in-author # should be able to see the edit features.
Question is: how do I get the name token of the person who is responsible for the current logged in session and check that against my smart post ID?
H3S6: P-dash demonstrates the superior scalability of selective search:
We have now cleared WordPress at move 4. There’s not going to be a loss of trajectory, which validates my scalable method. Personal-dash is the first selective search web company since the design of programming languages themselves.
Reference Ch-16 and paste a block quote about Berliner vs Botvinnik with a bit of analysis.
The brute force paradigm is an entire metaphysical philosophy of the universe that the current generation of web developers trap themselves in by not analyzing the outcome of Kasparov vs Deep Blue.
Reference Ch-9, where I talk that ^
There’s not a single event that explains this whole host of phenomena except that. It was a watershed moment in history, but that watershed moment was veiled by a complexity barrier, and yet it’s still have the same effect over time, analogous to Kelempelen
Add some research about the expanded variation capacity as a function of depth using selective search vs brute force, an example where the value actually determines the unit
⭐️ All reductions are logarithmic functions because they reduce a function that skills in complexity exponentially into a linear function. X.ref-MIC,directive.fbno