From the perspective of the devs, they have a responsibility for saying something literally wont fly anywhere, ever, saying the business is responsible for every bad decision is a complete abrogation of your responsibilities.

▲

sublinear 12 hours ago | parent [-]

Why don't you tell your boss or team something like that and see how well that flies.

The responsibility of the devs is to deliver what was asked. They can and probably do make notes of the results. So does QA. So do the other stakeholders. On their respective teams they get the same BS from everyone who isn't pleased with the outcome.

Ultimately things are on a deadline and the devs must meet requirements where the priority is not performance. It says nothing about their ability to write performant code. It says nothing about whether that performant code is even possible in a browser while meeting the approval of the dozens of people with their own agendas. It says everything about where you work.

▲

jkestner 11 hours ago | parent | next [-]

Maybe everyone’s got a different situation, but when a different department tried to put ActiveX avatars all over their site, though it offended me from a UX perspective, I was able to get higher ups to reject it by pointing out that it would shut out 20% of their customers.

We always have discussions here about how you have to learn to talk to communicate your value to clients in a language they understand. Same goes for internal communications.

▲

toast0 11 hours ago | parent | prev | next [-]

> The responsibility of the devs is to deliver what was asked.

Software development isn't factory work. And factory workers are expected to notice problems and escalate them.

Anyway, they're paying me far too much to have me turn off my brain and just check the boxes they want checked in all situations. Sometimes, checking boxes because they need to be checked is the thing to do, but usually it's not.

	▲	sublinear 8 hours ago \| parent [-]
		> Software development isn't factory work We're definitely way past the point where there is a singular definition of what "software development" is supposed to mean. I also didn't describe anything like factory work.

▲

hobs 11 hours ago | parent | prev [-]

I didn't say anything about their development abilities, what I am pointing to is their professional responsibility. If a doctor is asked by a client to cut off their arm and they say no, and the client fires them, did the doctor err? (No) This doesn't comment on their ability to do surgery.

	▲	monkey_monkey 10 hours ago \| parent [-]
		So just to check, instead of doing something you were told to, that you know is a stupid idea (after telling all concerned it's a dumb idea and being told to go ahead anyway, eg adding a crapton of video to a page), you would just resign, to protect your personal integrity?