Your SlideShare is downloading. ×
0
Developers’ Toolkit in
  the Agile World
                 by

 Maria Diaconu & Alexandru Bolboaca
Code quality & indicators
Bad code?
We don’t write bad
     code...
...just occasionally
...when under pressure
Ups, we are almost
always under pressure
Or
My code is good-
enough. Why should I
     change it?
About the story tellers
               Maria Diaconu

Developer, Technical Lead, Manager
Agile/Scrum Practitioner & Coach
...
About the story tellers
            Alexandru Bolboaca

Soft ware Developer
Hands-on soft ware consultant@MosaicWorks
Aspi...
The fantastic journey
   of the beginner
     craftsman
Programming is fun
when you create great
  soft ware & write
    beautiful code
A minimal toolkit on
     the road
       Refactoring

 TDD    Clean Code   Emergent Design


           Pair
       Progr...
Clean code? What’s
       that?
Clean variable names
         Meaningful names
     Intention revealing-names
No encodings (e.g. Hungarian notation)

    ...
Clean functions
             Small !
Do one thing. And it’s DONE well.
       Descriptive names
        No sides effects
 ...
Clean code - error handling
      Try-Catch-Finally - written first
  Expected behavior covered first, exceptions
          ...
Refactoring

 23 + 23 + 23 + 23 + ... + 23
             or
        1000 * 23 ?

   Improve maintainability
        & reada...
Refactoring
     To write clean code, you must
first write dirty code and then clean it.

                      by Robert C...
Refactoring - how to
     E.g. : Extract methods, class
             Move methods
Replace conditions with polymorphism
   ...
The boy scout rule
It’s not enough to write the code well. The
    code has to be kept clean over time.
                  ...
Use the toolkit for
building soft ware
  incrementally
How we learn useful
    practices?
Soft ware Craftsmanship
Learn & Practice!
        &
Practice & Learn!
Code Kata
Code retreat
 Coding Dojo
Aspiring craftsmen




@AgileWorks -CodeRetreat/Dojo Bucharest - June
Good code reads like a
       novel.
Good code reads like a
         novel.
 Excellent code reads
      like haiku.
... and this is not the
  end of the journey
Thank you!
  Maria Diaconu & Alexandru Bolboaca

MosaicWorks - www.mozaicworks.com
mddiaconu@gmail.com; t witter: fireladyM...
Agileee Developers Toolkit In The Agile World
Upcoming SlideShare
Loading in...5
×

Agileee Developers Toolkit In The Agile World

1,043

Published on

Slides from Maria Diaconu and Alexandru Balboaca talking at Agileee conference 2009, Ukraine

Published in: Technology, Travel
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,043
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
23
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Transcript of "Agileee Developers Toolkit In The Agile World"

  1. 1. Developers’ Toolkit in the Agile World by Maria Diaconu & Alexandru Bolboaca
  2. 2. Code quality & indicators
  3. 3. Bad code? We don’t write bad code...
  4. 4. ...just occasionally
  5. 5. ...when under pressure
  6. 6. Ups, we are almost always under pressure
  7. 7. Or
  8. 8. My code is good- enough. Why should I change it?
  9. 9. About the story tellers Maria Diaconu Developer, Technical Lead, Manager Agile/Scrum Practitioner & Coach Owner Mosaic Works Founder and Coordinator of Romanian Agile community, AgileWorks Romania
  10. 10. About the story tellers Alexandru Bolboaca Soft ware Developer Hands-on soft ware consultant@MosaicWorks Aspiring soft ware craftsman Active member of Romanian Agile community, AgileWorks Romania
  11. 11. The fantastic journey of the beginner craftsman
  12. 12. Programming is fun when you create great soft ware & write beautiful code
  13. 13. A minimal toolkit on the road Refactoring TDD Clean Code Emergent Design Pair Programming
  14. 14. Clean code? What’s that?
  15. 15. Clean variable names Meaningful names Intention revealing-names No encodings (e.g. Hungarian notation) int d; //elapsed time in days vs int elapsedTimeInDays
  16. 16. Clean functions Small ! Do one thing. And it’s DONE well. Descriptive names No sides effects No duplicated functions ComputeAndWriteResult() vs Write(Compute())
  17. 17. Clean code - error handling Try-Catch-Finally - written first Expected behavior covered first, exceptions treated after Don’t return Null; Don’t Pass Null try { MealExpenses expenses = expenseReportDAO.getMeals(employee.getID()); m_total += expenses.getTotal(); } catch(MealExpensesNotFound e) { m_total += getMealPerDiem(); } vs MealExpenses expenses = expenseReportDAO.getMeals(employee.getID()); m_total += expenses.getTotal();
  18. 18. Refactoring 23 + 23 + 23 + 23 + ... + 23 or 1000 * 23 ? Improve maintainability & readability through changes in small steps keeping the external behavior
  19. 19. Refactoring To write clean code, you must first write dirty code and then clean it. by Robert C. Martin
  20. 20. Refactoring - how to E.g. : Extract methods, class Move methods Replace conditions with polymorphism Eliminate duplicate code Extract data structure
  21. 21. The boy scout rule It’s not enough to write the code well. The code has to be kept clean over time. by Robert C. Martin
  22. 22. Use the toolkit for building soft ware incrementally
  23. 23. How we learn useful practices?
  24. 24. Soft ware Craftsmanship
  25. 25. Learn & Practice! & Practice & Learn!
  26. 26. Code Kata Code retreat Coding Dojo
  27. 27. Aspiring craftsmen @AgileWorks -CodeRetreat/Dojo Bucharest - June
  28. 28. Good code reads like a novel.
  29. 29. Good code reads like a novel. Excellent code reads like haiku.
  30. 30. ... and this is not the end of the journey
  31. 31. Thank you! Maria Diaconu & Alexandru Bolboaca MosaicWorks - www.mozaicworks.com mddiaconu@gmail.com; t witter: fireladyM www.alexbolboaca.ro alexboly@gmail.com; t witter: alexboly AgileWorks Romania - agileworks.ro
  1. A particular slide catching your eye?

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

×