Crazy that companies will do this shady stuff with client side code. At least it was slightly obfuscated at first, but that’s just incompetent fraud to leave it so obvious that a self professed non-software engineer (though clearly a smart guy) can read it and deduce what’s happening. Throw a tiny bit of random noise to the stepdown logic and it becomes much harder to find and reproduce as proof.

My shameful secret is admitting that LLMs are great for things like getting comfortable with a programming language. They’re generally trained on the same publicly available samples as these courses and the conversational extrapolation is great for identifying concepts you forgot the technical terms for (ie. “How would I do this in python: [Java code]”)

Vibe coding sucks, but walking through some examples with an LLM and a REPL can save hours of navigating docs or Hello World blog posts.

I might be alone on this but the freezing point of water is almost irrelevant in daily life. Any precipitation from 30°F (-1°C) to 35°F (1.5°C) results in some mix of snow/slush. Less than that and it’s snow/ice.

However if you live somewhere where they use salt as a de-icer, knowing the freezing point of saltwater (0°F, -17.7°C) is very, very important.

Its not 2007 any more, we’ve had nearly 20 years to research this stuff and the results are pretty conclusive. Even a broken boomer is right twice a day 🤷

No matter what structure they’ll focus on what engages them the most, which is pretty much always going to be the digital dopamine drip feed in their pocket.

I know you said no voice-reading-text and wanted personality, but for my money nothing is better background listening than History of English. You can listen to the whole narrative of an episode or just pick up some cool etymology here and there.