When code gets olderTips for keeping maintenance projects alive and kicking

Sven PetersAmbassadorAtlassian

Sven Peters

@svenpetsvenpet.com

Ambassador

Experiencemy

Disclaimer

Nothing has a more profound or long-lasting negative effect on the productivity of a software team than a mess. Nothing.“

“Robert C. Martin

gree

nField

grün

e Wiese

How long does it take?

8 hours

We need it in 6!

OK, I‘ll do it in 4!

no Tests!

REWRITE

REWRITE

WindowsBroken

the Engines Don‘t stop

no Plan BThere is

THE SCRUM MASTER

THE DEVELOPER

THE MANAGER

readabilityimprove

commentno

testautomated

Code Change Algorithmby Michael C. Feathers

Legacy1. Identify Change Points

5. Make Changes and Refactor

2. Find Test Points

3. Break Dependencies

4. Write Tests

Clean Code

nterface Segregation Principle

pen Closed Principle

iskow Substitution Principle

ingle Responsible Principle

ependency Inversion Principle

DRY Don‘t repeat yourself

KISS - Keep it simple, stupid

Favour Composition over InheritanceRoot Cause Analysis

Single Level of Abstraction

Seperation of ConcernsYou Ain‘t Gonna Need It

Clean CodeDeveloper

von Stefan Lieser &Ralf Westphalclean-code-developer.de

@svenpet

Sven PetersAtlassian