Shared Responsibility: Teamwork!
I'm kinda hurting here, looking to know that I'm not alone in this... Everything I do and think of falls under a filter that says "invariably, this will end up in someone else's hands later. Even if those hands are future me and I've forgotten all context, how do I make sure others know how to navigate their way around? Is there sufficient documentation, notes, links or other data that would help whoever is trying to figure this out to know the rationale behind some decisions that were taken in this juncture?" I lead by example. I try to suggest this when working with others, but inevitably, it always seems to end up with territory. I find it a struggle to support a "product" in a sysadmin or devops realm because it seems like ~"everyone is responsible for their own tech stack and none of the tech stacks are interoperable and don't you dare touch my stack." Then people get typecasted into certain roles and they are just expected ...