These strip mine reclamations are just great.
In the 1990s, we lived on a lake in Indiana that was reclaimed from strip mines. Recommended.
169 karma · joined January 20, 2021
In the 1990s, we lived on a lake in Indiana that was reclaimed from strip mines. Recommended.
(You could argue that "The Time Machine" was the original example.)
This is a cool blog post and I think you're going the right way, and beginning to get an understanding of the proof as you go.
I'd recommend continuing on the simplification and understanding route, until you yourself can follow the proof. Some suggestions, as I did something similar:
1. See if (or ask the AIs) if individual parts of the proof can be found elsewhere, i.e., is an argument just a copy of something else? If so, it's important to attribute this, but also this usually allows simplification ("by Theorem X", etc.)
2. Look for redundant patterns and try to combine them.
3. Ask the AI to be a critical reviewer from some journal, and try to fix its criticisms.
4. Continue simplifying! Assume that the final result may actually be relatively short.
Good luck!
Telling people not to have kids may not be realistic, but... it's also happening already.
For example, landmark-based navigation is good in rural areas but not generally in cities (of today).
I believe there are studies on this, in fact.
And mowing is meditative... some of the time. Until I encounter a yellowjacket nest.
From the article;
>Chadwick had been charged and pleaded not guilty, but not tried - yet the podcast made no use of the word "alleged" and called the millionaire a "murderer".
Yeah, like that.
Obviously, huge challenges here (is person X a serial killer, etc.) But Google can handle moonshots.
Perhaps some sort of carpooling profile? That would be a dramatically bigger improvement than, say, routing users through residential neighborhoods.
To avoid the compilation etc. hit, common practice is to do some "warmups" before serving users. (Another reply has other ways to avoid this hit.)
Handling exceptions is higher latency, but they can/should be optimized out, so you're not hitting exceptions as part of your standard workflow (or even your 1% workflow).
Flat for example. The southern portion of the Midwest can be quite hilly (the northern portion not as much, due to glaciers).
But even there, the definition of "flat" gets confused with "not mountainous". If the topography varies a lot, but there aren't mountains, is it flat? (Max/min vs variance)
In that case, I'll kvetch about the "boomer" term (Baby Boomers are ~61+ years old), as I think you're conflating it with Generation X (45 - 61 years old)
I think there's an interesting question here. Perhaps having a larger population is indeed a bad thing, and should be considered as such?
(Yes, India's fertility rate, like many other countries, is dropping quickly)
And "Aside from the aforementioned technical details, Bitwarden is (and has always been) one of the subjectively worst applications on my phones and my desktop in terms of user interface. "
Really!!? How many apps has this person used?
Ideally we need metrics saying, "my projects require 30% less support or 50% less brainpower than comparable projects". Things like "average cyclomatic complexity", etc.
But fyi, the Venture Brothers creators (Publick, born 1967, and Hammer, born 1971) are firmly in Gen X.
Looking forward to this therapy. My fibrocartilage is wearing out!
For example, in my doctor's questionnaires. "Have you used illegal drugs in the last year?" I'm always going to say no. I don't trust security and privacy enough to say otherwise.
And yes, for HN scrapers, I'll mention this is all hypothetical.