Mike Lee considers that a software engineer makes great applications not because he follows good rules but because he has a better way of looking at the world and he learns from experience.
Russ Miles discusses how to nurture the skill of learning by understanding it, valuing it and enhancing it in order to achieve an agile transformation within the organization.
Robert Myers talks about the role played by failure in Agile development, sharing a number of Lean and Agile practices helping to embrace failure and showing how to interpret the feedback received.
Dan North considers that ignorance is the major roadblock on the way to success, presenting strategies and techniques for reducing it, delivering software in a more deterministic and less riskier way.
Kenneth O. Stanley considers that innovation is stifled when we are strictly following a high goal, and we would progress more when we are inclined to discovery rather than following an objective.
Dan North argues that Agile best practices can help an organization only to a point, and continuing to rigidly apply them after that will stifle innovation and drive people away. Organizations need to continue to innovate, finding new ways and practices to develop software by looking at the motivations behind Agile practices and not just implementing them.
Amr Elssamadisy focuses on the individual and his responsibility to do his best to make things work in the team regarding the learning process, communication, dealing with upsets, ownership, and responsibility.
Dan North advices programmers on how to advance from beginner to expert: practice the basics, learn from others, understand trends, share knowledge, maintain the toolbox, learn how to learn, and start all over again.
Pete Goodliffe provokes his listeners to keep learning over the course of their entire life, offering advice on how to approach learning, what is valuable and what can be ignored, how to deal with new things, having a healthy attitude towards learning, and how to feed one’s curiosity.