thisCodeSucks

Build the plane while flying

Technical Debt

Turning into a monster

Borderline obsessive about how I do things

This code suuuuuuuuuuuuuuuuuuuuuucks.

REFACTORING

I rewrite the whole damn thing.

Regressions, of course

When code that worked, doesn't anymore. Because of something I did. Probably.

Regressions are the worst

• Unplanned for
• Difficult to spot
• Erode confidence in the whole team

That line of code is probably there for a reason.

There is a difference between technical debt and code that just irks me.

What does it matter if
my code is perfect
but my software sucks?

Scenario:

Swapping if / elif / else in favor of dictionary lookup.

if team == 'Falcons':
    odds = '100 to 1'
elif team == 'Patriots':
    odds = '3 to 1'
elif team == 'Titans':
    odds = 'maybe next year'

super_bowl_odds = {
    'Falcons': '100 to 1',
    'Patriots': '3 to 1',
    'Titans': 'maybe next year'
}

odds = super_bowl_odds.get(team, 'Unknown team')

Stack Overflow: "Better optimization technique using if/else or dictionary"

NO

Scenario:

Many of my dependencies are well out of date, some are unsupported altogether.

# requirements.txt
requests==0.2.0

YES

Scenario:

I've created a generic utility function to replace code that's been copied and pasted in several places

def plus_one_week(dt):
    """
    Returns the given date plus 7 days.
    """
    return dt + timedelta(days=7)

from ..utility.date import plus_one_week

# ...further down the page

        c = self.create(user_id=user.id,
            type='invitation',
            redirect_url=app.config['JOIN_LINK'],
            expires_on=plus_one_week(datetime.now()))

NO, but...

Scenario:

class BeveragesView(TemplateView):
template_name = 'drinks.html'

def get_context_data(self, **kwargs):
    context = super(BeveragesView, self).get_context_data(**kwargs)

    # leave the templates the same or change?
    context['drinks'] = get_beverages(self.request)
    return context

YES

Scenario:

A view design changes dramatically

YES, but...

Scenario:

Tests

• If they're not there, write them
• Forces you to understand the code deeply
• Strong business justification for refactoring
• Doubles as de facto documentation

  Eric Elliott: "5 Questions Every Unit Test Must Answer"

Documentation

Write it all down

Be careful with refactor tools

• grep - find via command line
• sed - find and replace via command line and regex
• PyCharm or other IDEs