On May 9th, 17:00 PM at Main
I will give a talk about the idea of Software Craftsmanship: What does this fuzzy term actually mean, how is it different from how we work today, and does being a software craftsman keep you your job?
I want to combine insight from current Agile software development methodologies, books and essays that touch the subject of Software Craftsmanship my own experience, and take look over the fence at the classic crafts.
This is not a Ruby-specific talk, but I believe it fits the conference very well. Ruby developers generally are passionate about their work and eager to learn, two of the traits of good craftsmen.
"A craftsman is someone who applies skill and care to the creation of a high quality end product." -- Jason Gorman
This is a noble goal that most of us are aiming for. But despite decades of practise and research, we still fail often: unmaintainable applications have to be rewritten from scratch, schedules slip, budgets are overdrawn, developers and customers are unhappy. Success is the exception, not the rule. Software craftsmen possess a blend of technical and social skills as well as the experience to fix this. But what exactly makes a craftsman and how do you become one?
Rate of this talk
(32 votes so far)