IaC got people to understand at the idea that your infra code should be treated like your app code. Checked in to source control, deployed via COCD etc. Not defined by clicking buttons and stored in opaque databases somewhere.
"IaS" gets at the idea that it's a continuously running process. It's not a provisioning script you run once, there's a live reconciliation loop running in prod alongside your application code.
Also a big truckers hitch fan, but that animation was hard for me to follow because it doesn't look anything like how it's used in real life. It doesn't really make sense to compare to a bowline, it's basically used like a ratchet strap.
The first part, up to step 6, is just a slip knot. That part could be replaced by a bowline. But the slip knot can be thrown in one-handed in the middle of the line without needing to pull the end through like a bowline. And when you're done you give it a yank and the slip knot pops out.
Step 7 is the real point of the whole thing. You're using the loop and the hook (in this example) to create a pulley system to crank your load down tight. Then the rest of the steps are a hitch to keep it in place.
This is more secure than the version than I typically see used (and would be annoying to untie). I normally don't poke the end through like in step 9, but make another slip knot so the whole thing can be unravelled by pulling on the end of the line like a quick release.
In a rational environment if you're leaving "for cause", it shouldn't come as a shock to your employer when you quit, in the same way a bad performance review or firing shouldn't come as a shock to the employee. There should be feedback in both directions, if they're not meeting your career goals or you're not meeting their performance goals.
But as a rule I wouldn't tell my boss I'm actively interviewing until I have an offer in hand. Just like, and for a lot of the same reasons, the company as a rule isn't going to inform under-performing employees that they're actively looking to hire someone to replace them before firing them.
Reminds me of this Penn and Teller trick with a similar method but the opposite effect -- see https://www.youtube.com/watch?v=gnEGedfTrzc (skip to 2 minutes in). Freely think of any card, then miraculously reveal the card in an improbable location. It's "easy", just hide all 52 cards and memorize where they're hidden.
As far as I understand it this is the opposite of that. In other words it only works if you already have internet access. You can use it to talk over the internet with your radio from within your own home wifi.
AREDN is basically trying to do what you want, within its limited coverage. You could install an AREDN mesh node in your car.
I took a communication class many years ago and this was the main thing I took away from it. If you give a reason or an excuse the other person will try to help you "solve" it. If you give a simple "no, sorry" or "no, thanks" there's nothing for them to latch onto or argue with.
Realize that the other person is free to ask anything they want, but just the act of them asking doesn't create any obligation on your part. Especially with people where you don't have a longstanding relationship, you don't owe anyone anything more than a polite no.
The other piece I learned was this useful phrase to deploy when under severe pressure to give a reason and for whatever reason you can't just disengage or leave: "Sorry, I'm just not comfortable with that". No one can reasonably argue with that, and if they do, having already given your reason you can then simply fall back into a loop of "No, sorry."
The first time I remember hearing the phrase was in 2009 when Roberts flubbed the swearing in oath at Obama's inauguration. They later announced that the oath was administered again privately "out of an abundance of caution."
Was that the origin, or was it in use before that?
Oh man, I have the same memory. Back in ‘92 or ‘93, in addition to the “^]” telnet trick, our local dial up gopher could launch vi sessions for sending emails which they hadn’t thought to lock down to prevent it from executing “sh”. Poking around in those university systems was my first exposure to Unix and I’d say pretty directly influenced my career path.
Beorg is awesome, I use it daily, but it's really "TODO" oriented, and not that great for editing documents.
I've often wished there was an iOS text editor that understood org format, even just basic markdown style formatting. I'm going to give org-web a go, I think it could be a good compliment to beorg.