[keldaris]

> I don't care if a CPU is running at 80% consuming more electricity when I could work for a week and make it do the same job at idle. It's an inefficient use of my time. That same week's worth of effort could be spent delivering more value than the $10k server + $500/year operating cost. (I'm paid less than that, but I deliver more value to my company than my paycheck.) Also, risk. If it works now, it may not after I spend a week mucking with it.

That attitude is perfectly fine and reasonable until people start applying it to user-facing software. That's how you get software that wastes millions of user hours and immense amounts of energy just so some programmer could "deliver more value" and, sadly, that applies to an alarming proportion of modern software.

[notme77]

Those same users are probably benefitting from the other thing I did that delivered value to my company. It has value for the company because it has value, directly or indirectly, for the customer. Eventually, it'll sort itself out with competition.

Ultimately, my work is dictated by what the customers whine about. If they make more noise over missing feature X than slow feature Y, X gets my time.

[keldaris]

> Those same users are probably benefitting from the other thing I did that delivered value to my company. It has value for the company because it has value, directly or indirectly, for the customer. Eventually, it'll sort itself out with competition.

This kind of oversimplified faith in the idealized notion of the free market completely ignores the myriad of externalities that systematically distort software competition. General arguments aside, it suffices to go through almost any set of software niches to note that the dominant products in most of them are dominant for reasons that have nothing whatsoever (and are frequently inversely correlated with) any reasonable sense of technical merit or even economic value produced (for the users) in the present (though many of them were once upon a time arguably the best in their respective niche).

> Ultimately, my work is dictated by what the customers whine about. If they make more noise over missing feature X than slow feature Y, X gets my time.

Non-technical users rarely articulate performance-related concerns, but that doesn't mean they don't have them. In my experience, if you have prolonged free form conversations with them, they will often voice impressions of the software in question getting slower and less reliable overall, whereas targeted questionnaires and focus groups will tend to laser in on specific features simply because those are much easier to articulate. Also, bad software is so common by now that some people can't even imagine that there isn't actually any sane technical reason for, say, Photoshop to take almost 10 seconds to open a simple image file. That doesn't mean you're not wasting their time, money and energy.

[layoutIfNeeded]

You see, that's the difference between a craftsman and a corporate drone.