I think something that relates to the pain of onboarding with unique configurations for core tools used by developers would be useful. To be specific I wish I didn't have to forward a developer to an already obsolete wiki page then nod and smile as they complain/tussle with the experience/vernacular/context of a document that has no owner. I think this is a bigger problem (which could be mine and mine alone as everyo…
Point is that just taking the tiny step of forcing this from a wiki page into code can tip things towards automation. The real difficulty is keeping those scripts up to date. I'm still working on a solution for that (hopefully I'll have something to share in the next few weeks).