shuckster

It’s slightly buggy, but I do depend on this utility.

Main point of contention: Adding a new bookmark in Chrome and changing the folder in which it is stored almost always causes an error and restore to the previous state.

Not a huge deal, but I have to consciously remember to do each action atomically, add, rename, move, with a second or two in between each action. Even then it’ll usually take a couple of goes to her right.

I also have a couple of “accounts” for work and play. Don’t forget to sign into one of them for more than a couple weeks. They expire.

Good to use a bookmark backup script: https://gist.github.com/shuckster/a91724adf5db1897ef07a69165...

Good point on teams, but I'm not convinced that linting is a great tool for juniors in the same way. Frustration is an instrument for learning, but adhering to linting rules forces that energy in the wrong direction for those still going through the basics.

On the point of being a robot, in what way are we not already "robots" by stubbornly sticking to what we think of as best? Are you not already a robot by limiting yourself to a narrow-range of what you consider "readable"?

I also find it annoying to occasionally lose white-space to Prettier. But I've learned my way around it: By either adding short comments or by decomposing single-lines into multiple ones, which ends up improving readability anyway.

I think the benefits of linting are similar to writing tests.

Initially the practice is detestable, especially if you've already developed some hard-fought coding chops without them. But after some time the practice itself influences your ability to write better code to start with, and successive tests become terser and more useful.

I think the same is true for linting. I found being involved in projects that enforce linting rules on commit to be insufferable, so I installed Prettier and configured it to format on save. Over time the auto-formatter did less because of the habits I was picking up.

I did have to confront the idea of being less precious and attached to my own coding-style, but frankly I still have pretty strong opinions despite having an automaton do my thinking for me in some of the projects I work on.

Of course, neither tests nor linting are a panacea, but so long as you give a hoot to start with you won't be able to avoid writing better code after using them.