Some evenings are just magical.

I just ran into a stupid issue that took 30 minutes of debugging to figure out. I have some JavaScript that would cause a radio button not to be checked by my code after a certain code flow was taken. So take code path 2 - it works, radio button gets checked. Take code flow 1 then code path 2 - does not work, radio button does not get checked.

Turns out code path 1 used prop('checked', false) and code path 2 used attr('checked', true) and they are incompatible. Each on their own worked, but if I ever set the checked property using prop, setting that same attribute using attr would no longer function. Weird.

"$15.8 million every 60 seconds. That's how much US consumers spent in two hours on Monday night," reports CNN

Kind of meaningless if you do not also specify how many people this include. Spending per person would have been much more interesting. As in 4.7c per person per minute. Hmmm...

My 91 gallon reef aquarium requires RO water for top-up as the saltwater evaporates. Usually you get a container, fill it with RO/DI water and have an auto top-up setup to keep topping up the tank as the water evaporates.\

The problem is that if the reservoir runs empty, you risk damaging the top-up pump (mine has a safety shutoff), but worse - you run the risk that the tank's sump runs dry and you burn out your main return pump.

I initially tried to use Neptune Apex' LLS-15 sensor but it turned out to be horrible. It would measure accurately down to about 12cm, then it would spike up to 18cm and stay there - while the reservoir runs empty. Recalibration did not help.

The new Apple Intelligence feature is helpful in many ways. However I just discovered one example where it increased risk, not reduced it.

It has a feature where it will auto prioritize emails and raise the mails it thinks is high priority, to the top of the list with a banner to emphasize its importance. Just... in this case, it emphasized a phishing email: