The fact that the loop is doing “find first driver matching these strange criteria” seems most obviously obscured by the pattern of assigning a value, then killing the loop or not. This strikes me as the part that makes the algorithm tedious to test, since it forces us to use a collection to test the intricacies of the inner conditions.

Once we isolate “find first driver matching condition” from computing the condition for each driver, I consider the rest a question of personal taste. Specification pattern, composition of filters, something like that. Whatever you find easier to follow.

I guess it’s time for a “mark this time so I can go back to it” feature, to reduce the need to pause. 🤷‍♂️

I am definitely keeping an eye on my electricity bill right now, since I have Unmanic running full speed and it’s about 3 weeks into a 4-month job that might only save 1 TB.

You can, but fuck off and do it somewhere else.

DWTFYW.

0 is not 9. Look closely.

Pig’s ass.