901 karma · joined November 21, 2020
https://www.upi.com/Top_News/World-News/2020/10/07/North-Kor...
Oh, the irony...
I wouldn't say that. YouTube is happy to pick semi-random popular videos from 14 years ago and generic crap and [re]viralize them by shoving them into everyone's recommended feeds, so much so that comments like "the algorithm has brought us together again, see you in 10 years" have become a meme.
Most of the things I do aren't really that important, but there's this one project where I need everything to work perfectly, or else I need to know about issues as soon as possible.
The whole thing depends on input I get from scraping, which basically means the data model can change at any time and there's a myriad errors that can happen. Besides from this input data, I also have to check that my "big-picture" assumptions about the model are correct before the actual program runs. In particular, the sample data already determines what values should be possible for most database tables; these tables don't change during program execution. I have a(n also immutable) config file that determines what can be queried from the database. This means I can prove that my config is/isn't correct (e.g. the program should never try to query for an inexistent value) before the program runs. And it should then be possible to turn these values into types to further tighten up the code and my workflow. But creating types from database values just feels all sorts of wrong. Or is it not?
All I really want is something that is DRY while also 100% ensuring the consistency of data before I run the program. I guess my idea is: Everything that can be automatically proved about the program before it runs, should be, and it should be stopped on its tracks before running if it's provably incorrect. I don't see how Clojure does that.
From everything I've read about Clojure, it sounds like the perfect fit for this kind of thing, but in the end I always conclude I'm too dumb and undisciplined to rely on myself to use it correctly. I make too many mistakes that boil down to assuming something has a different type than it actually has, or that it has a field it actually doesn't, I forget about checking important conditions, etc. And, to be quite honest, I'm too lazy for my own benefit, so I need the system itself to force me to do it the right way, while Clojure assumes you're responsible enough.
So I guess my question is: If I switch to Clojure for a critical project, how can I sleep at night?
> This data allows deterministic dependency resolution which is required by mach-nix[1] to generate reproducible python environments.
And no, I didn't get the URL wrong ;)
(meaning: just read TFA)
You might also ask yourself: Why would the HDL/LDL ratio matter? Why would mineral ratios matter? This pattern is not unique to Omega 3. Search for "micronutrient ratios", also timing the consumption of certain vitamins and minerals, fiber, etc. Nutrition isn't just about putting enough molecules into your body.
I've no idea what you mean by that.
> This video is the world we live in.
Reality includes komodo dragons, just as it does kindness. You say nature isn't "humanoid" and then ascribe to it qualities like ruthlessness. You're just as biased and delusional as whoever you're criticizing.
Also, typo: Higest -> Highest
Just please do some research as this stuff is not risk-free.
So, Nix? (Except maybe the part where there's no effort/changes needed...)
There's precedent in Ecto for a "magic" operator (`^` if I'm not mistaken), so it wouldn't be a stretch to implement it here as well.
It does get a little tiresome to keep starting over, so maybe breaking down each text into subtexts that each get memorized separately would work even better.
I wonder how well this would work for math and other technical texts.
Edit: I can memorize some lines very quickly, so it would also be nice to be able to skip all the intermediate steps and just completely hide the line, then increasingly backtrack if I forget it.
Another minor UX feedback: maybe align the "reveal" and "yes" buttons so I can press the buttons faster and without having to look at them.