Software architecture doesn't depend on modern code. It applies to any codebase, even legacy. I read this in a book once, but this job forced me to put that knowledge into practice.

Clean Architecture diagram showing separation of concerns in ASP.NET

The hard part isn't the patterns, it's translating technical skill into real problem solving. You need to communicate, align with the team, and push toward shared goals.

Soft skills are essential for developers working with legacy systems

Code alone doesn't ship features. People do.