3 ms·
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
by steventhedev 4y ago
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 for dev laptops.
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).
- bjconlan 4y agoYeah, this was my problem (we have many Mac users so my liberal use of 'xdg-open' wasn't appreciated (I'm sure it was more than that I didn't have a Mac to test it against'.) 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