AngeloR
Joined 15 years ago
Joined 15 years ago
This video of execs at Patreon apparently turning a blind eye to employees calling out patreon users that were selling images of underage children: https://twitter.com/TizzyEnt/status/1315626557688483841?s=20...
They also laid off their ENTIRE security team: https://techcrunch.com/2022/09/09/patreon-security-layoffs/
Imagine you fell for a ponzi scheme. Now imagine you knew where the person who ran that ponzi scheme was.
The remark is a bit flippant (and feels grammatically incorrect) but the sentiment remains.
Lots of people view crypto as a get-rick-quick scheme on both sides. Even after warnings of "don't put any money in that you aren't comfortable losing" people put in money that they aren't comfortable losing. Coupled with the fact that most of these crypto projects maintain very high levels of community involvement (normally through discord/twitter). Sometimes when people lose a lot of money they lash out at the systems they lost money through. So they turn on the devs of whatever chain/token they gambled on.
p possesses maximum "descent" for a character (the bit below the baseline on a font).
É not only meets the traditional "ascent" but exceeds it since diacritics normally extend past the traditional ascent on a capitalized letter.
These aren't the only characters that possess these values (although, I assume some selected code points are unique), but just ones that do.
It's important to note it's not just this one thing that can do it, but there's a collection of things that can get you labeled as a PSB.
I think the foundation of the pyramid (API and Implementation semantics) is often discussed in code reviews when it should have almost no place. By the time you get to the code review not only should these have been ironed out and shared with the whole team. What you should be looking at is simply adherence to the plan, and calling out deviations.
I wrote about a small rat about this: https://xangelo.ca/posts/code-reviews-are-failure/
I'm not affiliated with this project at all - I just really love it.
[1] https://www.ilograph.com/ [2] https://blog.ilograph.com/posts/fixing-aws-architecture-diag...
/ # nginx -V
nginx version: nginx/1.17.10
built by gcc 9.2.0 (Alpine 9.2.0)
built with OpenSSL 1.1.1d 10 Sep 2019
If your indeed job posts didn't bring diverse candidates then, why do you think it would now? Because you added a "Please apply if you're DiVeRsE" line to it? Don't be ridiculous.
If you want diversity of candidates you can't keep going back to the same talent pools. You have to diversify where you're drawing talent.
If your college program is primarily getting white/asian males, you can't suddenly expect it to start throwing in women & poc as well. You can't suddenly expect it to start giving you LGBTQ+ candidates.
If you want diverse candidates, you have to look at diverse hiring pools. Look at the bootcamps that focus on diverse groups you're targeting. Look at schools that focus on diverse groups you're targeting.
If you're really interested in diverse candidates, you can't keep expecting them to just show up if you add a "We want diversity!" to your job description - you have to change where you look for them.