Yeah, fuck them. All of the up-side to being an academic disappeared more than a decade ago. If they think salary is the *only* thing theyâ(TM)re not winning at, theyâ(TM)ve got their collective heads up their asses.

Maybe you should read up on the evidence supporting the health benefits of mindfulness tasks before you write it off as useless.

Everyone has their reasons. In my case I had no real interest in ad blockers until dice.com's ad partners started serving exploits.

Agree 100%. I installed adblock plus when slashdot started throwing URL blocks from the ad rotator. How do I know the next ad rotation won't be a driveby? The industry provides zero guarantees and relies too much on upstream ad providers to vouch for safety.

To the best of my knowledge "head starts" in letters and numbers make no difference in long-term outcomes. I'm disappointed to hear Gates pushing for this sort of thing. Solid educational resources at the right developmental stages are critical for long-term success, not some sort of fast-track to the ABCs.

Investors don't care about 20% revenue growth y-o-y if EPS has tanked.
GOOG Earnings Per Share:
5.04(3/31/2014)
4.97(3/31/2013)
8.75(3/31/2012)
http://www.nasdaq.com/symbol/g...

This got a lot of publicity but it doesn't really add all that much security. Supposing you choose 4 words from a dictionary of 200k (roughly the order of magnitude of the OED), you arrive at about 70 bits of entropy. Conversely, choosing a 10-character password from a 62 letter alphabet (a-zA-Z0-9) yields 59 bits of entropy- the difference is only a factor of 1024. Attackers aren't so dumb as to just try choosing random characters- they have very good priors on how common any particular character sequence is in the typical password and will mix and match entire words, with or without leetspeak substitutions, etc.

Of course no matter how rigorous your policy, it all goes out the window once your users type the same password into some other random site.

Complexity matters mainly if your attacker gains offline access to your hashes. Far and away the main source of password compromise is non-uniqueness (using the same password elsewhere). This is actually the main benefit of forcing a periodic password change. Graphical and gesture passwords are horribly insecure from shoulder surfers.
If you can, support as many factors as possible. Multiple factors gives your users flexibility- they may not always be able to receive an SMS or have a card reader handy. TPM-based virtual smart cards are super handy for remote auth from a domain-joined device- no cards or readers required.

Don't apply for a dev job. Assuming there was sufficient math in your PhD apply for a data science or data analyst role, which will include a fair share of programming but also mentally engaging work. Hiring managers for these roles look for people that have strong analytical skills and the ability to learn new things (proof: you have a PhD). What languages you know is secondary in these roles to how well you dig in to a problem and deliver insights.

Gotchas more than quirks:
- the day you realize you put a side effect in an assert() call.
- the day you realize GCC, maybe it was V2, not sure this is still an issue, exploits extra bits of precision in the Intel FPU, *only if* optimizations are enabled, which causes certain iterative floating point algorithms (eg SVD) to fail to converge.

In both cases everything works great in debug builds but goes to hell in release builds and it's incredibly painful to get to root cause.

for sure the first site I'd attack is obscure registrar namecheap...

Some details here: http://en.wikipedia.org/wiki/P...

NCMEC uses PhotoDNA which is a fuzzy hash that can detect altered images.
http://en.wikipedia.org/wiki/P...

Yes, most likely GOOG is using the same thing everyone else uses- the NCMEC standard is PhotoDNA:
http://en.wikipedia.org/wiki/P...

+1000. The OP has embedded hardware skills which is a relatively rare skill-set- the barrier to entry is for sure a lot higher than basic software programming. My advice would be to leverage the hardware skillset into some new embedded programming domain (learn new hardware-specific tricks). There's little-to-no value in reinventing yourself as a generic programmer.