!Smelly code - The origins

Some best practices we use to forget

Transcript

1. !smelly_code clean development @alexsimonescu
2. Coach better than teach
3. N-Layered Domain Oriented Architecture Guide
4. SOLID
5. what’s next?
6. GRASP
7. General Responsibility Assignment Software Patterns
8. (High cohesion) && (Low coupling)
9. Cohesion
10. High Cohesion - Methods of a class have much in common
11. High Cohesion - Methods of a class have much in common - Methods focus on same functionality
12. High Cohesion - Methods of a class have much in common - Methods focus on same functionality - Higher cohesion between elements = better
13. High Cohesion - Methods of a class have much in common - Methods focus on same functionality - Higher cohesion between elements = better - Lower cohesion can be disturbing; but not critical
14. Cohesion Types
15. Functional Cohesion Small units, work together and share same intention / function
16. Sequencial Cohesion Output of an element, serves as input for another one
17. Informational Cohesion Different modules work with same data object
18. Procedural Cohesion Elements are grouped together in order to sequentially execute a task
19. Temporal Cohesion Elements are executed at same moment of time
20. Logical Cohesion Logical elements are put together in same module
21. Loose Coupling
22. Loose coupling - Increase reusability
23. Loose coupling - Increase reusability - Low colateral effect when changing collaborators
24. Patterns
25. Reuse / release equivalence - Libraries
26. Reuse / release equivalence - Libraries - You are the consumer
27. Reuse / release equivalence - Libraries - You are the consumer - You should not need to look at source code
28. Reuse / release equivalence - Libraries - You are the consumer - You should not need to look at source code - Take care with semantic versioning
29. Common reuse principle - Tells how to organize packages
30. Common reuse principle - Tells how to organize packages - The classes on a package are reused together
31. Common reuse principle - Tells how to organize packages - The classes on a package are reused together - If you reuse one class from the package, you should reuse all
32. Acyclic dependencies - The dependency graph between packages should be direct
33. Acyclic dependencies - The dependency graph between packages should be direct - There must not be any cycles
34. Smells
35. Compound names
36. Long names
37. Comments
38. Long parameters list
39. Duplicated code
40. Conditional complexity
41. Large classes
42. Dead code
43. Temporary fields
44. Crime scene
45. Crime scene
46. Code Maat
47. Code Maat
51. Find the boss
52. Use cases
53. MVC
54. MVC
55. MVP
56. MVP
57. MVVM
58. MVVMP
59. Clean Architecture
64. Hexagonal
68. Thanks!