That was an interesting read, thank you!

Why is it not possible to use stone wall space?

I agree. That reminds me: > Imagine a doctor performing a procedure and then suddenly saying “Oops! Something went wrong…” That is the last thing anyone wants to hear when the stakes are high, whether it’s surgery or someone’s source of income. That is not the time to be cutesy or fluffy. > —https://wix-ux.com/when-life-gives-you-lemons-write-better-e...

You may consider using a password manager[1] that allows to auto-fill the password field. Use xkcd-based passphrase[2] for the master password to make it easier to type.

[1]: just not LastPass with their regular security breaches. Personally, I recommend Bitwarden.

[2]: https://xkcd.com/936/

Actually, I have this on my TODO list for a long time, maybe someday I'll finally implement it.

[^1]: https://developer.spotify.com/documentation/web-api/referenc...

If anyone's else also confused about that part, there's some context: https://news.ycombinator.com/item?id=19022640

You could add the whole albums to the playlist, one by one, and then play the playlist w/ shuffle disabled. This last bit makes it a limited workaround, however.

On the other hand, Spotify API could allow to implement the custom solution to shuffle these, similar to https://spotifyshuffler.com/, if you have enough skills, time, and determination to do that.

Beware: I started this long before I became a fan of markdown, so the syntax of the whole file could seem as pretty weird, but it works for me. I mainly do `rg ~/commands.txt` in shell or `/` in vim when I need to find something in there.

There are also definitely too much commands dumped into the `Etc` section. I should reorganize this some day.

I know some devs that are anxious if they don't fix _every_ single comment in their PR, even if I'm just suggesting something as "nice to have". This helped to mark which comments are actual priority.

Also, make sure you're using code formatter in your CI, to avoid reviewing the code style, as this can start some unnecessary wars and frustration.

Also, I suggest sharing this article https://mtlynch.io/code-review-love/ with your colleagues, especially step 8:

> As the author, you ultimately control your reaction to feedback. Treat your reviewer’s notes as an objective discussion about the code, not your personal worth as a human.

To some degree, as a reviewer you can keep your tone friendly, but ultimately _every_ sentence can be took as personal attack, and you can't really do anything about that. Keep that in mind, don't focus _too much_ on the tone, and don't let that prevent you from giving a comprehensive review.

One other thing I personally do, because I'm famous for giving _really_ thorough reviews, is to make sure from time to time that the other person is fine w/ that. Simple DM "I hope you don't feel too overwhelmed by my CR?" helps, especially that often people respond that they actually approve I'm so thorough. If you worry people get offended, it is easy way to make sure if these worries are valid or not.

I find it quite amusing that the scam used the domain `people.ds.cam.ac.uk`, which contains `s.cam`.

Two main characters were meeting after-school to dig a tunnel, although their motivation was a little bit deeper (sorry, I couldn't help myself) than just digging itself.

I assumed that this software is basically a tongue-in-cheek reference to that, I had no idea this can actually have a practical purpose.