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…
At an old job I spent my first week on the job documenting the process from a wiki page into a bash script (albeit with some comment sections that said "do this manually"). A year later, one of our devs was up for a laptop upgrade and I convinced him to give Linux a try. I shared my script with him and he was up and committing code later that afternoon. The next week we had a company wide mandate to switch to linux f…
A move to devcontainers helped this but dictated some ide behaviours (majority of devs are tried and true jetbrains people) so changing they way they use their tools made this a 'no sale' so again like the wiki my scripts sit idle. But I dream for the day a `curl ${url} | bash` can solve these teething issues