Learning Styles Comparison 
- Aural / Auditory (vArk)
- Kinesthetic (varK)
- Multimodal (MM)
- Read/write (vaRk)
- Visual (Vark)
For most languages a single standard for documenting functions and methods in block comments (a.k.a. doc-blocks) has emerged.
There does not seem to be a definitive convention for documenting bash functions and files. Several different conventions exist
The following conventions are available:
If you look on Packagist, [the most popular packages] for [Feature toggles] are:
qandidate/toggle"Feature toggling for your PHP application." (
opensoft/rollout"Feature switches or flags for PHP" (
flagception/flagception"Feature toggle on steroids." (
joshuaestes/feature-toggle"Provides feature toggle functionality" (
zumba/swivel"Strategy driven feature toggles" (
The PlantUML Standard Library makes it possible to use popular icons in PlantUML with zero effort.
The plantuml-stdlib code as based on other projects.
As there were changes in some of those repos that were not (yet) in plantuml-stdlib, I decided to open some merge-requests to update things.
Because I don't like to do thnings manually that could be automated, I spend some time creating two BASH scripts:
Family trees/hierarchies of derivation among MUD codebases.
It is based on the information from: https://en.wikipedia.org/wiki/MUD_trees
Solid lines between boxes indicate code relationships, while dotted lines indicate conceptual relationships.
Made using Graphviz (DOT syntax).
|# This file is for unifying the coding style for different editors and IDEs|
|# For full details see: http://editorconfig.org/|
|# An explanation of all available properties can be found at:|
This gist contains all files use in this jsfiddle that shows information from DockerHub for a given project group on Gitlab.
The result can be seen here: