Refactoring Legacy Applications

June 10, 2017

94

Refactoring Legacy Applications

Aaron Holbrook

June 10, 2017

Tweet

More Decks by Aaron Holbrook

See All by Aaron Holbrook

Debugging PHP Applications

0

45

Build a PHP Safety Net: Automated Checks Before You Commit

0

23

Safe and Happy Deploys Using Automation

0

190

Introduction to IDEs and Debugging

0

180

Making WordPress Search Kick-ass with Elasticsearch

0

1.6k

Static Site to WordPress

0

110

WordPress is a CMS, DAMMIT!

7

2k

WordPress & Version Control (v2) - WordCamp Chicago 2012

9

5.3k

Other Decks in Technology

See All in Technology

初心者に Vue.js を教えるには

3

210

バイセルにおけるAI活用の取り組みについて紹介します/Generative AI at BuySell Technologies

1

200

Java x Spring Boot Warm up

2

420

Kubernetes Summit 2024 Keynote：104 在 GitOps 大規模實踐中的甜蜜與苦澀

0

270

新R25、乃木坂46 Mobileなどのファンビジネスを支えるマルチテナンシーなプラットフォームの全体像 / cam-multi-cloud

cyberagentdevelopers

1

110

Databricksワークショップ - 生成AIとDWH

2

4.5k

オニオンアーキテクチャで実現した本質課題を解決するインフラ移行の実例

13

2.7k

WHOLENESS, REPAIRING, AND TO HAVE FUN: 全体性、修復、そして楽しむこと

3

3.6k

顧客が本当に必要だったもの - パフォーマンス改善編 / Make what is needed

21

5.8k

わたしとトラックポイント / TrackPoint tips

masahirokawahara

1

200

Tokyo dbt Meetup #10 dbt Cloudユーザー会 & パネルディスカッション

1

180

現地でMeet Upをやる場合の注意点〜反省点を添えて〜

0

160

Featured

See All Featured

24

4.9k

97

6.7k

10 Git Anti Patterns You Should be Aware of

653

59k

VelocityConf: Rendering Performance Case Studies

325

24k

Build your cross-platform service in a week with App Engine

229

18k

Testing 201, or: Great Expectations

38

7k

[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails

32

1.8k

Sharpening the Axe: The Primacy of Toolmaking

37

1.8k

How STYLIGHT went responsive

95

5.1k

No one is an island. Learnings from fostering a developers community.

19

3k

Why You Should Never Use an ORM

53

9k

Adopting Sorbet at Scale

73

9k

Transcript

Refactoring Legacy Applications aaronjholbrook aaronjholbrook.com no stock photography was harmed
in the making of this deck
None
None
None
None
None
None
None
Why Refactor?
Things to be careful of Refactoring just to refactor (superﬁcial
or unnecessary) Taking on too much at once (spinning plates) Staleness (not shipping) Partial or incomplete refactor Not testing
None
Why are YOU refactoring?
Why I refactor
Comprehension
Maintainability
Simpliﬁcation
Co n s i s t e n c y
Test Debug Take it slow Simplify Strategies & Techniques
File length File naming File and directory organization Namespace Strategies
& Techniques
Decouple Single Responsibility Exit Early / Exit Often Abstract complexity
Strategies & Techniques
None
None
aaronjholbrook aaronjholbrook.com Aaron Holbrook Director of Web Engineering Zeek Interactive