Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Legacy code & fun

Legacy code & fun

Welcome all my name is Marco, I'm italian.
I've been writing in PHP pretty much since I was 20 and I worked as PHP developer in Italy, UK and here in Melbourne of course.

I don't know why exactly but a little bit everywhere I found myself to work on legacy code.

This presentation is going to be all about my experience, thoughts and ideas on legacy code.

I hope you'll enjoy :)

borracciaBlu

January 13, 2016
Tweet

Other Decks in Programming

Transcript

  1. 4

  2. • code written by other people • executable (in some

    way is working) • nobody is able to read the code (no tests) Legacy code properties: 5
  3. • code written by other people • executable (in some

    way is working) • nobody is able to read the code (no tests) Legacy code properties: 6
  4. http://blog.noctua-software.com/deal-with-legacy-code.html In one case I was specifically hired to replace

    the original maintainer who -as I later learned- left the company from a burnout caused by the frustration of having to maintain his own code. 7
  5. E.W.Dijkstra /dɛɪkstra/ My point today is that, if we wish

    to count lines of code, we should not regard them as “lines produced” but as “lines spent”: the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger. 11
  6. 14

  7. • no documentation • no ownership • scared to change

    • bad deadlines Why it’s happening : 24
  8. 26

  9. 28

  10. 1-4 is low complexity 5-7 is moderate complexity 8-10 is

    high complexity 11+ is very high complexity CYCLOMATIC COMPLEXITY 30
  11. 33

  12. Life isn't black and white. It's a million gray areas,

    don't you find? BE INCREMENTAL 37