abcdaiojjdfoj

I love Goodreads. I use it to rate and review books I've read. I use it to read reviews of books I have (or might want to) read. And I follow people who write interesting reviews.

I never look at whatever Goodreads recommends. The people I follow usually come across interesting books I would have never heard of. If they review a book, and it sounds interesting, I add it to the top of my list of things to read. This is a giant semi-sorted text file. If I feel the urge to read some book, and it's already in my list, I will put it to the top of the text file. A bit like a splay tree. I don't care that my stuff is not perfectly categorised and systematised because reading habits are not like that.

I pay no attention to the actual star rating of books on Goodreads. There are a lot of bad reviews on Goodreads. You usually know within 2 seconds whether a review will be worth reading. Sometimes I will filter books by lowest star. I often found the people I follow because I saw them write an intelligent, detailed, dissenting review of a book.

I like it when you have nice, composable utility functions. Ideally each test contains a short preamble setting up the appropriate context for the test to run. The preamble elucidates what the tests are actually testing. It can also serve as documentation on how to use those functions.

There will probably be some duplication across tests, but if the utility functions are idempotent/composable, they're usually pretty easy to read/understand and equally mechanical to write/update.