User:Prd: Difference between revisions

(16 intermediate revisions by the same user not shown)

Line 1:

;<small>Holder of the skeleton key.</small>

;Upgraded to level <~~small~~>8</~~small~~>

;Upgraded to level <big>9</big>

[https://www.youtube.com/watch?v=qf-_bRjZ38U The Decider]

----

Line 13:

::KenshiDBdotWiki@gmail.com

----

[~~https~~:~~//www.youtube.com/watch?v=kbCIsCgrD-E Right on time.~~]

:[[Project:Realpolitik|Realpolitik, World Revisions]]

~~[https://www.youtube.com/watch?v=V1nGjPTcSIk Woohoo!~~]

----

~~;Understand(ing mission critical systems, why they must not fail and why mission creep invalidates intentional design, i~~.e. ~~process failure)~~

:https://www.mediawiki.org/wiki/Manual:Job_queue/For_developers

:https://~~forums~~.~~debian~~.~~net~~/~~viewtopic~~.php?t=~~120652~~

:https://www.mediawiki.org/wiki/Manual:$wgJobTypeConf

~~;Merely because something has been embraced does not mean it qualifies as anything other than a stopgap to an unsolved problem~~. ~~If the levies are built to break then you have all the evidence you need once the flood waters clear and beg the questions "how" and "why"? Because, you trusted someone who never deserved it~~. ~~Perhaps you were desparate~~. ~~Maybe the path of least resistance is the most sensible~~. ~~Which is why we have resistors (read as process controls and guardrails)~~. ~~Stop allowing the flow to dictate the direction - it does not and never has cared which path it follows~~. ~~Systemd is proof that incompetency is the norm in software engineering and its creator should be ashamed~~. ~~No apologies for wanton neglect~~.

:https://wikitech.wikimedia.org/wiki/MediaWiki_Engineering/Guides/Backend_performance_practices

:https://www.mediawiki.org/wiki/Database_transactions

:~~Scalar severity~~

:https://www.mediawiki.org/wiki/Manual:Job_table

#~~Non~~-~~Critical Applications~~

:https://www.mediawiki.org/wiki/Manual:Database_layout

#~~Short Product Life Expectancy~~ / ~~Non-Critical Applications~~

:https://www.mediawiki.org/w/index.php?title=Manual:Database_layout/diagram&action=render

~~#Product Accessible to Field Repair~~

:https://www.mediawiki.org/wiki/Extension:EventLogging

~~#Application Critical~~

:https://www.mediawiki.org/wiki/Extension:EventLogging/Guide

~~#Refurbished or Reclaimed Parts~~

:https://www.mediawiki.org/wiki/Extension:EventLogging/Programming

#~~Reporting Source Alert~~ on ~~Items~~

:https://www.mediawiki.org/wiki/Architecture_guidelines

#~~Field Work or Repair Impossibility (i.e.~~, ~~Satellites~~, etc.)

:https://wikitech.wikimedia.org/wiki/Performance/Metrics#Save_Timing

#~~Mission Critical~~

:https://wikitech.wikimedia.org/wiki/MediaWiki_Engineering/Guides/Backend_performance_practices#Long-running_queries

#~~Safety Critical~~

:https://wikitech.wikimedia.org/wiki/MediaWiki_Engineering/Guides/Frontend_performance_practices

#~~Life Dependent Applications~~

: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.

@@ Line 1: / Line 1: @@
 ;<small>Holder of the skeleton key.</small>
-;Upgraded to level <small>8</small>
+;Upgraded to level <big>9</big>
 [https://www.youtube.com/watch?v=qf-_bRjZ38U The Decider]
 ----
@@ Line 13: / Line 13: @@
 ::KenshiDBdotWiki@gmail.com
 ----
-[https://www.youtube.com/watch?v=kbCIsCgrD-E Right on time.]
+:[[Project:Realpolitik|Realpolitik, World Revisions]]
-[https://www.youtube.com/watch?v=V1nGjPTcSIk Woohoo!]
 ----
-;Understand(ing mission critical systems, why they must not fail and why mission creep invalidates intentional design, i.e. process failure)
+:https://www.mediawiki.org/wiki/Manual:Job_queue/For_developers
-:https://forums.debian.net/viewtopic.php?t=120652
+:https://www.mediawiki.org/wiki/Manual:$wgJobTypeConf
-;Merely because something has been embraced does not mean it qualifies as anything other than a stopgap to an unsolved problem. If the levies are built to break then you have all the evidence you need once the flood waters clear and beg the questions "how" and "why"? Because, you trusted someone who never deserved it. Perhaps you were desparate. Maybe the path of least resistance is the most sensible. Which is why we have resistors (read as process controls and guardrails). Stop allowing the flow to dictate the direction - it does not and never has cared which path it follows. Systemd is proof that incompetency is the norm in software engineering and its creator should be ashamed. No apologies for wanton neglect.
+:https://wikitech.wikimedia.org/wiki/MediaWiki_Engineering/Guides/Backend_performance_practices
+:https://www.mediawiki.org/wiki/Database_transactions
-:Scalar severity
+:https://www.mediawiki.org/wiki/Manual:Job_table
-#Non-Critical Applications
+:https://www.mediawiki.org/wiki/Manual:Database_layout
-#Short Product Life Expectancy / Non-Critical Applications
+:https://www.mediawiki.org/w/index.php?title=Manual:Database_layout/diagram&action=render
-#Product Accessible to Field Repair
+:https://www.mediawiki.org/wiki/Extension:EventLogging
-#Application Critical
+:https://www.mediawiki.org/wiki/Extension:EventLogging/Guide
-#Refurbished or Reclaimed Parts
+:https://www.mediawiki.org/wiki/Extension:EventLogging/Programming
-#Reporting Source Alert on Items
+:https://www.mediawiki.org/wiki/Architecture_guidelines
-#Field Work or Repair Impossibility (i.e., Satellites, etc.)
+:https://wikitech.wikimedia.org/wiki/Performance/Metrics#Save_Timing
-#Mission Critical
+:https://wikitech.wikimedia.org/wiki/MediaWiki_Engineering/Guides/Backend_performance_practices#Long-running_queries
-#Safety Critical
+:https://wikitech.wikimedia.org/wiki/MediaWiki_Engineering/Guides/Frontend_performance_practices
-#Life Dependent Applications
+: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.