5 ms·

I'm not so sure. Most of the web devs I have worked with over the years haven't been overly thoughtful regards UX. I'd even go as far to say that it's the least

by som 4y ago

I'm not so sure. Most of the web devs I have worked with over the years haven't been overly thoughtful regards UX. I'd even go as far to say that it's the least considered aspect of their process. "Not my job" mentality. Tho probably says more about the nature of my experience than anything else.

som 4y ago
To add to this, I absolutely believe it is the developer's role to interrogate a design (and its implementation) and feedback where appropriate.
- iostream24 4y ago
  Which one does, and doesn’t have power over a clients response to such. Insisting over and over again not being a viable strategy etc.
  - somishere 4y ago
    No doubt. But this sounds like a communication problem between two stubborn parties. If someone demands a ridiculous feature and is immune to rational compromise, then sure .. state your objection, build the feature and send an invoice. In my experience this is rarely the situation. More often its a case of the real issue not being clearly articulated, a lack of will to compromise on behalf of the implementer (as much as the annoying, ignorant client), and a general cynicism from both parties as to the role of the other.
- Beltalowda 4y ago
  I've done this, but it can be hard. Some designers can be very protective of their design, and you have to fight entire battles for something like "this white header text on a light-grey background image is almost unreadable, so I tweaked the colour a bit and added a text shadow" and other really basic no-brainers like that. I don't even have very strong opinions about design; anything is fine with me. The only part I really do have a strong opinion on is "it should be readable", and enforcing only that has been very tiresome at times.
  - somishere 4y ago
    I totally agree it's not always easy. But again I think with something like this it's about savvy communication rather than enforcement. How do you articulate a challenge to a designer that respects their role in the process? Contrast is easy, there's defined standards you can defer to. But for sure, it gets tricky where it's just a difference of opinion or priorities. Regardless, just going ahead and changing the design is probably the nuclear option. It's only going to start a war. Put the shoe on the other foot: consider same designer dropping a 2008 era jQuery snippet into your carefully constructed page to resolve an issue in the build. Not fun for anyone. Edit: I should add, I'm basing all of this on personal experience. Appreciate some situations just suck and you have to get on with it.
duxup 4y ago
> "Not my job" For many I suspect it really isn’t their job to decide otherwise if someone wants a horrible footer…
- somishere 4y ago
  For sure, but then this isn't so much about "deciding" as it's about critical implementation and basic communication. Again this is in my personal experience, but when features like this make it through it's almost always due to an oversight on behalf of multiple teams .. or severe cynicism from a dev.

by som 4y ago

som 4y ago

To add to this, I absolutely believe it is the developer's role to interrogate a design (and its implementation) and feedback where appropriate.

iostream24 4y ago
Which one does, and doesn’t have power over a clients response to such. Insisting over and over again not being a viable strategy etc.
- somishere 4y ago
  No doubt. But this sounds like a communication problem between two stubborn parties. If someone demands a ridiculous feature and is immune to rational compromise, then sure .. state your objection, build the feature and send an invoice. In my experience this is rarely the situation. More often its a case of the real issue not being clearly articulated, a lack of will to compromise on behalf of the implementer (as much as the annoying, ignorant client), and a general cynicism from both parties as to the role of the other.
Beltalowda 4y ago
I've done this, but it can be hard. Some designers can be very protective of their design, and you have to fight entire battles for something like "this white header text on a light-grey background image is almost unreadable, so I tweaked the colour a bit and added a text shadow" and other really basic no-brainers like that. I don't even have very strong opinions about design; anything is fine with me. The only part I really do have a strong opinion on is "it should be readable", and enforcing only that has been very tiresome at times.
- somishere 4y ago
  I totally agree it's not always easy. But again I think with something like this it's about savvy communication rather than enforcement. How do you articulate a challenge to a designer that respects their role in the process? Contrast is easy, there's defined standards you can defer to. But for sure, it gets tricky where it's just a difference of opinion or priorities. Regardless, just going ahead and changing the design is probably the nuclear option. It's only going to start a war. Put the shoe on the other foot: consider same designer dropping a 2008 era jQuery snippet into your carefully constructed page to resolve an issue in the build. Not fun for anyone. Edit: I should add, I'm basing all of this on personal experience. Appreciate some situations just suck and you have to get on with it.

duxup 4y ago

> "Not my job" For many I suspect it really isn’t their job to decide otherwise if someone wants a horrible footer…

somishere 4y ago
For sure, but then this isn't so much about "deciding" as it's about critical implementation and basic communication. Again this is in my personal experience, but when features like this make it through it's almost always due to an oversight on behalf of multiple teams .. or severe cynicism from a dev.