Please enable JavaScript.
Coggle requires JavaScript to display documents.
Legacy code (learn (visualize a code (flame graphs, dependensies maps,…
Legacy code
learn
visualize a code
flame graphs
dependensies maps
callstacks
static code analizes
git history
git blame
issue tracker
input/ output
tech stacks
versions
libs
bugs
constraints
business and domain
how to survive :checkered_flag: :question:
change mindset
negative mindset never get you to a positive results
be brave to change
take full ovnership
it is your code
do not complain if you not going to fix it
it was created by reason
try to understand
history
motivation
bussiness logic
all adequate people
set a priorities
control refactoring
identify key priorities
share findings
document improvements
explain decisions
involve team
observe before act
change road map
it is
Old code that not run on os
Code that have no tests
not cover cases
Code that I dont understand
code that was writen not by me
unconfortable to make changes
good parts
It was sucsessful
customers use it and like features
you have a work
you could learn a lot
it is a collective result
reflection of organisation
generations of devs
it is rare 1 single dev
time distributed
sclerosis
hours of bug fixes and new features
constant changing requirements
How to avoid to become a legacy
decision logs
documentation
bugs
corner cases
tests
why we did it this way
FAIR
Forget everething and run
deprecated tech stack
The momentum