refactoring

Refactoring Oli Wood @coldclimate

What How Tools When

2,300 lines single file no classes 2 years old

"too important to risk breaking it"

"make it do this..."

replacing what is there with something new

that does exactly the same thing

same functionality

...faster

...securer

...extendable

...maintainabler

...more better

work out what it actually does (you think)

...high level

fits into a couple of paragraphs

...low level

function by function docblock it

find out what it actually does

including the bits everybody forgot

document its API/interface/what ever

unit tests*

Redesign it

high level logical grouping

Class structure

...think design patterns (maybe)

work out where you are going

...and get there step at a time

...nail the bit you're working on

...don't have too many balls in the air

...#TODO this thing you will forget

...#SHOULDDO ace thing you might do later

...keep running the tests

...and stop at 80%

sublime text

redacted

grep -Rin

phpunit

Selenium

ghetto tests (curl > Apache logs > *nix > diff)

code formatters

php codesniffer

php coding standards fixer

Refactoring is a good sign you're thinking about the code

...constant refactoring is geek circle jerk

...man up and live with it

...when it stops you doing something more important

...when you know what you're doing

...once the cost of not doing it out weighs that
of doing it

...when can't stand it any more

16 files object orientated does exactly the same thing

2 new modules Several £k income Multi-developer

A confession

refactoring

refactoring

More Decks by coldclimate

Other Decks in Technology

Featured

Transcript