0
Better Software Developers
People not Resources
Developers?
Managers?
Software Projects
Chaos Summary Report 2009


                   24%
      32%




             44%
At the beginning..
Raise of complexity
Waterfall
Requirements


          Design


               Implementation



                           Verification
UML
Design Patterns
AGILE
2000 to 2008
60




45




30




15




 0
     2000   2002   2004   2006   2008
A Process is not enough
It needs skilled people
Can we measure developers?
Visionary
Trailblazer
Workhorse
Drone
Idiot
Software Engineering failed
Master and Apprentices
Study
Find a Mentor
Code Kata
Code Kata
    public void roll(int pins) {
	   	 rolls[currentRoll++] = pins;
	   }

	   public int score() {
	   	 int sc...
Coding Dojo
http://katakasts.com
How to hire them?
What do developers want?
Two Factor Theory



Job Satisfaction     =
Hygiene Factors      +
Motivation Factors
Hygiene Factors
You get what you pay
Motivation Factors
Cool Technologies
Right Kind of Problems
Being Recognized for Hard Work
Conclusions?
Raise the Bar
Chaos Summary Report 2009


                   24%
      32%




             44%
Pilots
Doctors
Forget the Cheaper
Hire the Best
Choose your way



         No Dev
Dev
Developers of the world, unite!
Questions?
Better Software Developers
Better Software Developers
Better Software Developers
Better Software Developers
Better Software Developers
Better Software Developers
Upcoming SlideShare
Loading in...5
×

Better Software Developers

3,346

Published on

How to become great developers and create Better Software through them.

4 Comments
11 Likes
Statistics
Notes
No Downloads
Views
Total Views
3,346
On Slideshare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
91
Comments
4
Likes
11
Embeds 0
No embeds

No notes for slide

Transcript of "Better Software Developers"

  1. 1. Better Software Developers
  2. 2. People not Resources
  3. 3. Developers?
  4. 4. Managers?
  5. 5. Software Projects
  6. 6. Chaos Summary Report 2009 24% 32% 44%
  7. 7. At the beginning..
  8. 8. Raise of complexity
  9. 9. Waterfall Requirements Design Implementation Verification
  10. 10. UML
  11. 11. Design Patterns
  12. 12. AGILE
  13. 13. 2000 to 2008 60 45 30 15 0 2000 2002 2004 2006 2008
  14. 14. A Process is not enough
  15. 15. It needs skilled people
  16. 16. Can we measure developers?
  17. 17. Visionary
  18. 18. Trailblazer
  19. 19. Workhorse
  20. 20. Drone
  21. 21. Idiot
  22. 22. Software Engineering failed
  23. 23. Master and Apprentices
  24. 24. Study
  25. 25. Find a Mentor
  26. 26. Code Kata
  27. 27. Code Kata public void roll(int pins) { rolls[currentRoll++] = pins; } public int score() { int score = 0; int frameIndex = 0; for (int frame = 0; frame < 10; frame++) { if (isStrike(frameIndex)) { score += 10 + strikeBonus(frameIndex); frameIndex++; } else if (isSpare(frameIndex)) { score += 10 + spareBonus(frameIndex); frameIndex += 2; } else { score += sumOfBallsInFrame(frameIndex); frameIndex += 2; } } return score; }
  28. 28. Coding Dojo
  29. 29. http://katakasts.com
  30. 30. How to hire them?
  31. 31. What do developers want?
  32. 32. Two Factor Theory Job Satisfaction = Hygiene Factors + Motivation Factors
  33. 33. Hygiene Factors
  34. 34. You get what you pay
  35. 35. Motivation Factors
  36. 36. Cool Technologies
  37. 37. Right Kind of Problems
  38. 38. Being Recognized for Hard Work
  39. 39. Conclusions?
  40. 40. Raise the Bar
  41. 41. Chaos Summary Report 2009 24% 32% 44%
  42. 42. Pilots
  43. 43. Doctors
  44. 44. Forget the Cheaper
  45. 45. Hire the Best
  46. 46. Choose your way No Dev Dev
  47. 47. Developers of the world, unite!
  48. 48. Questions?
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×