|
|
|
<<< Previous speaker
|
next speaker >>>
|
Dan North, Agile troublemaker, developer, originator of BDD
Dan writes software and coaches teams in agile and lean methods. He believes in putting people first and writing simple, pragmatic software. He believes that most problems that teams face are about communication, and all the others are too. This is why he puts so much emphasis on "getting the words right", and why he is so passionate about behaviour-driven development, communication and how people learn. He has been working in the IT industry since he graduated in 1991, and he occasionally blogs at dannorth.net.
|
Presentation: "Sharpening the Tools"
Time:
Wednesday 10:30 - 11:30
Location:
St. James's Suite
Abstract: We start out as software novices with an empty toolbox and lots of good intentions. Over the years we collect all sorts of odd tools and techniques. Some are general purpose, some very specific; some are necessarily short-lived, others can last a lifetime. One of the skills of a software craftsman is keeping this toolbox in good condition, so the tools are always easy to find and in good working order. Removing clutter and updating tools is as important as keeping the long-lived tools in good working order. And owning a box of state-of-the-art tools is useless if you are not keeping yourself up-to-date in using them.
In this talk Dan confesses that he'd let his toolbox fall into disarray and tells you what he's doing about it. Come along and learn some strategies for discovering, selecting and maintaining the tools and techniques that will serve you as a software craftsman.
Keywords: Tools, techniques, craftsman, experience, kata, learning, alternatives
Target Audience: Developers of all levels - apprentices, intermediate, master practitioners
Presentation: "Introduction: Irresponsible Architectures and Unusal Architects"
Time:
Thursday 10:20 - 10:30
Location:
St. James's Suite
Presentation: "Simplicity - the way of the unusual architect"
Time:
Thursday 13:45 - 14:45
Location:
St. James's Suite
Abstract: It is often said that the difference between architecture and design is one of scale. Architects are concerned with "big" design and "big" integration. As developers become architects and architects become enterprise architects, the systems they design become ever bigger and more complex. But does big necessarily need to mean complicated?
In this talk Dan argues for a new appreciation of simplicity, using examples from systems analysis, enterprise integration, build and deployment, and provides strategies to help you extract the simple essence from complex situations and problems, and to distinguish the simple from the simplistic.
"I would not give a fig for the simplicity this side of complexity, but I would give my life for the simplicity on the other side of complexity." - Oliver Wendell Holmes
Keywords: simple, simplicity, alternatives, complexity, risk, essence, thinking tools, de Bono, NLP
Target Audience: Architects who think there must be more to life than UML and SOA, and that ESBs, portal servers and even J2EE might have been a massive fraud...
|
 |
| |
