The Craftsman Developer In An Agile World

2,546 views

Published on

The Craftsman Developer In An Agile World - presented by Corey Haines at OpenAgile Romania conference eLiberatica 2009

Published in: Technology
1 Comment
7 Likes
Statistics
Notes
  • Corey, we can't download the slides?
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
2,546
On SlideShare
0
From Embeds
0
Number of Embeds
268
Actions
Shares
0
Downloads
99
Comments
1
Likes
7
Embeds 0
No embeds

No notes for slide

The Craftsman Developer In An Agile World

  1. 1. But first Saturday, May 23, 2009
  2. 2. Why do we write bad code? Saturday, May 23, 2009
  3. 3. When do we write bad code? Saturday, May 23, 2009
  4. 4. Pressure Saturday, May 23, 2009
  5. 5. Have to get it done! Saturday, May 23, 2009
  6. 6. “Get It Done” vs “Do It Right” Saturday, May 23, 2009
  7. 7. Hack Away At Code Saturday, May 23, 2009
  8. 8. An idea Saturday, May 23, 2009
  9. 9. Constant Pressure Saturday, May 23, 2009
  10. 10. Every Month, in fact Saturday, May 23, 2009
  11. 11. Sound Familiar? Saturday, May 23, 2009
  12. 12. Agile? Saturday, May 23, 2009
  13. 13. Corey Haines Journeyman Developer That’s Me! www.coreyhaines.com coreyhaines@gmail.com @coreyhaines Saturday, May 23, 2009
  14. 14. The Craftsman Developer why you need to be one presented by Corey Haines at Saturday, May 23, 2009
  15. 15. or Saturday, May 23, 2009
  16. 16. Why Agile Can Fail Saturday, May 23, 2009
  17. 17. Naked Scrum Saturday, May 23, 2009
  18. 18. Scrum Assumption Saturday, May 23, 2009
  19. 19. Developers Self-Organize Saturday, May 23, 2009
  20. 20. Responsible Developers Saturday, May 23, 2009
  21. 21. Usual Process Saturday, May 23, 2009
  22. 22. Beautiful System Saturday, May 23, 2009
  23. 23. Add a feature Saturday, May 23, 2009
  24. 24. Add a new feature Saturday, May 23, 2009
  25. 25. Change a feature Saturday, May 23, 2009
  26. 26. Time Passes Saturday, May 23, 2009
  27. 27. Look Familiar Saturday, May 23, 2009
  28. 28. Add a new feature How? Saturday, May 23, 2009
  29. 29. Crap Code Saturday, May 23, 2009
  30. 30. Software Gardener Saturday, May 23, 2009
  31. 31. Saturday, May 23, 2009
  32. 32. Saturday, May 23, 2009
  33. 33. Constant Cleaning Saturday, May 23, 2009
  34. 34. Emergent Design Saturday, May 23, 2009
  35. 35. Add a feature Saturday, May 23, 2009
  36. 36. Clean It Up Saturday, May 23, 2009
  37. 37. Add a new feature Saturday, May 23, 2009
  38. 38. Clean It Up Saturday, May 23, 2009
  39. 39. Change a feature Saturday, May 23, 2009
  40. 40. Time Passes Saturday, May 23, 2009
  41. 41. Clean Architecture Saturday, May 23, 2009
  42. 42. Over Time Saturday, May 23, 2009
  43. 43. How do you do this? Saturday, May 23, 2009
  44. 44. Extreme Programming (XP) Saturday, May 23, 2009
  45. 45. Development Techniques Saturday, May 23, 2009
  46. 46. Saturday, May 23, 2009
  47. 47. Why don’t we do them? Saturday, May 23, 2009
  48. 48. We don’t know how Saturday, May 23, 2009
  49. 49. How do you learn to do it? Saturday, May 23, 2009
  50. 50. Emergent Design / Evolutionary Design Saturday, May 23, 2009
  51. 51. Over Time Saturday, May 23, 2009
  52. 52. Test-Driven Development (TDD) Saturday, May 23, 2009
  53. 53. How do we learn? Saturday, May 23, 2009
  54. 54. Work != Practice Saturday, May 23, 2009
  55. 55. Agilists assume Craftsmanship, only few people pursue craftsmanship - Jurgen Appelo earlier today Saturday, May 23, 2009
  56. 56. How do we practice? Saturday, May 23, 2009
  57. 57. Software Craftsmanship http://manifesto.softwarecraftsmanship.org/ Saturday, May 23, 2009
  58. 58. Continual Learning Saturday, May 23, 2009
  59. 59. Deliberate Practice Saturday, May 23, 2009
  60. 60. Practice Techniques Coding Dojo Code Kata Code Retreat Acceptance Test-based Saturday, May 23, 2009
  61. 61. Coding Dojo Saturday, May 23, 2009
  62. 62. Kata Saturday, May 23, 2009
  63. 63. Performed Kata Saturday, May 23, 2009
  64. 64. Code Retreat Saturday, May 23, 2009
  65. 65. Acceptance Test-Based Saturday, May 23, 2009
  66. 66. Practice Saturday, May 23, 2009
  67. 67. Minimize Distance Between “Get it Done” and “Do it Right” Saturday, May 23, 2009
  68. 68. Stop Writing Crap Saturday, May 23, 2009
  69. 69. Thank You! Contact Information: www.coreyhaines.com Thanks to Saturday, May 23, 2009

×