1 of 17

Slide Notes

DownloadGo Live

The Rewrite

Published on Nov 18, 2015

Are code rewrites in software good or bad? Why? What can I do?

PRESENTATION OUTLINE

REASONS

  • Architectural problems
  • Inefficiencies
  • Ugliness
Photo by -Piskami

All this can be solved in the
OLD CODE

THE REAL REASONS

  • Reading code is harder than writing it
  • Developers always hate old code
  • The former developer is always a fool
  • Feel more experienced today
Photo by Jitter Buffer

REWRITE = BAD!

Photo by Krstnn Hrmnsn

WHY IS IT BAD?

  • No progress for customer
  • Old code is battle-proven
  • Chance for competitors to catch up
  • New code will not be better
  • Wasting money for features that already exist
Photo by wili_hybrid

"A team would rewrite a product. What will come out of it is the exact same product with a new code base. That’s not worth the time." - Jason Fried

Photo by marfis75

BUT JASON FRIED REWROTE BASECAMP!

REWRITE = BAD?

ALWAYS?
Photo by Leo Reynolds

TECHNOLOGY BASED

IN MOST CASES THE REASON FOR A REWRITE IS
Photo by Γηεψλ

SAME Problem
SAME Solution
NEW Technology

Photo by chrisotruro

SOLUTION BASED

A REWRITE CAN BE GOOD IF IT'S
Photo by Marcus Vegas

SAME Problem
NEW Solution
NEW Technology

Photo by jenny downing

Approach the
OLD PROBLEM
in a
NEW WAY

NEW WAY

  • New Insights
  • New Features
  • New Technology
  • New ...

Tech Rewrite = Bad

Solution Rewrite = Good

LET'S GO