Hell for developers

The system I'm developing is depending on an image generating application, that is generating thousands of unique images per day. The kicker? The application is a single thread wpf application hosted on two desktop computers, behind a load balancer, in our server room... because 'it can't be converted to a service'...

Found out today that the company wants to hire the consultant that thinks that unit testing is a waste of time, CI and code coverage metrics are useless, DI is mumbo-jumbo. But 500+ line procedural methods are fine, you just start the method with a small essay of a comment on what it does...

A colleague figured he would fix our performance issues by replacing .Count() > 0 statements with .Any()

Perfect idea, except he just did a replace all.

But hey,
var totalCount = items.Any();
Might have its uses.