288 karma · joined November 14, 2018
To me the interesting point is the reminder that there is an innate tension between going fast and being "clean" (i.e. maintanable/understandable). And once you are aware of it you can make your decisions in an informed way. Too often this tension is forgotten/ignored/dogmatically put to the back ("performance doesn't matter over cleanliness" and the likes).
Mind you, I'm also of the camp that performance is very secondary to cleanliness in modern enterprises, but I appreciate a reminder of just how much we are sacrificing on this altar.
The tests he put together here are hardly something I'd call a straw-man argument, they seem like reasonable simplification of real-cases.
" (while the age for rifle is federally 18...) Exceptions to this include if the gun is to be used for specified activities including employment, ranching, farming, target practice and hunting. "
and
" For example, in Vermont it’s legal to sell a handgun or rifle to someone over 16. In Maine, Alaska, Minnesota or New York State you can sell a rifle to someone over 16. In Minnesota, as long as it’s not in the city, you can sell a rifle to a 14-year-old without parental consent. "
Seems confirmed by ( https://giffords.org/lawcenter/state-laws/minimum-age-to-pur.... ):
" Age 14 or 15 and has a firearms safety certificate "
I don't think the problem is so much about them checking on the kids' family after being called by some neighbour (which is prob. legitimate to avoid any risk of neglect etc.).
As you said t he problem is that they arrested a parent who, for all intents and purposes, was complying with their questioning. In front of their children. And threatened the second parent with arrest. And taking away the children.
I don't see how you can make the jump from "response was disproportionate" to "commentators are not that different from the person who reported the incident" though.
As mentioned, this seems to be more prevalent in people who are, objectively, well-off in the financial department, so it's not like they "hate" the system per se and could afford degrees of financial independence that many others will never be allowed to.
But otoh the only "real" traction we are getting for issues like, in this case, climate change seem to be relatively recent and caused by more and more catastrophic, tangible effects (80% of Pakistan under water, heatwaves, tropical storms becoming a regular occurrence in the coastal US, you name it)
I am an "official" millennial, born 1989. One thing I have noticed (in an anectodical, personal and subjective way) is that my age bracket, especially those I would consider higher on an intelligence/success curve, appear to be so much more closet-nihilist than everyone else around.
What I mean by that is that, while of course we don't really want to see the world burn, we are secretly hoping, in the dark, when no one is watching, for things to always go tits up a bit. Like there is a subconscious fascination to the aesthetics of Nero playing the lire while Rome burns. And upon deep self-reflection that's always a bit unsettling.
I don't know if it's related to the generational trend, or maybe it's just selection bias over the people around me, but I think it's mostly the former rather than the second. Probably stems from the fact that we saw our beloved parents struggle in old age with health and finance, while we live in a more priviliged regime (remember that I mentioned this applies mostly to financially successfully peoples) where money seems more immaterial.
So I guess the author might be onto something about this whole financial nihilism thing.
I hate this general reccomendation style that names need to be short. This only made sense in the old times of programming where you had to actually type them. The reality of IDE's bringing all forms of intellisense and autocomplete means you almost never type a name out, thus being short brings no benefit if not "habit". You should really try to have understandable names, detailed names, but not care about shortness. "timeout" is a good variable name if you language has some great type system and your coding works with that. "timeoutInSeconds" is a better one if you are just using an int/long to distinguish it from "timeoutInMillis" and avoid silly mistakes.
You are thinking active sabotage like git-committing a bug. Passive sabotage is trivial. I recommend skinming the CIA saboteur manual on the topic.