Kevlin Henney does not make recommendations for architecting software but rather brings into discussion five considerations useful to be reflected upon: economy, visibility, spacing, symmetry, emergence.
Kevlin Henney is an independent consultant and trainer based in Bristol, UK. He has developed and delivered training courses, consultancy and software across a number of domains. He is coauthor of two volumes in the Pattern-Oriented Software Architecture series, A Pattern Language for Distributed Computing and On Patterns and Pattern Languages.
QCon is a conference that is organized by the community, for the community.The result is a high quality conference experience where a tremendous amount of attention and investment has gone into having the best content on the most important topics presented by the leaders in our community. QCon is designed with the technical depth and enterprise focus of interest to technical team leads, architects, and project managers.
Factory and Junkyard are not the same.
Re: Factory and Junkyard are not the same.
There is a subtle shift in metaphor from ownership (manufacture, own and discard) to one of borrowing (borrow, use and return), a more resource-centred view of object lifecycles, both low-level resources and domain objects that have structured lifecycles with well-defined retirement/completion events.
When it comes to addressing where the disposal role should go, there are of course two existing locations that could serve: the product and the producer. The one discussed in the talk is that of the producer, i.e., a factory disposal method. The alternative that you mention, i.e., self-disposal method, is not discussed in the talk, but is an equally valid consideration (just not the one explored in the talk). My VikingPLoP 2003 paper, "Factory and Disposal Methods" (is.gd/5gKf0) discusses both variants.
Returning to the real world we may also consider that the responsibility for disposing of the Accord should lie with the original manufacturer. Just because it doesn't at the moment, does not mean that the status quo represents the most appropriate solution!
I hope that answers your question.