Difference between revisions of "Talk:Time Management with timeline"
Jump to navigation
Jump to search
Line 2: | Line 2: | ||
The whole point of using PKC is to leverage its powers in managing Namespaces. And you guys ([[User:KevinTung|Kevin]] & [[User:Baliforester|Jared]]) have been selfishly define namespaces in ways that are most convenient in your own private contexts, without thinking about Namespaces must be put in a "Single Source of Shared Truth", such as a single wiki or Git repository, to ensure the consistency and re-usability of the chosen names. This mental laziness causes systematic misunderstanding, and most seriously, delayed the possibility to make progress in a reasonable speed. Moreover, the explicit statement that all of your actions must be put into a [[Logic Model]], which you both conveniently ignored, repeatedly caused our communication to go into directions that goes no where. This is really a sad condition that is now being documented here. One more time, all pages are specialization of the [[Logic Model]], and this page included, must have a [[Logic Model]]. --[[User:Benkoo|Benkoo]] ([[User talk:Benkoo|talk]]) 09:32, 15 July 2021 (UTC) | The whole point of using PKC is to leverage its powers in managing Namespaces. And you guys ([[User:KevinTung|Kevin]] & [[User:Baliforester|Jared]]) have been selfishly define namespaces in ways that are most convenient in your own private contexts, without thinking about Namespaces must be put in a "Single Source of Shared Truth", such as a single wiki or Git repository, to ensure the consistency and re-usability of the chosen names. This mental laziness causes systematic misunderstanding, and most seriously, delayed the possibility to make progress in a reasonable speed. Moreover, the explicit statement that all of your actions must be put into a [[Logic Model]], which you both conveniently ignored, repeatedly caused our communication to go into directions that goes no where. This is really a sad condition that is now being documented here. One more time, all pages are specialization of the [[Logic Model]], and this page included, must have a [[Logic Model]]. --[[User:Benkoo|Benkoo]] ([[User talk:Benkoo|talk]]) 09:32, 15 July 2021 (UTC) | ||
{{Logic Model | {{Template:Logic Model | ||
context=The lack of named spatial/temporal contexts will cause confusion in the process of communication | context=The lack of named spatial/temporal contexts will cause confusion in the process of communication | ||
goal=Use [[Logic Model]] to capture [[context]], [[goal]], [[success criteria]] in Wiki. | goal=Use [[Logic Model]] to capture [[context]], [[goal]], [[success criteria]] in Wiki. |
Revision as of 09:44, 15 July 2021
Process Anti-Pattern Observation
The whole point of using PKC is to leverage its powers in managing Namespaces. And you guys (Kevin & Jared) have been selfishly define namespaces in ways that are most convenient in your own private contexts, without thinking about Namespaces must be put in a "Single Source of Shared Truth", such as a single wiki or Git repository, to ensure the consistency and re-usability of the chosen names. This mental laziness causes systematic misunderstanding, and most seriously, delayed the possibility to make progress in a reasonable speed. Moreover, the explicit statement that all of your actions must be put into a Logic Model, which you both conveniently ignored, repeatedly caused our communication to go into directions that goes no where. This is really a sad condition that is now being documented here. One more time, all pages are specialization of the Logic Model, and this page included, must have a Logic Model. --Benkoo (talk) 09:32, 15 July 2021 (UTC)
{{Template:Logic Model context=The lack of named spatial/temporal contexts will cause confusion in the process of communication goal=Use Logic Model to capture context, goal, success criteria in Wiki. criteria=Seeing Logic Model as a formal data structure to be included in pages that describes named entities. outputs=A Logic Model written by each page's verifier in PKC. process=A compositional process to relate Inputs with Outputs. inputs=#PKC access # Content Creator #Page Verification Process boundaries= The intersection of arrogance and stupidity. }}