5,084 karma · joined August 1, 2011
[ my public key: https://keybase.io/jwildeboer; my proof: https://keybase.io/jwildeboer/sigs/H6tm14xTFzYSXNWDml-Oo5AFXHpL9tQp2nZJF4wBBY0 ]
$argon2id$v=19$m=512,t=256,p=1$MpTGuneSB8SZATwS8muyTg$ENTNP76aTiadBOdYxHcyhokF1gx/pCOOgjQj7Pn22G4
And even if you don’t need them all, by training them you give them a better chance when finding new jobs. A small investment can go a long way. Also helps your companies reputation when people don’t simply get removed.
I honestly don’t care about the rationale, but this inconsistent behaviour is simply wrong. After 18 years of discussion, end this. Whenever DECRYPTION_FAIL occurs, there MUST be no decrypted content.
The person complaining did try. Made his iPhone a hot spot, put it in the car and left it there for days. But the update wasn’t triggered.
Founded by realistic visionaries (Bob Young and Mark Ewing). Bob was smart enough to bring in Matthew Szulik, who gave Red Hat structure and growth. And Matthew was smart enough to hand over to Jim Whitehurst.
Red Hat is nowadays a smooth running company with 64 quarters of growth, with a portfolio that goes far beyond Linux.
Execution is key. Having passionate employees a must.
Disclaimer: I'm a Red Hatter
[1] http://stackalytics.com/?metric=commits&project_type=kuberne...
Put it in the footer or the "About me" page, add a license blurb to all your entries in a blog etc. It's just a bit of one-time work but it helps a lot in building reputation.
Also none of the pictures have any kind of license or copyright info. I cannot even see from the article at [2] that he took the pictures himself.
In conclusion my opinion is yes, the designer should have asked for permission. But also the author should add copyright/license info to his site and make that info easy to discover.
I'm sure Netflix will do the right thing and we all live happy ever after :-)
[1] http://goughlui.com/about-me-a-short-bio/contact-me/ [2] http://goughlui.com/the-vhs-corner/intro-inside-the-vhs-cass...
“Reviewing and testing consensus changes is really, really hard. [...] Essentially, even one or two weak reviews in a chain of reviews can break the entire consensus system with a catastrophic bug.”
https://www.slideshare.net/NadiaEghbal/consider-the-maintain...
How many projects? How are they rated "top"? When you make such a bold claim, you should be able to back it up with verifiable sources IMHO.
Also, being a Red Hatter that has welcomed thousands of people in our New Hire Orientations, I dare say that we actually do employ quite some developers that continue their good work in a lot of communities. Describing that as "the 1% approach" feels a bit wrong.