Create a tips, tools and tactics guide for coders

[NateWr]

This guide could provide a bunch of different advice/tools for working with the code. Some ideas:

• eval(\Psy\sh())
• throwing exceptions
• Vue.js dev tools
• Quick video: using blame on github to identify why something was done a certain way
  • Example: variable and config name mismatch. what was intention? https://github.com/pkp/pkp-lib/blame/01a2c1404a4b5634554d9c2f080dffde723facee/controllers/grid/files/FileDateGridColumn.inc.php#L53
• Finding where something is used:
  • genre settings for isSupplementary and metadata types. See references in database, then track those keywords back to the form where the description is.
• AuthorizationDecisionManager logging policies that failed
• constants tools
• Postman
• mailLogger plugin

[jonasraoni]

As a new developer landing in the sea of unknown code, what I always miss is:

• Understanding how the software works (https://wiki.osgeo.org/wiki/File:Ojs_workflow.png)
• How to build a simple form to save/load data (covering routes, ways to save data, if I can create new tables/fields, permissions, etc.)
• Small and concise text + hands-on examples are a great way to learn (the best documentation I've seen so far was the one from Vue.js).

[marcbria]

Soooo long ago we made a version of this diagram that IMHO is as detailed but more clear than the original one. https://revistes.uab.cat/web/sites/default/files/documents/workflowojs-v04.svg

Some time after (but still far away) we did a simplified version to explain OMP that could also be adapted: https://revistes.uab.cat/web/sites/default/files/documents/all-v3.png

Jumping to a different topic... as an old sysadmin I'm used to track errors in the sever side, but in different posts Nate made us notice this is going to change. More and more logic is in the front end so would be great if a video about "how to debug" in the front end is recorded.

I'm not thinking only in coders... it will be useful for sysadmins and even final users that need to track an issue.