818 karma · joined February 21, 2007
http://area51a.net/mds mds@area51a.net
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.
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.
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.
AREDN is basically trying to do what you want, within its limited coverage. You could install an AREDN mesh node in your car.
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."
Was that the origin, or was it in use before that?
So, thanks telnet!
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.
http://www.thedrive.com/news/22665/the-10-longest-kept-cars-...
https://www.ibm.com/watson/supply-chain/resources/csc/deskto...
One concrete example IBM likes to talk up is predicting shipping delays due to weather events and automatically recommending alternate suppliers.
You'd think they would consolidate administrative services like payroll under UCOP, but UCOP doesn't even do their own (they outsource it to UCLA).
Are there any technical IBM employees here who have been "forced" to relocate?
This post and all others I've seen are just rewrites of the original (unsourced) article last month in The Register (https://www.theregister.co.uk/2017/02/09/ibm_workfromhome_cu...) with no additional facts or updates.
I may be proven wrong, in which case I'll be looking for another job. But agreed, as far as I can see, at least regarding technical employees this is FUD.