Issue #358

tl;dr: "Games industry veteran rattles off a sample of 50 things he expects of developers he works with:" (1) Can articulate precisely the problem trying to be solved. (2) Someone else can articulate the problem trying to be solved. (3) Can articulate why the problem is important to solve. (4) Can articulate how much my problem is worth solving. (5) Have a Plan B in case the solution to my current problem doesn’t work. And More. 

tl;dr: "A few long-tenured engineers, who happen to have the explicit access credentials to all key systems and implicit permission to use them, help respond to almost all incidents. These folks become increasingly load bearing, as few others acquire the knowledge, and access credentials, to respond when they’re not available. Fast forward to the future, and one of these key responders leaves the companies, which creates more load on the remaining responders." Will discusses how to solve this. 

tl;dr: "I had two problems it could solve: low side project motivation, and loving dark chocolate sea salt almonds way too much. I'm a codemonkey - Why not feed my monkey brain when I push code? I couldn't find a USB candy dispenser, so I figured I'd try a cat feeder. This thing rocks, and I'll show you how to replicate what I did."