• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Euruko 2009 - Software Craftsmanship
 

Euruko 2009 - Software Craftsmanship

on

  • 242 views

 

Statistics

Views

Total Views
242
Views on SlideShare
242
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

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

    Euruko 2009 - Software Craftsmanship Euruko 2009 - Software Craftsmanship Presentation Transcript

    • Software Craftsmanship for better software Phillip Oertel @ EuRuKo 200912.05.2009 (Di)
    • Overview • Where does this term come from? • How does it help us? • What does it demand?12.05.2009 (Di)
    • We‘ve compared ourselves to ...12.05.2009 (Di)
    • artists12.05.2009 (Di)
    • musicians12.05.2009 (Di)
    • writers12.05.2009 (Di)
    • architects12.05.2009 (Di)
    • engineers12.05.2009 (Di)
    • We are professional software developers.12.05.2009 (Di)
    • craftsmen12.05.2009 (Di)
    • 12.05.2009 (Di)
    • schedule requirements code quality12.05.2009 (Di)
    • It‘s our fault.12.05.2009 (Di)
    • How does Software Craftsmanship fix this?12.05.2009 (Di)
    • Values12.05.2009 (Di)
    • Responsibility12.05.2009 (Di)
    • Practise12.05.2009 (Di)
    • Discipline12.05.2009 (Di)
    • Practises12.05.2009 (Di)
    • Iterative development12.05.2009 (Di)
    • Automated tests12.05.2009 (Di)
    • KISS keep it simple, stupid.12.05.2009 (Di)
    • Close customer collaboration12.05.2009 (Di)
    • Continuous small improvements12.05.2009 (Di)
    • 12.05.2009 (Di)
    • Code for other humans, not machines.12.05.2009 (Di)
    • Think of code in flux.12.05.2009 (Di)
    • Refactoring12.05.2009 (Di)
    • Hard, Basic skills12.05.2009 (Di)
    • Comments Classes Formatting Unit Tests Meaningful Names Systems Functions Error Handling Objects and Data Structures Concurrency Boundaries12.05.2009 (Di)
    • Functions12.05.2009 (Di)
    • Functions • small • prefer exceptions • do one thing • don‘t repeat yourself • one level of abstraction • use descriptive names • function arguments • have no side effects12.05.2009 (Di)
    • How we learn12.05.2009 (Di)
    • 12.05.2009 (Di)
    • learn like craftsmen: apprentice journeyman master12.05.2009 (Di)
    • we loose masters.12.05.2009 (Di)
    • values and skills are not enough.12.05.2009 (Di)
    • 12.05.2009 (Di)
    • 12.05.2009 (Di)
    • some books • Clean Code, Robert C. Martin, 2008 • The Pragmatic Programmer, Andy Hunt, Dave Thomas, 1999 • Refactoring, Martin Fowler, 1999 • Software Craftsmanship, Pete McBreen, 200212.05.2009 (Di)
    • photo credits • Musician: http://www.flickr.com/photos/tommarcello/2250681391/ • Fountain pen: http://www.flickr.com/photos/brightmeadow/281659324/ • Architecture model: http://www.flickr.com/photos/blahflowers/2613241979/ • F1 Engineers: http://www.flickr.com/photos/7480659@N06/2295266851/ • Craftsman: http://www.flickr.com/photos/andreasej/3120849218/ • Doctor: http://www.flickr.com/photos/orcoo/345583754/ • Monkeying around: http://www.flickr.com/photos/practicalowl/661094024/12.05.2009 (Di)