User:Prd: Difference between revisions

(71 intermediate revisions by the same user not shown)

Line 1:

~~Git:~~

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

<br>

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

=~~==== Studybuddy =====~~

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

*~~HTTP~~

----

*~~HTML~~

Figure it out mentality.

*CSS

*https://en.wikipedia.org/wiki/We_choose_to_go_to_the_Moon

:*LESS

*https://en.wikipedia.org/wiki/File:President_Kennedy%27s_Speech_at_Rice_University.ogv#file

:*Mustache

From signal to server, understand '''everything'''!

*JS

----

:*Node - ~~Relevant and flexible~~. ~~Hard not to base around this~~.

:Socials

:*Vue - Practical answer to clean interface.

::Discord - prd1847

:*Nuxt - Somewhat naturally coupled with Vue & Node. ~~Understandable and more approachable than Next & React~~.

::Prdandsuch on [https://www.reddit.com/user/prdandsuch/ Reddit]

:*Express - Decent option for managing server-side while the rest are dealing with the client-side. ~~Depends on tests~~.

::KenshiDBdotWiki@gmail.com

::*jQuery - Too prevalent not to be familiar with.

----

::*Leaflet - Foundation of the map but as per the coordinate transformation the library is mostly a guideline, not a rule.

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

*PHP- (We hate Laravel)

----

:*Parsoid

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

*Nginx - See maintenance & downtime plans.

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

:*SSL

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

*Kubernetes

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

:*Blue/~~Green~~

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

*MySQL

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

:*MariaDB

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

*Cargo

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

*MW-core

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

*Unix

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

*Bash

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

~~<br>~~

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

:No. I ~~will not be using Django (Python) or Rails (Ruby)~~. ~~Considering the ubiquitous presence of PHP~~ on ~~MediaWiki~~ and ~~the lack~~ of ~~integrating tooling for~~ the ~~aforementioned I~~'~~m left~~ with ~~too much added work to try and get those spun up~~. ~~Time~~ is ~~better spent developing skills~~ which ~~can directly translate~~ to ~~the wiki~~. ~~Besides~~, ~~a javascript heavy approach to~~ the ~~map gives me ample exposure~~ to the ~~other big player on the wiki (especially for gadgets)~~. ~~This is not about making '''the greatest map~~ to ~~ever exist built in~~ the ~~most ideal way'~~''. ~~Rather~~, it needs ~~to meet various functional uses and refine around those~~. ~~Obviously the existing map is a rudimentary mock-up and embodies only one test of one feature (coordinate conversion)~~.

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

@@ Line 1: / Line 1: @@
-Git:
+;<small>Holder of the skeleton key.</small>
-<br>
+;Upgraded to level <big>9</big>
-===== Studybuddy =====
+[https://www.youtube.com/watch?v=qf-_bRjZ38U The Decider]
-*HTTP
+----
-*HTML
+Figure it out mentality.
-*CSS
+*https://en.wikipedia.org/wiki/We_choose_to_go_to_the_Moon
-:*LESS
+*https://en.wikipedia.org/wiki/File:President_Kennedy%27s_Speech_at_Rice_University.ogv#file
-:*Mustache
+From signal to server, understand '''everything'''!
-*JS
+----
-:*Node - Relevant and flexible. Hard not to base around this.
+:Socials
-:*Vue - Practical answer to clean interface.
+::Discord - prd1847
-:*Nuxt - Somewhat naturally coupled with Vue & Node. Understandable and more approachable than Next & React.
+::Prdandsuch on [https://www.reddit.com/user/prdandsuch/ Reddit]
-:*Express - Decent option for managing server-side while the rest are dealing with the client-side. Depends on tests.
+::KenshiDBdotWiki@gmail.com
-::*jQuery - Too prevalent not to be familiar with.
+----
-::*Leaflet - Foundation of the map but as per the coordinate transformation the library is mostly a guideline, not a rule.
+:[[Project:Realpolitik|Realpolitik, World Revisions]]
-*PHP- (We hate Laravel)
+----
-:*Parsoid
+:https://www.mediawiki.org/wiki/Manual:Job_queue/For_developers
-*Nginx - See maintenance & downtime plans.
+:https://www.mediawiki.org/wiki/Manual:$wgJobTypeConf
-:*SSL
+:https://wikitech.wikimedia.org/wiki/MediaWiki_Engineering/Guides/Backend_performance_practices
-*Kubernetes
+:https://www.mediawiki.org/wiki/Database_transactions
-:*Blue/Green
+:https://www.mediawiki.org/wiki/Manual:Job_table
-*MySQL
+:https://www.mediawiki.org/wiki/Manual:Database_layout
-:*MariaDB
+:https://www.mediawiki.org/w/index.php?title=Manual:Database_layout/diagram&action=render
-*Cargo
+:https://www.mediawiki.org/wiki/Extension:EventLogging
-*MW-core
+:https://www.mediawiki.org/wiki/Extension:EventLogging/Guide
-*Unix
+:https://www.mediawiki.org/wiki/Extension:EventLogging/Programming
-*Bash
+:https://www.mediawiki.org/wiki/Architecture_guidelines
-<br>
+:https://wikitech.wikimedia.org/wiki/Performance/Metrics#Save_Timing
-:No. I will not be using Django (Python) or Rails (Ruby). Considering the ubiquitous presence of PHP on MediaWiki and the lack of integrating tooling for the aforementioned I'm left with too much added work to try and get those spun up. Time is better spent developing skills which can directly translate to the wiki. Besides, a javascript heavy approach to the map gives me ample exposure to the other big player on the wiki (especially for gadgets).  This is not about making '''the greatest map to ever exist built in the most ideal way'''. Rather, it needs to meet various functional uses and refine around those. Obviously the existing map is a rudimentary mock-up and embodies only one test of one feature (coordinate conversion).
+: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.