335 karma · joined July 5, 2015
https://www.prismnet.com/~hcexres/style/pompous_words.html
First time encountering the expression for me. It's not about jargon, as far as I can tell.
https://en.wikipedia.org/wiki/List_of_U.S._cities_with_most_...
http://www.japan-guide.com/topic/0011.html
The LGBT stat came from Wikipedia. For controversial stuff like that in the US, WP is pretty good. I used to think it was 10-15%, 1 in 7 was the number I learned growing up, I guess it's 1 in 25.
https://en.wikipedia.org/wiki/LGBT_demographics_of_the_Unite...
For me, "abnormal" generally means "what is wrong with you" (the response given here), whereas "normal" can even include eye-rolling and "oh so you're one of those". The difference between 1 in 33 (3%) and 1 in 666 (0.015%, from the tail end past +3 sigma which accounts for 50% - 99.7% / 2) is really quite palpable.
But again, let's face it: it's not as common as I thought, and it's not as uncommon as you thought.
Let's face it, we're both being kind of sloppy.
Personally I would never do it, but like, different strokes.
Also, define richly. Assume monthly savings of $2000/month on housing, call it $500 / week, that's $25 an hour. Plenty of people make less than that, so again it's just priorities.
+/- 3 sigma = 99.7% of the sample, and we know 3% is > 2 hours (for all of Japan, not Tokyo). There's near the same percentage of LGBT adults in the US (~4%).
All we're arguing over is the use of the word normal. Would you be happier with "uncommon but not an extreme outlier"?
http://nbakki.hatenablog.com/entry/2014/02/20/124942
and this one for Japan paints a more vague but differently interesting picture:
http://www.japan-guide.com/topic/0011.html
Really, it's not unusual to meet a salaryman with a 2-hour commute.
The four things I can think of are:
1) tighter registration and controls, GPS tracking
2) better training and education for gun owners, mandatory, free
3) arming more citizens so they can take out mass shooters
4) better training in non-lethal methods for police
It was hard at first, but we still have sugar in various forms around the home to use on occasion. We're buying more fruit now too, but eat less than it takes to make the juice we eliminated.
We're losing about one pound per week, with no change in activity levels. So that's crudely about 500 calories per day, each. We have sweet things for social reasons, or to celebrate. The trick is just to avoid buying them so you can't eat them when you get hungry. Once we get down to our target weights I imagine we'll buy more.
It's really quite shocking when you stop buying sugar, just how many of your usual purchases you end up putting back on the shelf.
Personally I believe that as far as financial success is concerned, how well you handle transactions is just as important as net worth (so it's best to have a lot of money and handle it really well), but that's impossible to quantify of course.
http://lesswrong.com/lw/jw5/how_much_wealth_is_produced_by_h...
But, mostly this was just me refuting your claim that I don't understand what it's like to be poor (and desperate). I could go on, in ways that don't have anything to do with organized crime, but I have to go now. It's really infuriating being told by someone that doesn't understand your experience that you don't understand your own experience.
If "understanding the poor" is your goal, you'd do well to dispense with the condescending generalizations.
Further, there's a misunderstanding about the method. You do a binary search on the "percentage" of code viewed as an instruction stream that is allowed to execute, starting from the beginning. I understand that a can have a different length from b. Given more code, you can also search based on timestamps. You never comment out a and allow b to execute without it, this is nonsense. If that's what you thought I meant, I can understand comments about not actually being able to program. I did not explain this clearly, but only because I had forgotten that it was necessary to explain this clearly, because some people actually don't know how to program, even on HN.
Poor quality control in manufacturing, natural crystalline formation defects, excessive impacts in handling, extreme thermal stresses, etc.
Cast iron, being a non-ductile material, in the daily thermal cycling of cooking, any minute microscopic fissure will start to propagate through a process known as metal fatigue, and eventually fail catastrophically.
To some degree, cast iron can be annealed or hardened, depending on your cooking habits. Something I do which I would not recommend to anyone else: I buy cheap cast iron cookware, heat it up red hot and pour cold water in it. If it didn't crack, them I heat it up again in an oven and let it cool down as slowly as possible to anneal any internal stress.
In any case, if the skillet is of great value to you, there are places that actually can repair it for you.
As a last tip, stop practicing skillet abuse and trying to be an iron chef. :-)