Oh See Paren Left Brace Whatmark
For loads of alternatives, see the Jargon File
Oh See Paren Left Brace Whatmark
For loads of alternatives, see the Jargon File
Gonna have to disagree with #3 - stopping Vim is not necessary for this. There’s the builtin :!
command.
Don’t forget /auto, for things that get automatically mounted when you first access them (autofs)
Yes, it’s legal in much of the US. Many states require a permit for concealed carry, but not for open carry. WalMart has signs at the front of the store “requesting” people not to open carry, but apparently not prohibiting it.
Slow down there - you’re making some rather large assumptions about why they have guns. Sure, some people have guns for “self defense” (some for valid reasons, others because racism). Others have them for hunting. Sometimes they’re inherited and have sentimental value.
Edit: Also, kids aren’t the only reason not to keep them loaded. Keeping guns and ammo separately secured introduces enough of a delay to reduce the risk of suicide, for example.
Pornography is
close tofull sex work
FTFY
That would be true for competent web developers. Unfortunately, those are a vanishingly small subset.
That is not accurate.
Nah. This has happened with every major corporate antivirus product. Multiple times. And the top IT people advising on purchasing decisions know this.
Favorite would be a highly customized zsh.
fizsh (not fish) is what I actually end up using, as I can’t be bothered to copy that config around and retune it for each machine. Gives me the syntactic sugar of zsh with common default options on by default, an OK default prompt, and doesn’t break POSIX assumptions like fish. Also Installs quickly from the package manager without needing to run through the zsh setup each time - unlike oh-my-zsh. And if I still need customization, all the zsh options are still there.
And that assumes no second hand
Exactly.
Notify the maintainer of the open source tool - they’re in the best position to push for compliance. They have the power to revoke the company’s license.
Having known multiple trans people and heard them talk about the arguments for and against early disclosure: Fear.
They may not be public about their status, and fear exposure to family or coworkers seeing their public profile.
They may fear harassment from transphobes. This could range from DM accusations of pedophilia to religious screeds to doxxing to death threats.
They may be trying to avoid “chasers.” There are some people for whom a trans body (particularly a transfem body) is a fetish, who don’t actually care about the person inside. Plenty of transpeople don’t appreciate that kind of attention.
Fear of rejection. They may believe that nobody will respond if they’re open about not being cis.
Also two less fear-related (and less common) possibilities:
Ideology. To some people, specifying “transman” or “transwoman” reinforces a social distinction they find invalidating or don’t accept. How many profiles have you seen that specify themselves as “cisman” or “ciswoman”? For these people, it’s a way of rejecting cisgender normativity.
Maybe they just aren’t ready to talk about their genitals yet, or have their first conversation be about their surgical plans or history. Not only can get really repetitive having that be the first conversation with every single match, it means they don’t get any of the information they’re looking for about a potential partner until much later in the process and have to invest a lot of their own time up front. Just like you want the salient information you care about early on, so do they.
Something I haven’t seen mentioned yet - who is the company’s HIPAA “Compliance Officer”? If it’s anyone other than your boss, you could document the situation to them in an e-mail. If you want to be slick about it, ask them if there is “still any compliance need to keep the replacement machine ready or if it would be OK to repurpose it, given [your boss’s name here]'s decision not to move forward with the upgrade.” They’re on the hook for compliance violations, so they’ll likely see to it.
I would also suggest making a habit from now on of documenting verbal conversations that result in actionable decisions in short e-mails to the other party: " To recap our discussion, [bullet point list]"
You can excuse this as being for your own reference so you don’t forget any to-do items or so that they can correct any misunderstanding on your part, but it makes for a fantastic CYA if that ever becomes necessary. For really important items likely to bite someone later, print a paper copy if you don’t fully own and control the machine AND the e-mail local archive. Only bring those out if absolutely necessary, as in when SOMEBODY will be fired or you’re about to be legally scapegoated. They’ll save your butt once, but it will probably be time to start looking for another job because the boss will think either that you should have pushed harder earlier to fix the issue or be worried about their inability to scapegoat you in the future.
The last time it went to the Supreme Court, they couldn’t make up their minds. The current court would probably support it.
Probably because of this. The commenter overstated the situation, but there are valid and serious criticisms to be made.
The most encouraging thing in the whole talk for me was when he told a roomful of IT folks that they need to join or form Unions and they cheered.