The Software Craftsman (2nd edition)
Upcoming SlideShare
Loading in...5
×
 

The Software Craftsman (2nd edition)

on

  • 2,734 views

The Software Craftsman (2nd edition)

The Software Craftsman (2nd edition)

Statistics

Views

Total Views
2,734
Views on SlideShare
2,711
Embed Views
23

Actions

Likes
1
Downloads
52
Comments
0

4 Embeds 23

http://calebesantos.wordpress.com 15
http://www.slideshare.net 5
http://www.linkedin.com 2
https://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    The Software Craftsman (2nd edition) The Software Craftsman (2nd edition) Presentation Transcript

    • The Software Craftsman Gøran HansenAspiring Software Craftsman @ Capgemini
      http://blog.goeran.no
      @goeran
      mail@goeran.no
    • Outline
      Why do we need Software Craftsmen?
      The Software Craftsman persona
      How to become a Software Craftsman
    • Why do we need Software Craftsmen?
    • Have you ever been slowed down by bad code?
      - Robert C. Martin aka. Unclebob
    • “The best processes in the world will not save a project from failure if the people involved do not have the necessary skills to execute the process; conversely, really good developers can make any process work”
      – Pete McBreen, Software Craftsmanship: The New Imperative
    • Bad code amplifies the risk of project failure
      – even for agile projects!
    • We need Software Craftsmen because they don’t write bad code…
    • When do we write bad code?
    • Pressure
    • When we have to “Get It Done”!
    • ”Get It Done”
      vs.
      ”Get It Right”
    • Skill deficiency
    • A Software Craftsman will choose “Get It Right” (and get it done)!
    • Because he has the skills to do so…
    • The Software Craftsman persona
      The Software Craftsman persona
    • A Software Craftsman will always “Do It Right” – also under pressure
    • A Software Craftsman takes responsibility
    • A Software Craftsman takes pride in his work. Both the end product and the process towards it
    • A Software Craftsman signs his work
    • “Software Craftsmanship is all about putting responsibility and pride back into the software development process. As Hunt and Thomas (The Pragmatic Programmer) state, we need to start ‘signing our work’ again, just as other craftsmen do”
      – Pete McBreen, Software Craftsmanship: The New Imperative
    • A Software Craftsman is a continuous learner. When he doesn’t work, he spends his time studying, to find new methods and tools can refine him as a Software Craftsman
    • “An investment in knowledge always pays the best interest”
      - Benjamin Franklin
    • A Software Craftsman practice deliberately, and understands the difference between practice and work. He practices in order to be prepared for work
    • A Software Craftsman writes code
    • “Knowledge is not the same as having the skills and practical ability to create software”
      – Pete McBreen, Software Craftsmanship: The New Imperative
    • A Software Craftsman has the right attitude towards Software Development
    • A Software Craftsman contribute to the community
    • Characterization of a Software Craftsman
      Will “Do It Right”
      Take responsibility
      Take pride in his work
      Signs his work
      Continuous learner
      Practice deliberately
      Write code
      The right attitude
      Contribute to the community
    • A Software Craftsman don’t write bad code because he hones his skills
    • How to become a Software Craftsman?
    • Tips from The Pragmatic Programmer:
      Care about your craft
      Think about your work
    • Start learning
    • What should I learn?
      TDD – can be applied to all languages
      Functional, dynamic and statically typed languages – learn the different paradigms
      Refactoring – learn how to change your code efficiently
      Design patterns
      Tools (ReSharper, Visual Studio, Ndepend, Pex etc)
      Frameworks (Nhibernate, Mongo db etc)
    • Start training!
      Code Dojos
      Code Katas
      Pair programming with other fellow Craftsmen
    • Practice – work on a real project
    • We need Software Craftsmen because they don’t write bad code
    • A Software Craftsman don’t write bad code because he hones his skills
    • And you can become a Software Craftsman by honing your skills (study, training and practice)
    • A special thanks to
      Corey Haines, for letting me using his slides.
      http://www.slideshare.net/openagile/the-craftsman-developer-in-an-agile-world
      http://www.coreyhaines.com
    • The Software Craftsman Gøran HansenAspiring Software Craftsman @ Capgemini
      http://blog.goeran.no
      @goeran
      mail@goeran.no