I would read/watch/etc the heck out of this for literally every large software company.
What's the part of your stack/operations/etc you're proudest of?
What is the corner that touches everything where staff engineers fear to tread? Where 3 multi-year efforts to fix failed?
What's the part of your stack/operations/etc you're proudest of?
What is the corner that touches everything where staff engineers fear to tread? Where 3 multi-year efforts to fix failed?
An open secret in the tech industry is that these documents exist, they're just not public.
Step one: Hire someone who was recently at X, in the ordinary course. Have them braindump into a document.
Step two: Ask for comments from your other previously-X developers.
Step one: Hire someone who was recently at X, in the ordinary course. Have them braindump into a document.
Step two: Ask for comments from your other previously-X developers.
There's an interesting professional challenge about respecting secrets about things you built, because on the one hand NDA etc etc etc, and on the other hand ex-employers don't own most contents of your brain even though a lot of it is relevant to similarly shaped new employers.
(One function of consultants is to launder practices of various firms into Industry Best Practices (TM) so that there is technical diffusion faster than the ordinary cycle of people moving around the industry.)
