Ex-cons have a shitty past. White supremacists are currently and actively shitty.
3,334 karma · joined February 10, 2009
Ex-cons have a shitty past. White supremacists are currently and actively shitty.
Glossing over this fact in order to safely hate other people is what makes them shit people.
They will just give the same bullshit answer as always. Sometimes throw in a new phrase ("24/7 guarded datacenter") to pretend they are not vulnerable to obvious risks.
I call strawman.
Both article and researcher make no claims further than "cultural influence".
The rest is that "point free" describes a programming paradigm, while terms you listed describe the mechanisms you can use to apply it.
A new software is just another thing they'll turn off, not enter data into, or bypass for convenience.
You need to code them a new culture.
Bad comparison. Breaking into a car is a locally constrained high-risk attack vector.
This is a low-risk unconstrained attack vector. A bored person anywhere in the world could fuck their shit up with no risk or consequence.
#!/bin/cat
1
2
fizz
4
buzz
6
… 98
fizz
buzzIf you did, you'd have found a way for it to work.
Making a pretty cool deploy script? Document it and put it out there as OSS.
Making a class/module to sort items semantically? Make it OSS.
Someone made an IDE extension to syntax highlight WebVTT files? Make i OSS.
Made a file lister/selector for JQuery? OSS.
Integrating 3rd party X with 3rd party Y? Opensource your module for it.
Unless all your developers do is hack stuff badly together in a monolithic mess, some of it can be opensourced.
Anyone can cook up a coin by forking Bitcoin or Litecoin and do a search-and-replace on the name in the code and nothing else.
Why? You have Google at your fingertips.
If you don't have "strong" - i.e. skilled and disciplined - people, or you can't allow things to happen outside "just because ok?"-rules, it's flaccid agile.
Like jelly in a glove, it's flexible but not in a useful way.
1. Jet fuel
2. Sugar
3. Plastics
4. Space Rockets
5. The gays
I've had days where I've ended up doing literally nothing, but still objectively outperform some colleagues because they rammed some shitty unstable undocumented race-condition hack into the codebase.
One of your teams write messy code? Don't try to educate them. Instead enforce strict coding standards that forbid all but the most basic complexity. Everyone else now have to make their code more verbose and objectively worse, while the problem team still writes bad code but now they make even more of it in a neater formatting.
2) Raise wages only for people who threaten to leave.
3) Run a high tech software development shop but have an IT department that assumes everyone only ever need Excel and Outlook.
Ports are blocked. Local computer admin is locked. Updates are forced, delayed and centralized. Hardware is underpowered. Network blocks ping.
4) Demand to be in full control.
Make sure nobody does anything you don't understand. Shoot down experiments you can't see the point of, even if they're small. Hire skilled and experienced people, but demand that you can understand everything they do.
5) Let random people deal with hiring and interviews.
Hiring is both a hard and sensitive process. On one hand you are giving people an impression of your workplace, and on the other hand you are trying to evaluate the skill of someone who has a different skill set than yourself.
Giving this job to some burnt out elitist asshole who throws resumes in the garbage because they did or didn't include a cover letter, or a wannabe drill sergeant who tries to be "tough" and "test them under pressure" during interviews, gives you a bad rep in tech circles and doesn't help you hire skilled people. Giving it to someone who can't be bothered to reply to applicants or update them on rejections is also shitty.
6) Open fucking landscape workplaces.
Fuck.
Being anti-nazi is "radical leftist" now?
Disregarding how you both feel about it, waving a nazi flag legitimizes and strengthens an inherently violent ideology of ethnic cleansing.
Intent - real or pretend - doesn't matter.
The guy on the street outside wears thick waterproof pants and thick waterproof rubber boots when he cleans the street with a pressurized water hose.
Water is generally considered safe [citation needed], but you still don't want to get hosed in it for hours on a daily basis.
- Constantly wet feet catch fungus and foot rot.
- Water lowers your body temperature, making you more susceptible to infection from and outbreak of common cold.
- Containing water contamination to an surface - instead of your clothes and skin - makes it easier to rid yourself of surplus water when taking a break.
- Wet clothes are highly impractical because they are heavy and shed water everywhere you go for hours after.
TLDR; Protective clothing doesn't imply toxicity.