Talk of Sergey Sergyenko, CEO at Cybergizer, at Ruby Meditation #30 Online 24.10.2020
Next conference - http://www.rubymeditation.com/
Description:
I hope that the code I write continues to be used after I die. Which is why I only ever write legacy code" - this is what Patterson mentioned on his Twitter last September. In this talk, I will define metrics and try to distinguish code from Legacy to the one that Survived. Also, I will introduce the so-called "Code Survival" refactoring approach.
Announcements and conference materials https://www.fb.me/RubyMeditation
News https://twitter.com/RubyMeditation
Photos https://www.instagram.com/RubyMeditation
The stream of Ruby conferences (not just ours) https://t.me/RubyMeditation
6. Legacy Code is code inherited
from another developer or team
which uses older technologies
that are no longer supported or
have been superceded by a newer
version. Many programmers say
that “code becomes legacy code
as soon as it’s writtern”
7. The reason that programmers think the old code is a
mess is because of a cardinal, fundamental law of
programming:
IT’S HARDER TO READ CODE
THAT TO WRITE IT
8. There are TWO KINDS of
software: the one that
people complain about and
the one that nobody uses.
12. The longer a piece of code lasts
in a codease, the
MORE VALUE it can deliver.
Customers don’t care about the
age of the code, they care about
WORKING SOFTWARE.
13. The Roman bridges of antiquity were very inefficient
structures. By modern standards, they used too much
stone, and as a result, far too much labour to build.
Over the years we have learned to build bridges more
efficiently, using fewer materials and less labour to
perform the same task.
- Tom Clancy (The Sum of All Fears)
14. Biological Systems, as a Human for
example, can’t be a legacy, b/c of
aging, but they can produce it and
measured by its Value.
HOW DO YOU
CREATE SYSTEMS
THAT SURVIVE?
HOW DO WE
CREATE SYSTEMS
THAT OUTLAST US?
19. It all comes back to one
thing: CODE SURVIVES by
providing VALUE and being
DIFFICULT TO REPLACE
THE REVENANT CODE
20. ONE PAGE PROGRAM:
RECYCLE THE CODE:
KILL AND REPLACE
CODE PERMANENTLY
SMALL THINGS ARE
GOOD
IMMUTABLE DEPLOYMENS:
NEVER UPGRADE SOFTWARE ON
AN EXISTING NODE