Release your refactoring superpower

Release Your Refactoring
Superpower
By:
Adam Culp
Twitter: @adamculp

2
Release Your Refactoring Superpower
●
About me
– OSS Contributor
– PHP Certified
– Zend Certification Advisory Board
– PHP-Fig voting member (IBM i Toolkit)
– Consultant at Zend Technologies
– Organizer SoFloPHP (South Florida)
– Organizer SunshinePHP (Miami)
– Long distance (ultra) runner
– Photography Enthusiast
– Judo Black Belt Instructor

3
●
About me
– OSS Contributor
– PHP Certified
– Zend Certification Advisory Board
– PHP-Fig voting member (IBM i Toolkit)
– Consultant at Zend Technologies
– Organizer SoFloPHP (South Florida)
– Organizer SunshinePHP (Miami)
– Long distance (ultra) runner
– Photography Enthusiast
– Judo Black Belt Instructor
I am the
PHP Ninja!!!

4
●
Fan of iteration
– Pretty much everything requires iteration to do well:
●
Long distance running
●
Judo
●
Development
●
Evading project managers
●
Refactoring!

5
●
What Can I Do?
– Estimation

6
●
What Can I Do?
– Estimation
– Coding (actual refactoring)

7
●
What Can I Do?
– Estimation
– Algorithms

8
●
What Can I Do?
– Estimation
– Algorithms
– Convince Business

9
●
What Can I Do?
– Estimation
– Algorithms
– Convince Business
– Silver Bullet

10
●
Modernization?
– How?
●
New infrastructure (servers, technology, etc.)

11
●
Modernization?
– How?
●
●
New frameworks or libraries

12
●
Modernization?
– How?
●
●
●
New programming language

13
●
Modernization?
– How?
●
●
●
●
New DB

14
●
Modernization?
– How?
●
●
●
●
New DB
– Why?
●
Desire

15
●
Modernization?
– How?
●
●
●
●
New DB
– Why?
●
Desire
●
Bored

16
●
Modernization?
– How?
●
●
●
●
New DB
– Why?
●
Desire
●
Bored
●
Perceived need

17
●
Modernization?
– How?
●
●
●
●
New DB
– Why?
●
Desire
●
Bored
●
Perceived need
●
To gain something
– Speed
– Functionality

18
●
Modernization?
– How?
●
●
●
●
New DB
– Why?
●
Desire
●
Bored
●
Perceived need
●
To gain something
– Speed
– Functionality
– When?
●
Next 6 months, year(s), decade

19
●
Modernization?
– How?
●
●
●
●
New DB
– Why?
●
Desire
●
Bored
●
Perceived need
●
To gain something
– Speed
– Functionality
– When?
●
●
Realistic time

20
●
Modernization?
– How?
●
●
●
●
New DB
– Why?
●
Desire
●
Bored
●
Perceived need
●
To gain something
– Speed
– Functionality
– When?
●
●
Realistic time
●
NOW!

21
●
Rewrite FTW!

22
●
Typical Loop
– Business Responses
●
No time

23
●
Typical Loop
●
No time
●
No money

24
●
Typical Loop
●
No time
●
No money
●
No need

25
●
Typical Loop
●
No time
●
No money
●
No need
●
Things are “good enough”

26
●
The Fix

27
●
Case Study
– Managing legacy system costs: A case study of a meta-assessment model
to identify solutions in a large financial services company – 2017 (by
James Crotty, Ivan Horrocks) -
https://www.sciencedirect.com/science/article/pii/S221083271630126
0#b0025
●
2001 Brooke and Ramage defined legacy as:
– Old information system remaining in operation within an Organization

28
●
Case Study
0#b0025
●
– Business critical, resisting modification as failure would cause significant impact
on business

29
●
Case Study
0#b0025
●
on business
– Based on outdated technology but critical day-to-day operations

30
●
Case Study
0#b0025
●
on business
– Built when processing and storage was much more expensive

31
●
Case Study
0#b0025
●
on business
– Poorly documented

32
●
Case Study
0#b0025
●
on business
– Poorly documented
– Lack of design

