jasonj79

Neat idea, but defaulting to recursive force mode (-rf) is frankly a bit scary (and irresponsible). A great way to accidentally shoot your own foot off after you've put it through a meat grinder.

I pity the fool that tries to use this programmatically with a unset or null var, eg.

  skrub /$imfucked

Sounds like sour grapes, not discrimination...

I moved coast to coast to work for a SV technology company (fully paid), did NOT graduate from a fancy college (or any for that matter), have my nights and weekends free, and see the struggle daily that is the fight to find qualified talent... Truth is that tech companies are having an extremely hard time filling seats, and they frankly can't afford to discriminate on anything other than lack of skill necessary or extreme culture mismatch.

The only thing I agree with in this article is that yes, 3 times is a pattern... a pattern that they don't want to hire him. Maybe he should figure out why that is before blindly blaming it on race.

Having been a hiring manager for a few years... I can say that degrees have only really mattered to me when the applicant hasn't any real experience to speak of in the industry.

Experience is king, plain and simple.

That said, the best post-experience education I've received is self study in algorithms... If you haven't had the exposure from your time achieving your EE degree, do yourself a favor and hit up Kahn Academy or Coursera (or others) for a course, you won't regret it.

Lastly, build yourself a strong LinkedIn profile if you haven't already, as my best leads have come from there almost exclusively.

I wondered the same, but I'm not sure that doubling my password would annoy me into changing it, especially when the password was previously capped at 8 characters.

makes sense... hopefully this is their reason instead of the former.

A better way to do this would have been:

* hash current passwords with a salt, unique to each password entry, and throw away the plaintext entries.

* keep a history of hashes per user, to prevent changing to a past password

* ensure fair complexity of the incoming password

* once the deadline has been reached, force users who have not yet changed their password to do a password reset via an online form

* never, ever again think that doubling a password is a proper way to fix a security issue, ever...

I't because they are still storing passwords in cleartext... If they were hashing passwords (which is the correct way to do it) there would be no limit.