Learn how best practices to get a legacy project back on track to success

2. What I am gonna hear listen?

3. Legacy
Symptoms
No one knows
No documentation
Things works “as-is”, don’t touch

4. No time for new features
Can’t recover fast from down time
Bugs slip into production
Procastinate or entirely avoid new deployments
Legacy
Symptoms

5. Inadequate software architecture
Non testable code / Not tested
Manual processes
Team discipline / professionality
Poisoned culture
Legacy
Causes

6. Lack of competitiveness
Less revenue
Less profit
Legacy
Results

7. What is not defined cannot be measured.
What is not measured, cannot be improved.
What is not improved, is always degraded.
“
”Lord Kelvin

8. DISCLAIMER
Each team is a world,
each client a universe.
There is no single success recipe.

9. Technical Best Practices

11. Right sizing issues
Issue as unit of work
One issue / One branch
Issue as doc of the problem
Focused
Divide and conquer
Max 2d scope ~300 lines

12. 1) Dev starts working on issue X
2) Dev finds a small bug unrelated to X and
fixes it within X
3) Dev continues working on X
1) Dev starts working on issue X
2) Dev finds a small bug Y unrelated to X
3) Dev opens a new issue for Y and
continues work on X
1) Dev starts working on issue X
2) Dev finds a small bug Y unrelated to X
3) Dev opens a new issue for Y
4) Dev switches to Y …. merges to master
5) Merge master into X
6) Continue working on X

13. Commits
Commit message as doc
Atomic in purpose
Commits should tell a story
https://about.futurelearn.com/blog/telling-stories-with-your-git-history
https://www.slideshare.net/joelchippindale/telling-stories-through-your-commits

14. Peer review all contributions
Use pull requests
Shared responsibility
Remember: Max 2d scope ~300 lines

15. Avoid comments in code
Keep docs in code

16. Documenting
Issues/Features
Commits
Pull Requests
How to build
How to run
Software architecture
Architectural decisions
Code meta data
with context

18. Automate

19. Build with ease

23. Trunk Based Development
Forked repositories
Short-lived feature branches (2d max)
All contributions peer reviwed
All contributions CI built before merging
Main repository only master (trunk)
Master always release readyhttps://trunkbaseddevelopment.com

27. Atomated merging
Run CI against merge(master, PR)
https://bors.tech/

28. Automated changelog
github-changelog-generator
https://github.com/github-changelog-generator/github-changelog-generator

30. Testability

33. Production Smoke Tests
Don’t alter other user’s environment

35. Architecture

37. Microservices Rant
SOA vs MS
SRP: Business level vs Technical level
Responsibility: Department vs Dev team
ESB vs Service Mesh
Resilient & Scalable

39. Use VCS
Capture team knowledge
Make knowledge searchable and context aware
Automate builds, releases and deployments
Create tests
Deploy smoke tests
Monitor and alert
Prepare production for failure and change
WRAPUP

41. THANKS
@dcerecedo
Daniel Cerecedo

42. We transform the World
building better software
with a startup mindset