33
●
Case Study
– Modernization Drivers
●
Skillset shortages (old technologies)

34
●
Case Study
●
●
Technical needs

35
●
Case Study
●
●
Technical needs
●
Business needs

36
●
Case Study
●
●
Technical needs
●
Business needs
●
Personal bias

37
●
Case Study
– Cost Reduction Strategies
●
Ordinary maintenance

38
●
Case Study
●
●
Reverse engineering

39
●
Case Study
●
●
Reverse engineering
●
Restructuring

40
●
Case Study
●
●
Reverse engineering
●
Restructuring
●
Re-engineering

41
●
Case Study
●
●
Reverse engineering
●
Restructuring
●
Re-engineering
●
Migration

42
●
Case Study
●
●
Reverse engineering
●
Restructuring
●
Re-engineering
●
Migration
●
Discard

43
●
Case Study
●
●
Reverse engineering
●
Restructuring
●
Re-engineering
●
Migration
●
Discard
●
Wrapping

44
●
Case Study
●
●
Reverse engineering
●
Restructuring
●
Re-engineering
●
Migration
●
Discard
●
Wrapping
●
Outsource?

45
●
Case Study
●
●
Reverse engineering
●
Restructuring
●
Re-engineering
●
Migration
●
Discard
●
Wrapping
●
Outsource?
●
Freeze

46
●
Case Study
●
●
Reverse engineering
●
Restructuring
●
Re-engineering
●
Migration
●
Discard
●
Wrapping
●
Outsource?
●
Freeze
●
Carry On

47
●
Case Study
●
●
Reverse engineering
●
Restructuring
●
Re-engineering
●
Migration
●
Discard
●
Wrapping
●
Outsource?
●
Freeze
●
Carry On
●
Replacement with commercial off-the-shelf software and discarding

48
●
How Do We Know?
– Measurement
●
A Method for Assessing Legacy Systems for Evolution – 1998 (by Jane
Ransom, Ian Sommerville, and Ian Warren) -
http://citeseerx.ist.psu.edu/viewdoc/download?
doi=10.1.1.128.9889&rep=rep1&type=pdf
– Legacy = business critical = cost not justifiable

49
●
How Do We Know?
– Measurement
●
– Company and project specific

50
●
How Do We Know?
– Measurement
●
– Continuously refined

51
●
How Do We Know?
– Measurement
●
– Continuously refined
– Gains depth of understanding of business

52
●
How Do We Know?
– Criteria
●
Decision Model for Legacy Systems - 1999 (by . H. Bennett, M. Ramage, and
M. Munro) - ftp://ftp.inf.puc-
rio.br/pub/docs/FomularioSolicitacoes/mariliaGFerreira-09-13-7.pdf
– Based more upon organizational points
●
Boundary: the unit of analysis

53
●
How Do We Know?
– Criteria
●
●
●
Vision: global summary of the unit

54
●
How Do We Know?
– Criteria
●
●
●
●
Logic: rationale for vision

55
●
How Do We Know?
– Criteria
●
●
●
●
●
Structure: of the organisation

56
●
How Do We Know?
– Criteria
●
●
●
●
●
●
Roles: organizational roles of people

57
●
How Do We Know?
– Criteria
●
●
●
●
●
●
●
View of information: resource analysis

58
●
How Do We Know?
– Criteria
●
●
●
●
●
●
●
●
Costs: major costs, both financial and nonfinancial

59
●
How Do We Know?
– Criteria
●
●
●
●
●
●
●
●
●
Benefits: both financial and nonfinancial

60
●
How Do We Know?
– Criteria
●
●
●
●
●
●
●
●
●
Benefits: both financial and nonfinancial
●
Risks: major sources of risk

61
●
How Do We Know?
– Structure
●
A Framework to Assess Legacy Software Systems - 2014 (by Basem Y.
Alkazemi) -
https://pdfs.semanticscholar.org/da50/7665a6c3bacb5559996bd436a9f76aa
4e5a7.pdf
– Strategies
●
Replacing

62
●
How Do We Know?
– Structure
●
Alkazemi) -
4e5a7.pdf
– Strategies
●
Replacing
●
Maintaining

