H3S1: What is personal-dash?
Hu: A personal dash is the Walgreens-version of engagement with Chess University, your future home, for all your career needs. The personal-dashTM is the first physical product developed by our R&D-department, as well as the first product, at the $10.price-point.
H4S1: The rule of 8:<x-ref: WP.MIC-H2S11>
Hu: The reason that, throughout history, chess players have been the best programmers, is due to their intuitive understanding of the rule of 8:
MIC.43-Ex,16: Is 28…d4 a good move? A: Every pawn advance will clear 2 diagonals, as well as the rank that it precedingly # occupied, and in this case one of those diagonals a2 / f7 allows a value-adjusted assass of the s.f7-Q: Effect analysis of the b-p after 27…d5 ? The reason that 28. Qxf7 ! , played in the game <r: ch-35 ex-18, 19> is considered a value-adjusted assass is because the s.f7-Q is clearly far more valuable than its counterpart due to its 1) connection to the heavy battery along the f-file, while the f.a2-Q is hangtacked and 2) its involvement in the devastating attack being unleashed on the f-Kingside. Losing this queen is tantamount to losing the attack, which is the source of s’s -6.0 advantage <SF 14 d-22> in the initial b-p, and therefore allowing this exchange is tantamount to losing 6 p-score (!). 28…Rxf7 (+1) 29. Bxh5 (-2) ! dxe3 (+3) 30. Bxf7 (-2) Fin.
⭐ There is no limit to the amount of information, or complexity, that can be contained in a game of chess, or even a move, but this complexity, at no point, overloads our natural limits, because the board itself, is limited by the rule of 8. Analogously, human users will be overloaded, by UX–design, if there are more than 8 significant, interactive elements, on any one screen, or layer. Since iOS allows scrolling, even on the app.icon-screen, many people have upwards of 40 app icons on this layer, and are so overloaded, from this point, that they can hardly open their phone, without a significant | intentional blindness<MIC.ch-42>, that, practically, limits their view to maybe 3 apps, and so, they are less functional, than if 8. Since the intentional blindness occurred at a higher layer, the blindness will be propagated to lower layers, and even in Instagram, with its 3-wide grid, and the fact that only 3 things can be shown in the feed, and the profile has 3 elements, the mental-clog further limits, at every level of depth. See how WeChat circumvents this issue in<WP.MIC-H2S12>. H5S1: The rule of 8 in human facial geometry: Hu: The human face is the oldest | chess board, in that it is capable of a representation of infinite | depth, of emotion, and yet, is structured, to perceived in stepwise–eighths:
H5S1: A human face consists of 8 elementary | particles: 2 eyes, a nose, a mouth, 2 ears, cheeks, a chin, and a forehead. H5S2: A nose consists of 8 parts: 2 nostrils, a bridge, the connection to the mandible, the bulbous tip, the midline, the width, and the eye-bisection. Fin.v-1
H4S2: A breakthrough in personalization:
Hu: By combining our high.IQ-developers, architecture-obedience, and the simplicity of design # of personal-dash, we are able to bring you a level of personalization that has never been before offered, in any product, especially digital, in history. Your current-dash, your desktop | or mobile homescreen, has only personalization, on the first layer, of app-icons, whereas personal–dash has personalization at every, and any layer, to infinite–depth, like your own computer folder hierarchy, but for the entire–internet.
H4S3: Key principles:
H5S1: The protocol | layer: the personal–dash itself is only the protocol | layer<WP.MIC-H2S20>, meaning navigation, is super faster, and H5S2 Offloading.mental-capacity: much of your mental | capacity, in navigating between tasks, is occupied by the primary | flow of web services, which serves their business needs, but not you H5S3: Post–buy customer service<WP.MIC-H2S26>, permitting you to edit as you wish #, request changes #, and design self-help coaching sessions, around the design of your dash # H5S4: innovative | front–end | edit design<WP.MIC-H2S10>
H4S4: Access-managed:
Hu: Thanks to our innovative | implementation of WordPress.access-management<WP.MIC-H2S5>, only-you will have access to your own personal–dash. H5S1: In the future, we plan on # allowing you to share your dash, as well as access other users’ dash–templates.
H3S2: How to use personal-dash:
H4S1: Honing in:
Hu: Since personal-dash is built with the principle of stepwise–progression through layers.of-abstr, you can mass–reduce, subcon–load, by zooming in, even, to a particular 2nd layer. For example, say that my personal dash consists of 4,500 total unique | URLs; right now, I want to focus on my job-stuff, which contains 5 main URLs, and 10 subsequent # By zooming in to p.dash-2: job-stuff, and setting a hard | limit<WP.MIC-H2S15> on going back, keeping in mind that, already, personal-dash makes lateral | pivots between layer.2-menus already un-immediate<WP.MIC-H2S27>
H4S2: Paving the right neuronal-pathways:
Hu: The rigid | logical structure of personal | dash is, in its entirety, rooted in the correct | principles of hierarchical | categorization, using the unique system developed during our creation of Material in Chess ’22, which enabled its author #, to self-learn 700 pages of intense theory, from every field, in just 1 year. Repeating this feat, within your field, would enable you to make Nobel–tier contributions in your sleep, and your brain is already capable of it, if it had # the correct | scaffolding structure, which will be established, over time, and rapidly, by your use of personal–dash. H5S1: By accessing a link through the optimal | pathway, one is also undergoing a stepwise-retrieval of paradigms and priming filters<ch-42>, such that when the link is reached, one has the correct mental | paradigms pre-loaded to ensure optimal | productivity, with no distractions.
H4S3: Self-education of the principles of human.centered-product,design:
Hu: Personal-dash, in its skeleton–architecture, is the best human.centered-product,design of all time, and the first to be hard-coded. In your use of it #, to create your own personal–dash, fully customized, you will learn H5S1: How to QA, identify bugs, such as mis.mapped-URLs, the most basic–bug, and use our breakthrough front–end | page editor<WP.MIC-H2S10> to correct-them, H5S2: How to product–design, around specific user goals, such as your own productivity, and mental health, and track, whether your design, meets those goals, and iterate H5S3: //cont.v-2
H4S4: Eliminating tab-overload:
Hu: Tab–overload is a misapplied | attempt to offload | retrieval capacity, but what it actually does #, is clog retrieval capacity, due to search.retrieval–scarcity; because you are afraid that you’ll forget the path to that tab, and the URL it contains #, or worse, the task you were doing, in that tab #, you leave it open, but this makes your search.retrieval-scarcity worse<MIC>. H5S1: Personal-dash is not just a link | manager, but a task | manager, and it eases search.retrieval-scarcity by max-redding the tab.retrieval-pathway, allowing you to manually retrieve–tabs fast, which, in turn, allows you to close your tabs<Turing, a problem since 2007>
H4S5: Personal-dash is for PC-only:
Hu: Personal dash is tested and approved for all PC.screen-sizes, including iMac, and Macbooks<untested>, but not for any devices that are considered mobile, on any platform, due to protocol–limitations.
H4S6: Saving personal-dash to your desktop #
Hu: The critical | installation step of personal–dash, the most concise | software of all time<prev-Davis, TempleOS-2005>, is to download the homepage, to your desktop. You can accomplish this # by clicking the hamburger | menu on your browser: if you are using a different | browser, search for the analogous | pathway #
