deleted by creator
deleted by creator
Vested interest? Literally vested stock options. Well, by now they’ve already been used to purchase stock.
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)
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.
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.
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.
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.
To be even more explicit on the last point, that means regularly updating OpenWRT and all your containers, not just the server’s base OS