13 ms·
> Your problem is that if you put your developers ahead of your customers, you’ll end up with just the developers. This implies it's just a matter of prioritie
by jrochkind1 11y ago
> Your problem is that if you put your developers ahead of your customers, you’ll end up with just the developers.
This implies it's just a matter of priorities. In fact, it's a matter of cost. The OP admits that what he advocates "isn't easy", technically. That means it's more expensive. More developer hours, more highly-skilled developers, or both.
It is a matter of priorities in the sense that an organization needs to understand what a good product looks like and be willing to spend the money to create a good product, trusting the investment will ultimately be repaid (as the OP argues but is hardly guaranteed). But it's not avoiding "putting developers over customers", in fact they need to be spending more on developers than they are now to get a good product, they need to 'elevate' their developers further, always remembering the ultimate goal is serving users of course.
- woah 11y agoI hate to be the guy- but how about just serving some html and some css?
- jrochkind1 11y agoI dunno, what do you think are the reasons media sites aren't doing that? Ads? Tracking? What they think is a good design/UX that users will like, find easy and enjoyable to read, and associate with professionalism and credibility? (are they right or wrong?) Good UX for multi-media presentations? Social media sharing icons? Good UX for mobile? Comments features? Other stuff?
- rjaco31 11y agoBasically a little bit of everything, it's just feature bloating.