Oh yes, legacy is the best place to learn. You replace something that's 'working' with something that keeps working but better. You write tests against a workin

Oh yes, legacy is the best place to learn. You replace something that's 'working' with something that keeps working but better. You write tests against a working system. The thing is already giving value, so you don't have to worry about that. And usually the problems are more and more complex as the code 'matures' so challenge. I don't like working on big greenfield projects. Give me a somehow working big ball of mud codebase to steer and I'm a happy man.