I think by "investigating a design" he means looking at how a component or system is structured to understand how it works. This is pretty common as a lot of de

I think by "investigating a design" he means looking at how a component or system is structured to understand how it works. This is pretty common as a lot of developers will get called to work on a piece of infrastructure that they aren't familiar with. They have to understand what they're working on so they apply an effective change Also, documentation is huge. I've worked with a lot of small companies and startups that have adopted it to share knowledge and to ease troubleshooting/onboarding. If you aren't doing it at work, consider it. There are a lot of approaches to it, such as self-documenting code, writing knowledgebase articles, recording demo videos, leaving contextual details in PRs, and even simply linking these pieces together so they're easy to find