These two things crossed my transom at the same time. They're both good and feel connected.
Richard eloquently points out the big issue for the next 20 years - software is politics now. This bit stuck out for me:
"I think the accountability model for a service needs to be an intrinsic part of the design of that service. Accountability needs to be embraced as part of the service design rather than abstracted away."
And Nick Foster (East Midlands represent!) stuck up his talk from dConstruct wherein he stresses the importance of designing for broken-ness, of realising the thing you're making won't always work and that it needs to acknowledge that.
The Future Mundane from hellofosta on Vimeo.
These seem related points to me. One failure mode is 'I have run out of paper', another is 'my data has been sold to a company I don't trust', another is 'my country has been invaded and they've seized all the servers'.
These are things to be designed for. These are user needs too. They have to be embraced.