Tweet
Tweet

Slide 1

Slide 1 text

@ragunathjawahar / legacycode.com Single-responsibility principle

Slide 2

Slide 2 text

@ragunathjawahar / legacycode.com Single-responsibility principle meets the real world! 🥳

Slide 3

Slide 3 text

SOLID @ragunathjawahar / legacycode.com

Slide 4

Slide 4 text

SOLID @ragunathjawahar / legacycode.com

Slide 5

Slide 5 text

Single-responsibility principle • Every class should have only one responsibility • A class should have only one reason to change • A module should be responsible to one, and only one, actor @ragunathjawahar / legacycode.com

Slide 6

Slide 6 text

Why do we have large classes? @ragunathjawahar / legacycode.com

Slide 7

Slide 7 text

Why do we have large classes? • Code smells • Long methods • Feature-envy • Too many methods/functions • Missing abstraction • Duplication • Primitive obsession • Data clumps • … • Developer churn • No tests • Cross-cutting concerns • Utilities • High-level classes

Slide 8

Slide 8 text

Why do we have large classes? • Code smells • Long methods • Feature-envy • Too many methods/functions • Missing abstraction • Duplication • Primitive obsession • Data clumps • … • Developer churn • No tests • Cross-cutting concerns • Utilities • High-level classes

Slide 9

Slide 9 text

High-level classes The term "high-level classes" typically refers to classes that operate at a higher level of abstraction compared to other classes in the system. They generally encapsulate broad concepts, complex behaviors, or orchestration tasks rather than speci fi c, detailed implementations. @ragunathjawahar / legacycode.com

Slide 10

Slide 10 text

High-level classes The term "high-level classes" typically refers to classes that operate at a higher level of abstraction compared to other classes in the system. They generally encapsulate broad concepts, complex behaviors, or orchestration tasks rather than speci fi c, detailed implementations. @ragunathjawahar / legacycode.com

Slide 11

Slide 11 text

High-level classes The term "high-level classes" typically refers to classes that operate at a higher level of abstraction compared to other classes in the system. They generally encapsulate broad concepts, complex behaviors, or orchestration tasks rather than speci fi c, detailed implementations. @ragunathjawahar / legacycode.com

Slide 12

Slide 12 text

High-level classes The term "high-level classes" typically refers to classes that operate at a higher level of abstraction compared to other classes in the system. They generally encapsulate broad concepts, complex behaviors, or orchestration tasks rather than speci fi c, detailed implementations. @ragunathjawahar / legacycode.com

Slide 13

Slide 13 text

High-level classes The term "high-level classes" typically refers to classes that operate at a higher level of abstraction compared to other classes in the system. They generally encapsulate broad concepts, complex behaviors, or orchestration tasks rather than speci fi c, detailed implementations. @ragunathjawahar / legacycode.com

Slide 14

Slide 14 text

High-level classes The term "high-level classes" typically refers to classes that operate at a higher level of abstraction compared to other classes in the system. They generally encapsulate broad concepts, complex behaviors, or orchestration tasks rather than speci fi c, detailed implementations. @ragunathjawahar / legacycode.com

Slide 15

Slide 15 text

TLDR; They just have too many things to do 🤷 @ragunathjawahar / legacycode.com

Slide 16

Slide 16 text

How do we deal with them? @ragunathjawahar / legacycode.com

Slide 17

Slide 17 text

—Albert Einstein “We cannot solve our problems with the same thinking we used when we created them.”

Slide 18

Slide 18 text

Eureka & StoryViewerPageFragment.kt @ragunathjawahar / legacycode.com

Slide 19

Slide 19 text

Eureka & StoryViewerPageFragment.kt @ragunathjawahar / legacycode.com

Slide 20

Slide 20 text

Eureka & StoryViewerPageFragment.kt @ragunathjawahar / legacycode.com

Slide 21

Slide 21 text

Eureka & StoryViewerPageFragment.kt (1350 LOC) @ragunathjawahar / legacycode.com

Slide 22

Slide 22 text

Live Demo 🧑💻 @ragunathjawahar / legacycode.com

Slide 23

Slide 23 text

Do • Use IDE-assisted refactoring • Use a git GUI client • Use micro-commits with Arlo Belshee’s commit notation • Pair/ensemble program • Verify manually

Slide 24

Slide 24 text

Don’t • Have long running branches • Push it too far @ragunathjawahar / legacycode.com

Slide 25

Slide 25 text

Installation $ brew install legacycodehq/tap/eureka @ragunathjawahar / legacycode.com

Slide 26

Slide 26 text

Watch $ eureka watch -x android StoryViewerPageFragment @ragunathjawahar / legacycode.com

Slide 27

Slide 27 text

@ragunathjawahar / legacycode.com

Slide 28

Slide 28 text

https://github.com/ LegacyCodeHQ/eureka @ragunathjawahar / legacycode.com

Slide 29

Slide 29 text

Questions? @ragunathjawahar / legacycode.com