Good code should be easy to follow with no function taking more than a minute to read and understand with meaningful names that can be trusted to do what they imply they do. Each function should ideally have 4 or less paths through the code with greater complexity being shoved into another method. Test Coverage is sexy. There is nothing that will make me hate a codebase more than when I have to dig deep down into a code base and find that one little variable that's getting set to null in some peripheral object instead of what it's supposed to be after hours of debugging.
And what did you watch on that Trinitron? Exactly. Fuck all that that resolution.
What are you really going to do with a 4K television and why is anyone going to make content at that resolution for you? No one will make content at that resolution for consumers because noone has the bandwidth to stream that kind of content. Upscaled content generally looks awful and graphics cards are always being pushed to the limit in terms of what we can render at acceptable framerates with given resolutions. Hell current gen consoles are still stuck at 30 fps at 1080p and plenty of games are pushing the hardware to the absolute limit. Even if we have 60 100 times the graphical processing power that we did ten years ago, it doesn't mean we should be using a resolution 60-100 times bigger, every improvement takes its toll(framerates, resolution, antialiasing lighting, texture quality, filtering,realworld physics offloaded to the graphics card.)
Expect your 4K monitor in a good five years or more when graphics cards are almost 20 times more powerful. Expect your 4K TV when 100Mb/s down stream fiber bundles are common place. And then barely expect it to change for a good decade after that.
We really need to know how they came up with that figure. If you have decently paid employees not able to work for 2-3 days while repaving those computers that could be a large chunk of that cost in terms of lost productivity. 3 days of 170 employees not working is almost 2 years of one employee not working. Then consider the age of the computers. For little over a third more of the cost to fix, they could get new computers, it could easily be worth it to upgrade to new computers if the original ones were old enough. The increased lifespan of new computers could alone justify the cost and the increased productivity from having up to date hardware only helps.
I have hardly ever known a mathematician who was capable of reasoning. -- Plato