One against 1 - The Journey of a developer with SOLID principles

Requirements always change, and your project design should be prepared to evolve in a incremental cycle, bringing value to customers as it was expected. What should we consider while moving to illumination?

Transcript

1. AGAINST1 the journey of a developer with SOLID principles against the urge to use many standard or not think about them ONE @helmedeiros
2. once upon a time…
3. framework MV* princípios design patterns
4. a-gi-li-ty |əˈjilitē| Is about building software in tiny increments
5. how to design a… Software with a good structure? Software that is flexible? Software that is maintainable? Software that is reusable? who knows who knows who knows who knows
6. If you build your project in tiny increments, aren’t you going to miss the whole picture?
7. agile design design smells principles
8. software project
 is an abstract concept
9. software project |ˈsôftˌwe(ə)r ˈpräjˌekt, -ikt| It has to do with the overall program design, as well as the detailed structure of each module, class, and method.
10. “If you are lucky, you start a project with a clear picture of what you want the system to be. If you are luckier still, the clarity of that design makes it to the first release.” - Robert C. Martin
11. agile design design smells principles
12. then something goes wrong
 software starts to rot
13. how to detect it… before the last responsible moment? without too much precaution? allowing it to change?
14. RIGIDITY: The design is difficult to change. 1
15. FRAGILITY: The design is easy to break. 2
16. IMMOBILITY: The design is difficult to reuse. 3
17. VISCOSITY: It is difficult to do the right thing. 4
18. NEEDLESS COMPLEXITY: Overdesign. 5
19. NEEDLESS REPETITION: Mouse abuse. 6
20. OPACITY: Disorganized expression. 7
21. why software rots… change in ways that the initial design did not anticipate changes need to be made quickly developers who aren’t familiar with original philosophy
22. requirements changes
 our designs and practices have been failing
23. agile design design smells principles
24. continuos application
 to improve the structure and readability of the software
25. iterativamente visando… simple code cleaning code expressive code moderate moderate moderate
26. SRP: The Single-Responsibility Principle S
27. OCP: The Open/Closed Principle O
28. LSP: The Liskov Substitution Principle L
29. ISP: The Interface Segregation Principle I
30. DIP: The Dependency-Inversion Principle D
31. “  Agile  teams  apply  principles  only  to  solve  smells.   They  are  not  a  perf7me  to  be  liberally  sca9ered  all   over  the  system.  “   - Robert C. Martin
32. AGAINST1 the journey of a developer with SOLID principles against the urge to use many standard or not think about them ONE @helmedeiros