Engineer here. It’s like that because that’s the way it’s always been. To change it would mean retooling silk-screen printing on the D-pad, and changing the wiring underneath. And they probably use this D-pad everywhere, so someone like me will have to talk to someone else like me, and right now I have phone shyness (can’t just be an email, have to call a meeting). I’ll also have to talk to a supplier and get them to change the wiring, and Procurement won’t let me just change anything, because it gives suppliers a chance to requote a job, and they’ll ask for more money. And then I’ll have to talk to Production, because they’ll have to retrain the workers, make sure someone doesn’t stop the line because this new part doesn’t look exactly like the old part. Oh, and Quality of course, need to make sure the inspectors don’t start rejecting the new parts (just kidding, they never look at parts). Then there’s Marketing. Since this is a customer-facing part, definitely need their input. Might have to change catalogs and brochures with new pictures.
No, they just got the good brand of gummy bears in the cafeteria, I’m going to go buy a bag of those, and then fill out these forms my new boss has been asking about. New boss, new forms, same old shit.
Sounds like a proper project to me. No wonder companies keep the same stuff for way too long. If it’s not horribly broken and on fire, don’t fix it. Being slightly broken is apparently totally fine though.
Nothing personal, but that’s bullshit on the company. Rotate the entire assembly 90° to the direction where the next track arrow points right, and counter rotate the ok gel button so that it’s properly up and down. I can’t imagine a silk screen template is that engrained. There might be some mounting screw difference, but adjust that in manufacturing from your parts suppliers. No reengineering of the harness necessary. This is just pure laziness.
You have allready missed details, this would be worse than before.
For two reasons:
The customers who are used to this scheme will have to relearn the button placement, this will generate complaints, so the change will generate bad PR for the brand for years as people upgrade their car and have to relearn the controls.
If we went with your suggestion, the volume buttons would be 90 degrees off.
Yeah engineer, developer, and designer all give their input. Designer proposal is likely the most user friendly, but, changes come with real tangible engineering / development costs. Manager says “ok stick with what we have, it’s cheaper.”
I’m a software engineer and UX designer.
Being in both those roles can sometimes be incredibly frustrating. Like “yes, this is the best solution for users. It helps dev by being more future proof, using more common patterns with more readily available open source software. It will take considerable dev time so we should do it now rather than later. If we don’t do this now it will just lead to more technical debt and a worse experience”
CTO: “sounds expensive, let’s not do it”
A year later, CTO: “why is this so convoluted? Shouldn’t we have worked on these changes earlier?”
Wouldn’t it be nice if an engineer had decision making power?
Engineer here. It’s like that because that’s the way it’s always been. To change it would mean retooling silk-screen printing on the D-pad, and changing the wiring underneath. And they probably use this D-pad everywhere, so someone like me will have to talk to someone else like me, and right now I have phone shyness (can’t just be an email, have to call a meeting). I’ll also have to talk to a supplier and get them to change the wiring, and Procurement won’t let me just change anything, because it gives suppliers a chance to requote a job, and they’ll ask for more money. And then I’ll have to talk to Production, because they’ll have to retrain the workers, make sure someone doesn’t stop the line because this new part doesn’t look exactly like the old part. Oh, and Quality of course, need to make sure the inspectors don’t start rejecting the new parts (just kidding, they never look at parts). Then there’s Marketing. Since this is a customer-facing part, definitely need their input. Might have to change catalogs and brochures with new pictures.
No, they just got the good brand of gummy bears in the cafeteria, I’m going to go buy a bag of those, and then fill out these forms my new boss has been asking about. New boss, new forms, same old shit.
Sounds like a proper project to me. No wonder companies keep the same stuff for way too long. If it’s not horribly broken and on fire, don’t fix it. Being slightly broken is apparently totally fine though.
deleted by creator
Nothing personal, but that’s bullshit on the company. Rotate the entire assembly 90° to the direction where the next track arrow points right, and counter rotate the ok gel button so that it’s properly up and down. I can’t imagine a silk screen template is that engrained. There might be some mounting screw difference, but adjust that in manufacturing from your parts suppliers. No reengineering of the harness necessary. This is just pure laziness.
that’s the way it’s always been!
You have allready missed details, this would be worse than before.
For two reasons:
The customers who are used to this scheme will have to relearn the button placement, this will generate complaints, so the change will generate bad PR for the brand for years as people upgrade their car and have to relearn the controls.
If we went with your suggestion, the volume buttons would be 90 degrees off.
You mean a designer right? Developers and engineers are the ones making these weird decisions
Managers make weird decisions, engineers and developers just do what they’re told when it comes to user facing experiences.
Yeah engineer, developer, and designer all give their input. Designer proposal is likely the most user friendly, but, changes come with real tangible engineering / development costs. Manager says “ok stick with what we have, it’s cheaper.”
I’m a software engineer and UX designer.
Being in both those roles can sometimes be incredibly frustrating. Like “yes, this is the best solution for users. It helps dev by being more future proof, using more common patterns with more readily available open source software. It will take considerable dev time so we should do it now rather than later. If we don’t do this now it will just lead to more technical debt and a worse experience”
CTO: “sounds expensive, let’s not do it”
A year later, CTO: “why is this so convoluted? Shouldn’t we have worked on these changes earlier?”
suprised_pikachu.jpg
As an engineer with a boss I really do not like and who makes moronic decisions ALL the time (that I then have to go along with), I agree