John Willis’ “Infrastructure as Code” should be a startling epiphany for anyone who has long neglected process and people in favor of technological solutions. Yet, I hope anyone here doesn’t need convincing about the validity of institutionalizing the collective knowledge
However, I wonder about a critical level of infrastructure maintenance that seems to be missed, document maintenance.
I’m sure everyone has experienced the frustration of reading a document with an invalid URL, but is this be accepted?
Should documents not be kept in repositories as well? Why not take the same proactive approach to maintaining links as we do “Not breaking the Build” when programming?
So why doesn’t your team have a utility to scan internal documents and links when they propose changing page structures, before they’re made live?