3 ms·
I would guess it is a combination of too much other work, too much legacy, and no one really caring about the aesthetics. Marketing guys pressuring devs for ne
by replicatorblog 17y ago
I would guess it is a combination of too much other work, too much legacy, and no one really caring about the aesthetics.
Marketing guys pressuring devs for new features. Enough late nights and you just stop caring about those details. Unless you have an ethos of good design like Apple.
- wvenable 17y agoWhen I'm rushed, I don't invent more code. If a slider already existed, wouldn't you just reuse that?
- replicatorblog 17y agoI'm thinking different parts might be owned by different teams, or they were written by the same team, but over a long period of time. We have a lot of UI issues like this, in a 100 person company. I imagine the bureaucracy of a place like Adobe could be hard to move.
- windsurfer 17y agoEspecially when they don't have any market pressure to move.
- Poiesis 17y agoI've worked on products like this. Some explanations include: * Copy-paste code reuse * Existing implementations aren't in a common library location, making them hard to find/nobody knows about them * Lack of knowledge about the relevant platform built-in implementation * Corporate organization is not set up to make information sharing easy * Product team organization doesn't include a core UI assets team * Product teams organized by feature and don't communicate