>Doesn't mean you should use those legacy/older/non-optimized approaches for new work.
>
>>In the abstract I don't disagree with you. But give the average business has anywhere from a small boatload to a truckload of legacy applications using older/non-optimized approaches, it's a reality

I'm not disagreeing with the original statement about optimistic vs pessimistic. I agree with you there.

What I'm saying is that some DBAs/developers are sometimes stuck with writing/maintaining jobs to scan parts of databases because of older approaches that might take months or years to clean up. Sad but true reality.

And even more tragic - while unusual, sometimes a developer might have to do something in "new" work to align with an older approach that's going to take a long time to sunset. Sometimes you have to plant a new weed with an older weed for a period before you can plant the actual flower. I'm dealing with that right now - the details are too bizarre to go into, but I've got to do something for a client I'd rather not do, but it's a business reality because of an existing relationship with another contractor and a third party. Stuff happens.