Unless you tied it to the exact areas of the codebase somehow, finding specific information about the code in video form would be hard. Plus, for myself, I don

Unless you tied it to the exact areas of the codebase somehow, finding specific information about the code in video form would be hard. Plus, for myself, I don't know how many times I've seen a piece of cryptic code written by some prodigy who left the company years ago. It would take a lot of effort to get documentation around these scenarios. Instead, it would be easier to get a company to get on board with adopting proactive documentation practices. This doesn't necessarily mean explicitly writing technical documentation, either. It can be implicit. Some companies that I worked for in the past would have policies around how work would be completed. A big thing they did would ensure that all of our work had tickets associated with them and that all branches were named after the tickets. This made it trivial to blame a line of code and start digging into not just who made it or when, but also why. I could see what other tickets were related to it to find out a lot of valuable contextual information, sometimes even for code that was implemented years before I showed up.