The US Army has formal training about this and provides an Advanced Skill Identifier (ASI) to those training to practice it. See: * Techniques for Effective K

The US Army has formal training about this and provides an Advanced Skill Identifier (ASI) to those training to practice it. See: * Techniques for Effective Knowledge Management, ATP 6-01.1, https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/atp6_01x1.pdf https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/atp6_01... The Army technique follows the DIKW model. https://en.wikipedia.org/wiki/DIKW_pyramid https://en.wikipedia.org/wiki/DIKW_pyramid When I did that job as NCOIC for a major sustainment command in Afghanistan I learned how to mix documentation, automation, and empathy to create a shared vision amongst the 24 shops that comprised the unit. I never would have matured into this writing corporate software. Since being laid off this year I am choosing to regress and aggressively embrace tacit knowledge. In the past I used to publish things I had learned to GitHub and many people found those writing extremely beneficial. As a JavaScript developer, however, I have finally been beaten into submission by the neglectful immaturity of my profession and so many of my peers. I have grown tired of debasing myself when so many people are hostile to any concepts of helpful guidance. The name of the game is attain employment by writing the same framework glue over and over thereby pandering to the desires of the least competent and least employable of the workforce. Any deviation is met with hostility first and possibly curiosity later. As a result I abandoned that line of work until I found a career change and now keep my learning about automation, performance, and architecture to myself.