Downloaded 27 times
Uploaded byAgileee
Agileee Developers Toolkit In The Agile World
This document discusses the importance of writing clean code and using refactoring techniques in an agile development environment. It introduces tools like test-driven development, clean code principles, and emergent design that can help developers improve code quality. Refactoring is presented as a key way to transform "dirty" code into clean code through incremental changes while preserving external behavior. The document encourages learning practices like code katas, coding dojos, and code retreats to help aspiring software craftsmen improve.
More Related Content
Similar to Agileee Developers Toolkit In The Agile World
![UiPath Automation Suite Installation (Hands-On) [2/3]](https://cdn.slidesharecdn.com/ss_thumbnails/automationsuitecommunitysession2-251015095633-a6d862f1-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
Agileee Developers Toolkit In The Agile World
- 1. Developers’ Toolkit in the Agile World by Maria Diaconu & Alexandru Bolboaca
- 2. Code quality &indicators
- 3. Bad code? We don’twrite bad code...
- 4.
- 5.
- 6. Ups, we arealmost always under pressure
- 7.
- 8. My code isgood- enough. Why should I change it?
- 9. About the storytellers Maria Diaconu Developer, Technical Lead, Manager Agile/Scrum Practitioner & Coach Owner Mosaic Works Founder and Coordinator of Romanian Agile community, AgileWorks Romania
- 10. About the storytellers Alexandru Bolboaca Soft ware Developer Hands-on soft ware consultant@MosaicWorks Aspiring soft ware craftsman Active member of Romanian Agile community, AgileWorks Romania
- 11. The fantastic journey of the beginner craftsman
- 12. Programming is fun whenyou create great soft ware & write beautiful code
- 13. A minimal toolkiton the road Refactoring TDD Clean Code Emergent Design Pair Programming
- 14. Clean code? What’s that?
- 16. Clean variable names Meaningful names Intention revealing-names No encodings (e.g. Hungarian notation) int d; //elapsed time in days vs int elapsedTimeInDays
- 17. Clean functions Small ! Do one thing. And it’s DONE well. Descriptive names No sides effects No duplicated functions ComputeAndWriteResult() vs Write(Compute())
- 18. 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();
- 19. Refactoring 23 +23 + 23 + 23 + ... + 23 or 1000 * 23 ? Improve maintainability & readability through changes in small steps keeping the external behavior
- 20. Refactoring To write clean code, you must first write dirty code and then clean it. by Robert C. Martin
- 21. Refactoring - howto E.g. : Extract methods, class Move methods Replace conditions with polymorphism Eliminate duplicate code Extract data structure
- 22. The boy scoutrule It’s not enough to write the code well. The code has to be kept clean over time. by Robert C. Martin
- 23. Use the toolkitfor building soft ware incrementally
- 24. How we learnuseful practices?
- 25.
- 26. Learn & Practice! & Practice & Learn!
- 27. Code Kata Code retreat Coding Dojo
- 28. Aspiring craftsmen @AgileWorks -CodeRetreat/DojoBucharest - June
- 29. Good code readslike a novel.
- 30. Good code readslike a novel. Excellent code reads like haiku.
- 31. ... and thisis not the end of the journey
- 32. 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