How to rewrite legacy 🏚️ system without PAIN! 🏘️

Story about taking over a legacy system created by different contractors and the recipe for how to continuously rewrite it (create a new one) without having a negative impact on existing users and company business. It’s a real-life sad story with a happy ending 😀

Welcome to the crazy world of creepy software architecture and design. The world where developers apply “learning by doing” but in a real and critical system.

What is wrong?

• Web service calls its own method by HTTP request
• Circular dependency
• Endless classes
• Project template example files
• Magic constants everywhere
• Cross DB queries
• And much more …

We have to take over system full of crap applications and services as well. It’s like a bad dream, NO! It’s like the worst nightmare!

You can have your own legacy system that has its own specific technical debts. But taking over a similar legacy system created by a different contractor would be a real disaster. It can be so…