- Real World Active Learning — the point at which algorithms fail is precisely where there’s an opportunity to insert human judgment to actively improve the algorithm’s performance. An O’Reilly report with CrowdFlower.
- Hearing With Your Tongue (BoingBoing) — The tongue contains thousands of nerves, and the region of the brain that interprets touch sensations from the tongue is capable of decoding complicated information. “What we are trying to do is another form of sensory substitution,” Williams said.
- The Art of Management — cybernetics and management.
- kiwi.js — a mobile & desktop browser based HTML5 game framework. It uses CocoonJS for publishing to the AppStore.
Empathy, communication, and collaboration across organizational boundaries.
I might try to define DevOps as the movement that doesn’t want to be defined. Or as the movement that wants to evade the inevitable cargo-culting that goes with most technical movements. Or the non-movement that’s resisting becoming a movement. I’ve written enough about “what is DevOps” that I should probably be given an honorary doctorate in DevOps Studies.
Baron Schwartz (among others) thinks it’s high time to have a definition, and that only a definition will save DevOps from an identity crisis. Without a definition, it’s subject to the whims of individual interest groups, and ultimately might become a movement that’s defined by nothing more than the desire to “not be like them.” Dave Zwieback (among others) says that the lack of a definition is more of a blessing than a curse, because it “continues to be an open conversation about making our organizations better.” Both have good points. Is it possible to frame DevOps in a way that preserves the openness of the conversation, while giving it some definition? I think so.
DevOps started as an attempt to think long and hard about the realities of running a modern web site, a problem that has only gotten more difficult over the years. How do we build and maintain critical sites that are increasingly complex, have stringent requirements for performance and uptime, and support thousands or millions of users? How do we avoid the “throw it over the wall” mentality, in which an operations team gets the fallout of the development teams’ bugs? How do we involve developers in maintenance without compromising their ability to release new software?
How do we manage systems that are too large to understand, too complex to control, and that fail in unpredictable ways?
“What is surprising is not that there are so many accidents. It is that there are so few. The thing that amazes you is not that your system goes down sometimes, it’s that it is up at all.”—Richard Cook
In September 2007, Jean Bookout, 76, was driving her Toyota Camry down an unfamiliar road in Oklahoma, with her friend Barbara Schwarz seated next to her on the passenger side. Suddenly, the Camry began to accelerate on its own. Bookout tried hitting the brakes, applying the emergency brake, but the car continued to accelerate. The car eventually collided with an embankment, injuring Bookout and killing Schwarz. In a subsequent legal case, lawyers for Toyota pointed to the most common of culprits in these types of accidents: human error. “Sometimes people make mistakes while driving their cars,” one of the lawyers claimed. Bookout was older, the road was unfamiliar, these tragic things happen. Read more…
The Contract, Fixing Signin, Pi Gaming, and Glitchy Marketing Constructs
- The Unengageables (Dan Meyer) — They signed their “didactic contract” years and years ago. They signed it. Their math teachers signed it. The agreement says that the teacher comes into class, tells them what they’re going to learn, and shows them three examples of it. In return, the students take what their teacher showed them and reproduce it twenty times before leaving class. Then they go home with an assignment to reproduce it twenty more times. Then here you come, Ms. I-Just-Got-Back-From-A-Workshop, and you want to change the agreement? Yeah, you’ll hear from their attorney. Applies to management as much as to teaching.
- Fixing Signin — The general principle can be stated simply, in two parts: first, give users a trust-worthy way to identify themselves. Second, do so with as little information as possible, because users don’t want to (and simply can’t) remember things like passwords in a secure way. (via Tim Bray)
- Retro Gaming with Raspberry Pi (Adafruit) — finally, a clear incentive for kids to work through the frustration of setting up their own Linux box.
- Mieko Haire — Apple’s fictious demo lady. Or is she fictitious? This is a new aesthetic-esque glitch, but while most glitches are glitches because you see something that doesn’t exist, this is glitchy because the fictions are actual people. Ok, maybe I need to lay off the peyote.