User:Prd: Difference between revisions

Never expect others to help you. You are completely on your own from idea creation to execution and implementation.
This includes anything from both discovery of & grasping concepts, software/package intricacies, concurrency conflicts up and down the stack, race conditions, debugging scenarios, error tracking etc. It is entirely upon you to solve your problems - and sometimes other people's problems become your own to solve. Deal with it.
There is no wisdom in the notion "don't reinvent the wheel" when spoken with respect to systems architecture which is akin to a pile of dirt. These are not wheels, they are at best the tread to the tire and little more. Reinvent to fix the undeniably bad. Don't stick with incompetency merely because it's popular.
Problems are global, solutions are local.
No feature outweighs its performance needs. "Working" isn't good enough.

@@ Line 1: / Line 1: @@
-Made some mistakes.
+;<small>Holder of the skeleton key.</small>
+;Upgraded to level <big>9</big>
-Made a wiki!
+[https://www.youtube.com/watch?v=qf-_bRjZ38U The Decider]
+----
-Made some more mistakes.
+Figure it out mentality.
+*https://en.wikipedia.org/wiki/We_choose_to_go_to_the_Moon
-*1/31: Website creation.
+*https://en.wikipedia.org/wiki/File:President_Kennedy%27s_Speech_at_Rice_University.ogv#file
+From signal to server, understand '''everything'''!
-*2/1: Initial networking hurdles (resolved as of 2/2), creation of map.kenshi.wiki
+----
+:Socials
-*2/2: Early development of map.kenshi.wiki.
+::Discord - prd1847
-*2/3-2/8: Migration to 1.43. E-mail server live. Evaluation of available extensions.
+::Prdandsuch on [https://www.reddit.com/user/prdandsuch/ Reddit]
-*2/9: Finalization of extensions for review. Initial Cargo testing.
+::KenshiDBdotWiki@gmail.com
-*2/10-2/11: Configuration marathon
+----
-*2/12: Successful testing of '''all''' planned features.
+:[[Project:Realpolitik|Realpolitik, World Revisions]]
-:*With the proven testing of Cargo & TemplateStyles the wiki is technically feature-ready.
+----
-:*UX development will continue for the duration of Feburary.
+:https://www.mediawiki.org/wiki/Manual:Job_queue/For_developers
-:*Ongoing:
+:https://www.mediawiki.org/wiki/Manual:$wgJobTypeConf
-::*Skin creation, implementation of Tailwind (or some other desirable CSS library).
+:https://wikitech.wikimedia.org/wiki/MediaWiki_Engineering/Guides/Backend_performance_practices
-::*Customized navigation scheme (MediaWiki's options are insufficient.)
+:https://www.mediawiki.org/wiki/Database_transactions
-::*Preliminary map modelling. (There are numerous ways to achieve the desired outcome. Performance optimization is first order.)
+:https://www.mediawiki.org/wiki/Manual:Job_table
-*2/13: Reworking Module & Template network for active use, i.e. broken link cleanup & redirect implementation.
+:https://www.mediawiki.org/wiki/Manual:Database_layout
-:*Resounding success. Lua errors are a thing of the past.
+:https://www.mediawiki.org/w/index.php?title=Manual:Database_layout/diagram&action=render
-:*Modules capacity goes well beyond what some wikifarms offer and is nearing Mediawiki parity.
+:https://www.mediawiki.org/wiki/Extension:EventLogging
-::*Note:Sometimes even beyond MediaWiki itself. Modules are not inherent to MediaWIki - they can be developed independently. See: [[Module:Protection banner]]
+:https://www.mediawiki.org/wiki/Extension:EventLogging/Guide
-*2/14:Completion of Module & Template network. Reorganization & adaption to site-native category structure.
+:https://www.mediawiki.org/wiki/Extension:EventLogging/Programming
-:*Some extensions are so powerful and potentially unwieldy that they might warrant restraining. DPL3 is great, too great.
+:https://www.mediawiki.org/wiki/Architecture_guidelines
-:*NOTE: <s>Setup Wikibase later today</s>. The more intricate templates want it to exist, see:
+:https://wikitech.wikimedia.org/wiki/Performance/Metrics#Save_Timing
-::*[[Module:Wikidata label]] & [[Template:Label]].
+:https://wikitech.wikimedia.org/wiki/MediaWiki_Engineering/Guides/Backend_performance_practices#Long-running_queries
-::*:NOTE2: The global language set is too much for the Lua calls. However, I believe within a certain range translations can be enabled. Nevertheless, it's better to implement the underlying templates & transclusions built around them. Not doing so ''may'' lead to unexpected cross-template parsing errors, see: [[Template:Tlg]]
+:https://wikitech.wikimedia.org/wiki/MediaWiki_Engineering/Guides/Frontend_performance_practices
-*Final decision: No Wikibase. There's no serious need to impose an unwiedly extra database upon the server. The small amount of modules missed out on are not worth the hassle or functionality to activate the modest feature additions.
+:https://wikitech.wikimedia.org/wiki/MediaWiki_at_WMF#Timeouts
-*2/15-2/16:Module testing & determinations on inclusions. Working through resultant transclusion chains.
+:https://wikitech.wikimedia.org/wiki/Infographics
-*2/17:Plans to circumvent the ''mw.wikidata'' table calls are underway. Seems quite possible.
+:https://wikitech.wikimedia.org/wiki/MediaWiki_Engineering/Guides/PHP_optimisation_tips
-:*Final round of extension addition, removal and review. Confirming configurations & ensuring expected operation (of yet unknowns).
+:https://www.mediawiki.org/wiki/ResourceLoader/Architecture
-:*It's looking like at most around 30 modules or so remain for vetting. Then backworking all that to isolate for Wikidata calls.
+:https://www.mediawiki.org/wiki/ResourceLoader/Developing_with_ResourceLoader
-::*Ahead of schedule.
+:https://wikitech.wikimedia.org/wiki/MediaWiki_Engineering/Guides/Measure_frontend_performance
+----
+;Lessons I've learned
+:# Never expect others to help you. You are completely on your own from idea creation to execution and implementation.
+:# This includes anything from both discovery of & grasping concepts, software/package intricacies, concurrency conflicts up and down the stack, race conditions, debugging scenarios, error tracking etc. It is entirely upon you to solve your problems - and sometimes other people's problems become your own to solve. Deal with it.
+:# There is no wisdom in the notion "don't reinvent the wheel" when spoken with respect to systems architecture which is akin to a pile of dirt. These are not wheels, they are at best the tread to the tire and little more. Reinvent to fix the undeniably bad. Don't stick with incompetency merely because it's popular.
+:# Problems are global, solutions are local.
+:#  No feature outweighs its performance needs. "Working" isn't good enough.