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 @SMEasterbrook: Me in @NatureGeosci: Open code policies won't increase code sharing much, but they will make us clean up our code http:/… 6 hours ago
- RT @DeanFortin: One day left to submit feedback to the city's Kinder-Morgan survey! Don't forget to have your say: haveyoursayvictoria.com/projects/propo… #… 16 hours ago
- RT @mhoye: wheretheresmuck.wordpress.com/2014/10/16/how… <-- I have to admit, crashing Schmidt's party and asking him to sign his own book Assange takes some gut… 2 days ago
- RT @jamesbow: Toronto's results suggest that Ford Nation stayed constant. Increased turnout turned the election against him. #topoli 3 days ago
- RT @AndrewMitrovica: The Harperites looked 4 a pretext 2 do this, they got it from a homeless, crack addled man with mental health issues: … 5 days ago