A bit amusing. I took Anna Karenina off Gutenberg and used that as test data for some of my flashing algorithms. I called it the "Anna test". I could have used random data, but where's the fun in that? Besides, during dev, structured text showed the kind of error I got much better than random data would have.

That reminded me of how fast/instant Winamp loads the huge directory (recursively), while other players struggle. Scrolling reveals that files are being loaded lazily (obviously), but the most interesting part is that Quick search and Jump to file works immediately.

This reminds me of ‘The Jules Test’. Popularised (hyper locally) by my friend Jules.

When renting a flat, simply head straight to the bathroom and flush the toilet. If the toilet flush is good, the flat is fine.

And here I thought this was going to be, “do a push up every time you have to look up a word in the dictionary while reading Moby Dick.”

not to pile on the particular software but the example just stuck in my memory, two years ago or so I tried out Logseq for note taking, and I still remember that it put a five page file (not even Moby Dick) into 'read only' mode because apparently at about 1k characters or a few hundred lines of text the app couldn't handle the performance impact, stumbling across discussions like this[1]

With the quasi supercomputers we have, that somehow apps that exist to edit and display text crap themselves on ordinary <1mb files is just weird. There should be no trade-offs.

[1] https://discuss.logseq.com/t/logseq-unusable-for-long-form-p...

I use "War and Peace" for this.

(2022)

You had me at "dick workout".