> "Working Effectively with Legacy Code" defines legacy code as code without tests thus hard to change it easily or with confidence.

This is not a universally accepted definition. I've owned plenty of services with 95%+ unit test coverage, massive integ test suites, and synthetic canary tests that ran every minute that I would consider legacy. Plenty of AI slop today gets barfed out with 100% test coverage, but much of it is legacy from day 1.

I aggree thre are many defs. I only used that ex as it's easy to use and understand.

What would you consider legacy? (not trynna fight, just wondering what you consider as one)