Haha ye. It is super interesting to see all those OS principals and seeing how nintendo implemented them. Stuff i will never forget either and some design patterns i have implemented in my actual job too
Maybe, part of your job is to not touch anything in a random day and observe what happens when something breaks. That way, you can document what’s not being fixed so that your team is more prepared when you’re actually not there.
This is the result of so called tribal knowledge in software development. It’s even worse when the senior citizen who understands everything retires, goes senile, or dies.
You kids today. In my day we used Visual Source Safe and would accidentally leave a critical file checked out when we went on vacation and nobody else could get anything done until we came back.
I once had to go on a longer medical leave, couple of months. In preparation, I documented everything - pages upon pages answering all questions in easily searchable formats. For more than a month, any questions I got were answered with links to specific sections in the documentation, so people would know where to find everything. I put the links everywhere, in total there were at least 200 links to various sections of the documentation throughout all our communication mediums, as well as all information repositories.
After I came back from leave, most of the things I was responsible for were turned off. When I asked why, the response was “we didn’t find your documentation”.
programmer_humor
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.