Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
When code gets older
Tips for keeping maintenance projects alive and kicking
Sven Peters
Ambassador
Atlassian
Sven Peters
@svenpet
svenpet.com
Ambassador
Experience
my
Disclaimer
Nothing has a more profound or long-
lasting negative effect on the productivity
of a software team than a mess. Nothing.
...
green
Field
grüne
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 B
There is
THE SCRUM MASTER
THE DEVELOPER
THE MANAGER
readability
improve
commentno
test
automated
Code Change Algorithmby Michael C. Feathers
Legacy
1. Identify Change Points
5. Make Changes and Refactor
2. Find Test Poi...
Clean Code
nterface Segregation Principle
pen Closed Principle
iskow Substitution Principle
ingle Responsible Principle
ependency Inv...
DRY Don‘t repeat yourself
KISS - Keep it simple, stupid
Favour Composition over InheritanceRoot Cause Analysis
SingleLevel...
Clean Code
Developer
von
Stefan Lieser &
Ralf Westphal
clean-code-developer.de
@svenpet
Sven PetersAtlassian
When code gets_older
When code gets_older
When code gets_older
When code gets_older
Upcoming SlideShare
Loading in …5
×

2

Share

Download to read offline

When code gets_older

Download to read offline

How to keep maintenance projects alive and kicking

Related Books

Free with a 30 day trial from Scribd

See all

When code gets_older

  1. When code gets older Tips for keeping maintenance projects alive and kicking Sven Peters Ambassador Atlassian
  2. Sven Peters @svenpet svenpet.com Ambassador
  3. Experience my Disclaimer
  4. Nothing has a more profound or long- lasting negative effect on the productivity of a software team than a mess. Nothing. “ “Robert C. Martin
  5. green Field
  6. grüne Wiese How long does it take? 8 hours We need it in 6! OK, I‘ll do it in 4! no Tests!
  7. REWRITE
  8. REWRITE
  9. WindowsBroken
  10. the Engines Don‘t stop
  11. no Plan B There is THE SCRUM MASTER THE DEVELOPER THE MANAGER
  12. readability improve
  13. commentno
  14. test automated
  15. Code Change Algorithmby Michael C. Feathers Legacy 1. Identify Change Points 5. Make Changes and Refactor 2. Find Test Points 3. Break Dependencies 4. Write Tests
  16. Clean Code
  17. nterface Segregation Principle pen Closed Principle iskow Substitution Principle ingle Responsible Principle ependency Inversion Principle
  18. DRY Don‘t repeat yourself KISS - Keep it simple, stupid Favour Composition over InheritanceRoot Cause Analysis SingleLevelofAbstraction Seperation of ConcernsYou Ain‘t Gonna Need It
  19. Clean Code Developer von Stefan Lieser & Ralf Westphal clean-code-developer.de
  20. @svenpet Sven PetersAtlassian
  • korayem

    Jan. 30, 2015
  • Zilnik

    Jan. 11, 2013

How to keep maintenance projects alive and kicking

Views

Total views

5,140

On Slideshare

0

From embeds

0

Number of embeds

2,577

Actions

Downloads

25

Shares

0

Comments

0

Likes

2

×