Atributed to Alberto Brandolini: - "software engineering can be thought of as a learning process with working code being a side-effect", attributed to Alberto Brandolini Some related thoughts: - to minimize waste, one needs to maximize learning - it's ok to dump stuff, if one learns. for example, to rewrite a part of the system if the understanding evolved to better fit the business case (and value) - when unexpected things pop up (especially right before the demo or sth), it is the learning that has occurred. - "scope doesn't creep, understanding does", by Jeff Patton (I think) - domain learning seems to happen best collaborative; so optimize learning for collaboration - failures = learning, so there are conceptually no failures - openmindedness implies more learning, so openmindedness fits into the learning metaphor -