506 karma · joined January 19, 2011
Prof. Nancy Leveson of MIT has done extensive research over the last forty years on the safety engineering of complex systems, and her 2012 book _Engineering a Safer World_[0] (open-access PDF at that link) is partly a response to Perrow's _Normal Accidents_.
[0]: https://mitpress.mit.edu/books/engineering-safer-world
In particular, and unlike Perrow, she thinks we really can design complex sociotechnical systems which aren't disasters waiting to happen, and her book provides a theoretical framework for doing so, plus a fully-worked design analysis technique and accident investigation technique using that framework. These have been and are being used under real-world conditions in a variety of industries including transportation, the military, and even software.
There's a conference every year at MIT which I've been going to every year for about four years now where folks present. Every year there are more industries and disciplines represented, and there have also been presentations of analysis techniques applying the theoretical framework in practical contexts like cybersecurity and privacy.
You're also very right that there are huge social and human factors components to safety, and her book talks a lot about getting that right and analyzing what went wrong at various levels of abstraction, including cultural and regulatory. I highly recommend it, if you're interested in this subject.
Based on what I know of the US Navy, I'm certain that the accident investigators working on this collision are doing so informed by this methodology.
"I'm going to invest 10 billion in startups but you have to relocate" is basically what Tony Hsieh did in Las Vegas, and it... based on how rocky that got, I think it's about more than just access to capital.
Open source funding is a cause near and dear to my heart, and I hope something is able to work out.
(And thanks!)
(Disclaimer: I work for Stripe, as of like last week. :)
I think changes which lead to positive progress are hard, and the bigger the problem or the higher up Meadows's leverage list, the harder the changes are. Cognitive dissonance and sunk cost thinking and other cognitive biases do increase the challenge as well. But I do see examples where I and others were able to make positive changes from our understanding of systems theory. I see making these changes as a marathon, not a sprint, so try to adopt an attitude of celebrating every step of the way ("dayenu"), and I also look to work like Nancy Leveson's[0], which tries to systematize the process of turning a systems understanding into actionable feedback.
It's often perceived to be the case that earlier interventions would have led to fewer losses, but it's important to adopt an understanding that the past is past, and all we can do to move forward is to change our behavior now. As the man says, the best time to plant a tree is twenty years ago, but the second-best time is today.
Around the university, the supermarket drew primarily from the adjacent neighborhoods, and got a lot of college students and local residents who were shopping on average weekly, so we quickly got skilled at using the machines. In the residential suburb, the supermarket draws from a much larger area, and there are more customers who shop there infrequently, so they never get skilled at using the machines. Even just as a skilled user, not as a professional checker, I would regularly stand in line behind people where I knew that I could have shaved minutes off their time merely if I had checked them out.
A lot of the skill involved was just in general operation: how to find barcodes, how to scan items reliably, how to identify produce and enter it correctly, how to use coupons, how to flag down help if the machine entered an unexpected state or required human assistance, how to use the payment terminal with cash, credit, and debit, how to bag items correctly and so that the machine would recognize them, what the various prompts mean and how to respond to them. There's a lot of complexity in operations which we denigrate as "unskilled" or "menial labor" which is only evident when you take the time to observe closely and see what people are actually doing in them.
Slaves are capital, and, like all capital, acquiring and maintaining them has nonzero cost.
In the antebellum American South, some tasks like ditch-digging were sufficiently hazardous that a plantation owner would rather not risk their investment in their slaves, and so would hire Irish ditch-diggers by the day, as the plantation owner would be out less money if they died while digging the ditch.
On the contrary, my local grocery store took out their self-serve checkout kiosks and replaced them with human checkers. Turns out there was some skill involved after all.
> ro·bot (n.) 1923, from English translation of 1920 play "R.U.R." ("Rossum's Universal Robots"), by Karel Capek (1890-1938), from Czech robotnik "forced worker," from robota "forced labor, compulsory service, drudgery," from robotiti "to work, drudge," from an Old Czech source akin to Old Church Slavonic rabota "servitude," from rabu "slave," from Old Slavic orbu-, from PIE orbh- "pass from one status to another" (see orphan).
http://www.etymonline.com/index.php?term=robot
All that's old is new again.
The people who never knew him, and who don't know MIT or MIT culture, and who want to turn Aaron into some kind of Internet freedom martyr all out of proportion to who he was and what he actually accomplished, those are the folks who I have a beef with.
Do I think he should have been rung up on federal charges? No. But he wasn't a student, or a teacher, or a visiting researcher, or an alum. He had no official affiliation to MIT, and he showed no understanding of or respect for our culture. The flip side of an open culture is respect for and maintenance of the commons, and instead he exploited ours. It was really hard to defend him at the time for abusing the openness of the MIT community.
(And now, in fact, MIT affiliates like Aaron and me no longer have access to MIT's institutional subscriptions, in what I can only assume is partly a response to his actions.)
MIT's history has no shortage of people who were part of the institution and part of the culture, who the administration failed to support when that support was more justified and more needed than it ever was in Aaron's case. I'm sorry for the outcome, and I don't think he deserved it, but I don't think he deserves either some kind of posthumous award, nor does MIT deserve the scorn heaped on it by those who would canonize him.
A bit like if your friend comes to your house, you tell him, "don't smoke weed outside, the cops around here will arrest you," and your friend says "I support marijuana legalization, so I'll smoke wherever I want." Your friend smokes up on your front steps, you try to get him to stop (it's your house after all), and then the cops show up, rough you up a bit, and arrest him.
There are many more deserving than Aaron Swartz of this award, within and without the MIT community.
A 401k is also supposed to be able to provide you with an income resembling your at-retirement income for at least 10 years, which is obviously impossible if you only have 2.5x your at-retirement salary in it.
It's very easy for assholes to 'hide' their assholishness if the people with power aren't looking for it, and won't listen to the people who see it. However, even people like that are now on notice that Uber employees are tainted.
(My housemate who's a middle school history teacher and I were mutually horrified last night at our respective interview experiences. He was hired to teach eighth grade after a single 45 minute Skype interview. I had just had a half-hour phone screen followed a week later by a two hour in-person interview, and I considered that quite short by my standards. I thought his process was ridiculously short; he thought mine was absurdly long.)
Also, and I say this as someone currently going through the process: given the way hiring for senior to C-level roles goes in 2017, do not expect "several months" of savings alone will be enough to cover you. Most of the large companies you might like to work for (Google, Microsoft) have hiring processes which can't move much faster than six weeks, and they can stretch out to six months or more.
I have friends whose RSI is sufficiently bad that it could be an issue.
If this is true of the people around you, then you know folks who are very, very lucky in their life and work.
(This is a serious question. It describes a lot of the security incident response work I've hired for.)
"Hey Carol, can you send me the link you're using to the wiki? Mine isn't working."
This is not really obvious from any of your marketing copy or documentation, nor would it be a realistic expectation if it were. I think you need to secure like your users don't know or understand your intentions.