2 ms·
I have to agree with many of these, but a bit sad that they need to be stated (I feel they are "common sense," like "Try using the tools I already have before r
by ChrisMarshallNY 2y ago
I have to agree with many of these, but a bit sad that they need to be stated (I feel they are "common sense," like "Try using the tools I already have before reaching for new ones.").
As for the documentation one, I'd sure like to see folks at least do more headerdoc-type stuff. In my context (Apple native development in Swift), DocC has given new impetus to at least headerdoc.
I wrote up my own post on how I do documentation: https://littlegreenviper.com/leaving-a-legacy/ https://littlegreenviper.com/leaving-a-legacy/
- langsoul-com 2y agoCommon sense for one isn't so common for another. When knowledge is implied, what happens when someone new comes in? How do they find out this hidden knowledge?
- ChrisMarshallNY 2y agoWell, the classic way, is training, shadowing, and mentoring. But those were the days, when people stayed with companies for many years. "Tribal Knowledge" is actually the classic way that skilled vocations have been passed on for hundreds of years, but then, companies got obsessed with hiring people right out of school, and putting them on projects that used to be done by folks with many years of experience. I have found that process and documentation are supposed to replace this type of knowledge transfer, and I have also found they don't actually work that well, for many reasons.