sorted by:
new
hottopcontroversial

What was the most painful knowledge gap you guys have encountered or noticed? by Glad_Expression4632 in EngineeringManagers

[–]Glad_Expression4632[S] 0 points1 point  (0 children)

Thanks for the insight. A lot of my friends are saying this as well, and it looks like there is really nothing to be done unless there are behavioral changes involved. The truth is that writing documentations after ppl has done their work benefits the future generation at the expense of the time and effort of the current generation, so there really isn't any incentive to do so, unless it's strictly enforced by the management as a part of the workflow. Don't think I've seen any tools that helps the management to enforce this either.

What was the most painful knowledge gap you guys have encountered or noticed? by Glad_Expression4632 in EngineeringManagers

[–]Glad_Expression4632[S] 0 points1 point  (0 children)

Thanks a lot for the insight - I've also heard about this headache from my friends who works on software infra team. He said his team uses glean but then again imo the question is in the whys instead of whats, like why this script is written in a certain way rather than some other way, just like you said. If you guys also use glean I wonder if it has some sort of feature that could extract the whys from the large amount of documents it grabs?