Just a reminder—over at the Never Work in Theory blog, we’ve already got about a couple dozen papers with empirical findings that (we think) are relevant for software practice. They’re beginning to cover a wide area: from parallel programming to teamwork dynamics to requirements prioritization to organizational structure. If you think of good and interesting papers that we haven’t discussed yet, drop me a note!
- RT @avibryant: 10 years ago I would have wholly disagreed with this. It’s probably 10 years before I wholly agree. But read it now: http://… 18 hours ago
- RT @jessitron: "The challenge of the experienced developer is to pass on wisdom without passing on dogma." @jergason jamisondance.com/03-29-2015/cyn… 19 hours ago
- RT @ciphergoth: Dunning-Kruger isn't what you think it is danluu.com/dunning-kruger/ also other mistakes, some of which I've propagated. 19 hours ago
- RT @nickstenning: The women and men who wrote the nearly bug-free code that controlled a $4Bn space shuttle and the lives of astronauts wor… 4 days ago
- RT @tinyrevolution: It's rare you get this kind of glimpse at the banal face of deep, true corporate evil: firstlook.org/theintercept/2… 1 week ago