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: @@
-*''Preserved'' - content in a presentable and well-documented manner, made freely available for those who seek.
+;<small>Holder of the skeleton key.</small>
-*''Reserved'' - for all Kenshi players to explore, inquire, experiment and enjoy the big sandbox.
+;Upgraded to level <big>9</big>
-*''Deserved'' - to empower players so they may get the most out of this great niche game.
+[https://www.youtube.com/watch?v=qf-_bRjZ38U The Decider]
-<br>
+----
-*'''I will not be using the [https://www.mediawiki.org/wiki/Extension:Graph Graph] extension. It's a security threat and not necessary.'''
+Figure it out mentality.
-*:Context, the module was rendered unstable [https://www.mediawiki.org/wiki/Extension:Graph/Plans and will continue to] until its replacement arrives.
+*https://en.wikipedia.org/wiki/We_choose_to_go_to_the_Moon
-*:Alternatives exist, just annoying because the pie charts are cute :<
+*https://en.wikipedia.org/wiki/File:President_Kennedy%27s_Speech_at_Rice_University.ogv#file
-*A few thousand edits from starting skin development & shaping the foundational content structure.
+From signal to server, understand '''everything'''!
-*:Estimated changeover on 2/22.  The MW1.43 configuration and the vast majority of transclusions wrapped up making the site "ready" for content addition.
+----
+:Socials
-*Say [https://www.youtube.com/watch?v=Z0AIu63Nmj8 yes!]
+::Discord - prd1847
+::Prdandsuch on [https://www.reddit.com/user/prdandsuch/ Reddit]
+::KenshiDBdotWiki@gmail.com
+----
+:[[Project:Realpolitik|Realpolitik, World Revisions]]
+----
+:https://www.mediawiki.org/wiki/Manual:Job_queue/For_developers
+:https://www.mediawiki.org/wiki/Manual:$wgJobTypeConf
+:https://wikitech.wikimedia.org/wiki/MediaWiki_Engineering/Guides/Backend_performance_practices
+:https://www.mediawiki.org/wiki/Database_transactions
+:https://www.mediawiki.org/wiki/Manual:Job_table
+:https://www.mediawiki.org/wiki/Manual:Database_layout
+:https://www.mediawiki.org/w/index.php?title=Manual:Database_layout/diagram&action=render
+:https://www.mediawiki.org/wiki/Extension:EventLogging
+:https://www.mediawiki.org/wiki/Extension:EventLogging/Guide
+:https://www.mediawiki.org/wiki/Extension:EventLogging/Programming
+:https://www.mediawiki.org/wiki/Architecture_guidelines
+:https://wikitech.wikimedia.org/wiki/Performance/Metrics#Save_Timing
+:https://wikitech.wikimedia.org/wiki/MediaWiki_Engineering/Guides/Backend_performance_practices#Long-running_queries
+:https://wikitech.wikimedia.org/wiki/MediaWiki_Engineering/Guides/Frontend_performance_practices
+:https://wikitech.wikimedia.org/wiki/MediaWiki_at_WMF#Timeouts
+:https://wikitech.wikimedia.org/wiki/Infographics
+:https://wikitech.wikimedia.org/wiki/MediaWiki_Engineering/Guides/PHP_optimisation_tips
+:https://www.mediawiki.org/wiki/ResourceLoader/Architecture
+:https://www.mediawiki.org/wiki/ResourceLoader/Developing_with_ResourceLoader
+: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.