63
●
How Do We Know?
– Structure
●
Alkazemi) -
4e5a7.pdf
– Strategies
●
Replacing
●
Maintaining
●
Re-architecting

64
●
How Do We Know?
– Structure
●
Alkazemi) -
4e5a7.pdf
– Strategies
●
Replacing
●
Maintaining
●
Re-architecting
●
Extending by wrapping

65
●
How Do We Know?
– Application
●
A Decisional Framework to Measure System Dimensions of Legacy Application
for Rejuvenation through Reengineering - 2011 (by Er. Anand Rajavat, Dr.
(Mrs.) Vrinda Tokekar) -
https://www.ijcaonline.org/volume16/number2/pxc3872674.pdf
– System domain
●
Customer requirements
●
Orgs strategic goals
●
Operational env
●
Risk management
i. Organizational
ii. Resource
iii.Development
iv.Personal
v. User Requirement
vi.Specialization
vii.Team
viii.Communication

66
-

67
-

68
●
Case Study
– Example Assessment
●
Step #1 - Does application meet or exceed definition of “Legacy”?
●
Answers: Yes, No, Maybe, Don’t know
– Business Critical
– Old
– Changed to meet organizational needs
– Degrades as changes made
– Maintenance cost increase as changes made
– Obsolete languages
– Poor, if any, documentation
– Inadequate data management
– Limited support capability
– Limited support capacity
– Lacks architecture to evolve to meet emerging requirements

69
●
Case Study
●
Step #1 – Technical value attribute assessment
●
Answers: Yes, No, Don’t know
– Maintainability
●
LOC
●
Control Flow
●
Cyclomatic complexity
●
Dead code fate
– Decompostability/Architecture
●
Modularity
●
% of modules with separation of concerns
●
Consumption
●
Extensibility
●
Style
●
Interoperability

70
●
Case Study
●
Step #1 – Cont’d
●
– Deterioration
●
Backlog increase
●
Defect rate increase
●
Response-time increase
●
Maintanance time per request increase
– Obsolescence
●
System age
●
Operating system version
●
Hardware version
●
Technical support availability
●
Security
●
Legality
●
System evolution required for business goals?

71
●
Case Study
●
Step #2 – Business value attribute assessment
●
– Economic value
●
Market value
●
Profitability index
●
IRR
– Data value
●
% of mission critical archives
●
% of application dependent archives
– Utility
●
Business function coverage rate
●
Actual usage frequency
●
Customer/user satisfaction metric
– Specialization
●
% of highly specialized functions
●
% of generic functions

72
●
Case Study
●
Step #3 – Organizational infrastructure attribute assessment
●
– Development & maintenance internal or outsourced?
– Technical maturity
– Commitment to training
– Skill level of system support
– Response to change

73
●
Case Study
●
Step #4 – Calculations
– Calculate all responses to 1 – 5 values (don’t know = 0)
– To easily plot on decisional matrix

74
●
Case Study
●
Step #5 – Conversion
– Convert Y, N, DK to numeric values and Avg %

75
●
Case Study
●
Step #6 – Plotting
– Display points on the decisional matrix

76
●
Superhero
– Status Granted
●
It’s YOU!

77
●
Supervillain
– Professor LOC
●
Fighting tools
– PHPLoc
– PHPmd (codesize)

78
●
The Data
– PHPLoc

79
●
The Data
– PHPmd

80
●
Ray Gun
– Docker Images

81
●
Arsenal
– 1 million commits
●
Rename Variable/Method/Class 77%
●
Extract Constant
●
Make Type Global
●
Rename Refactoring Command
●
Move/Extract Class 1%
●
Move/Extract Method 13%
●
Modify Method Parameters

●
Thank you!
– Code: https://github.com/adamculp/
Adam Culp
http://www.geekyboy.com
http://RunGeekRadio.com
Twitter @adamculp
Questions?

Release your refactoring superpower

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Ähnlich wie Release your refactoring superpower

Ähnlich wie Release your refactoring superpower (20)

Mehr von Adam Culp

Mehr von Adam Culp (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Release your refactoring superpower