• Save
Sandro Mancuso - Software Craftmanship @ I T.A.K.E. Unconference 2013, Bucharest
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
2,265
On Slideshare
427
From Embeds
1,838
Number of Embeds
5

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 1,838

http://2013.itakeunconf.com 1,275
http://itakeunconf.com 546
http://2014.itakeunconf.com 12
http://www.365dailyjournal.com 4
http://www.2013.itakeunconf.com 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Software Craftsmanship Sandro Mancuso @sandromancuso http://leanpub.com/socra
  • 2. Software Craftsmen just care about beautiful code
  • 3. Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
  • 4. We adopted Agile and now things will be OK … and the Agile Transformation Era began.
  • 5. And then we spend 10 year focusing on... … people, interactions, team building, the ecosystem… .. and processes became more important than technical practices
  • 6. Many Agile projects are now, steadily and iteratively, producing crap mediocre software. The Agile Hangover
  • 7. We want to get things done... … but we are under pressure
  • 8. The wrong notion of time
  • 9. But what is to be Agile anyway?
  • 10. Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
  • 11. The invisible threat Code quality Time per feature
  • 12. Manifesto for Software Craftsmanship raising the bar As aspiring Software Craftsmen we are raising the bar of professional software development by practising it and helping others learn the craft. Through this work we have come to value:
  • 13. Manifesto for Software Craftsmanship raising the bar As aspiring Software Craftsmen we are raising the bar of professional software development by practising it and helping others learn the craft. Through this work we have come to value: Not only working software, but also well-crafted software
  • 14. Manifesto for Software Craftsmanship raising the bar As aspiring Software Craftsmen we are raising the bar of professional software development by practising it and helping others learn the craft. Through this work we have come to value: Not only working software, but also well-crafted software Not only responding to change, but also steadily adding value
  • 15. Manifesto for Software Craftsmanship raising the bar As aspiring Software Craftsmen we are raising the bar of professional software development by practising it and helping others learn the craft. Through this work we have come to value: Not only working software, but also well-crafted software Not only responding to change, but also steadily adding value Not only individuals and interactions, but also a community of professionals
  • 16. Manifesto for Software Craftsmanship raising the bar As aspiring Software Craftsmen we are raising the bar of professional software development by practising it and helping others learn the craft. Through this work we have come to value: Not only working software, but also well-crafted software Not only responding to change, but also steadily adding value Not only individuals and interactions, but also a community of professionals Not only customer collaboration, but also productive partnerships
  • 17. What is Software Craftsmanship? Software Craftsmanship is all about putting responsibility, professionalism, pragmatism and pride back into software development
  • 18. Does context matter? Does it always matter?
  • 19. How do we know we are building the right thing? How do we know we are building the thing right?
  • 20. Adding value through practices  Automated testing  Test first  Test-Driven Development  Pair-programming  Continuous Integration
  • 21. Don't discuss practices, discuss value ~ Corey Haines
  • 22. Mastering the practices is hard … … and that's why we practice
  • 23. Perfect practice (narrowing the gap)
  • 24. Software Craftsmanship is a long journey to mastery
  • 25. Seniority is relative and transient
  • 26. Software Craftsmanship Attitude - Owning our careers - Not a 9 to 5 profession - Practice - Boy scout rule - Promotions
  • 27. The attitude towards legacy code
  • 28. Software Craftsmanship is not... … a church, trying to convert all developers It's about leading by example and showing how we can be better … about beautiful code It's about continuously delivering value not writing crap code
  • 29. Craftsmanship is not enough to guarantee the success of a project but the lack of it can be the main cause of its failure
  • 30. What does it mean to be a software craftsman?
  • 31. How it is done is as important as having it done ~ Eduardo Namur
  • 32. Are you a software crafter?
  • 33. Thank You http://leanpub.com/socr a Sandro Mancuso @sandromancuso