Too little or too much iodine can fuck up your thyroid (only because it uses iodine directly), but otherwise it's not real sensitive to lifestyle or diet... however it can influence what you want to do and eat (low thyroid causes sugar craving and lack of motivation/energy to do anything). TSH levels fluctuate depending on iron, selenium, and sugar intake, but there's no strong evidence that any of these will cause more than transient deficiency; indeed, low thyroid is a known cause of poor iron absorption, so it's rather the reverse -- eat well and you still won't get good use of it. At least one gene has been identified that causes poor T4-to-T3 conversion, IOW the DNA that controls the required enzyme is defective. Anyway, if you try treating hypothyroid with diet and exercise you won't get far. I can point at myself as a good example -- I'm more active than most folks (I've done physical work my whole life) and I eat almost entirely home-cooked, nutrient-dense food, but that doesn't do a thing for my Hashimoto's.

If I find that particular paper again I'll let you know. And depression as a consequence of subclinical hypothyroidism is very well established, but no longer generally acted upon. It used to be routinely treated as such, but when the TSH test came to prominence, most doctors started treating to make nice test results rather than treating the patients' symptoms.... despite that all the evidence is against using TSH as anything but a crude marker that something is wrong. False negatives are extremely common.

Here's a starter kit:
http://hormonerestoration.com/...

I have Hashimoto's thyroiditis, and I've had to take up reading the Journal of Endocrinology in sheer self-defense. It's quite shocking how much well-established endocrine research has never filtered down to GPs, never mind other specialty fields, despite that a malfunctioning endocrine system can fuck up just about anything else. I've concluded it should be the first line of inquiry (since fixing the thyroid will commonly cure a whole raft of apparently-unrelated physical and mental symptoms), but most doctors act like it's the last resort.

There's nothing better for turning you into a nervous wreck than knowing that your every word and motion are going to be dissected with the goal of disqualifying you...

Probably the most common cause of depression is subclinical hypothyroidism, specifically with low T3. One psychiatrist found that he could cure 90% of his patients by prescribing T3 to bring their active thyroid hormone level up to normal. (Prescribing T4 alone didn't work, probably because poor T4-to-T3 conversion is part of the problem here.)

Then it needs to be part of the qualifying exam, not external to that. If it's part of the exam, then it's obviously not going to be secret from the pilot examiners.

(Actually, I thought this was how it is already, at least in the U.S.)

In any case, you would need Amazon to actually enforce it.
While they do have more money for legal fees, they would risk a big PR issue if they tried to prevent some guy from working at Walmart after quitting Amazon. Also, the first guy with such a problem wouldn't have a lot of trouble finding someone to help them with legal fees, if only for the publicity.

This is probably just a scare tactic, to discourage people from leaving them, it is unethical, but not really enforceable.

Does that manual encourage bad code ?

The second one should also include "immutable". If it's hard to understand it will evolve easily to non working, and time spent on improvements can start to creep up very fast.

I have worked in very clever, solid code, but not easy to read. It was then maintained and extended by average, but competent programmers down the road, and turned into a big mess, only because it was so hard to understand.

In my experience, good code is easy to read, above all. That will make it easy to extend it coherently, find bugs and stuff. Also, if it doesn't work OK, it's easy to find out why. The single metric that saves time, money, and improves quality down the road is readability. Eveything else should be suject to that.

And, about the last point in the "article", "efficient", it's nonsense. Premature optimization is the root of all evil. You should _always_ follow the second rule of optimization (see http://c2.com/cgi/wiki?RulesOfOptimization ).

PHP can be good or bad, like any other code. Lately it's getting better.
As an example, do you think this looks bad? Looks pretty good to me.

  https://github.com/symfony/sym...

I have some awful, unreadable examples I could share in Java, PHP, Javascript and even C, but chosen language no longer forces you to write bad code. Maybe Perl, but I haven't seen it lately.

Fortunately the comment history is preserved. Not 5 posts up you state, and I quote:

"Most Americans don't understand just how restricted speech is in the UK by comparison to the US"

Restriction of free speech pertains to government restriction. We don't care what companies / institutions do. The BBC isn't the government.

So, I guess the gp was correct.

This weekend I saw a guy apparently picnicking across the road from my house. After a while I went over to see WTF, and turns out he was working for a mapping company (and the company drone was flying overhead, snapping photos). He told me that their maps are accurate to within 1/8th inch.

Or someone will figure they can tromp the pedal ALL the time because the car will take care of it... then when they get to a higher speed zone, the car will speed up inappropriately and run someone else off the road, or slide off the road because 45mph was okay on ice but 65mph is not. Or it will slow when doing so is dangerous (frex, when that truck behind you can't slow down that fast), but the sign said to. Situational awareness is not just the speed limit. It's a continuous series of judgment calls based on the whole damn road and everyone on it.

There are roads in California where the speed limit is different on opposite sides of the street, I shit you not. So on the same street, westbound the speed limit might be 40mph while eastbound it's 25mph. When I asked the highway department about this, I was told it's due to the street being on the boundary of different 'zones'.

No. You make the baseline a point the child won't cross again. That way you don't have to ratchet up; indeed, you'll probably never have to repeat it. Think of the time you burned your finger on the stove... you didn't try that again, did you!

I'm a pro dog trainer, and it's the same way. If a dog bites (eg. egregious misbehavior), and you just tap 'em on the nose, pretty soon they figure out your response wasn't serious, so they try it again... a little harder tap, and they figure out they can handle that just fine too, bite again, and it becomes an arms race. (That's precisely how puppy nipping becomes adult biting.) So instead you deck 'em first time around, so they know with certainty that what they did was Dumb and absolutely won't be tolerated, and they never try it again. It may sound harsh, but it's a lot kinder in the long run -- especially it's psychologically kinder, because you've set the solid boundary that the dog (or child) was probing for, rather than making it a fuzzy thing to be challenged over and over in case it's not for real. And when the boundary is fuzzy you do have to punish over and over, and get harsher as they discover how much they can take, and the boundary never does get established because they learn that if only they can take a little more, it'll move again.