3 ms·

I regularly hear a friend complain about BS like this and variants. "Why did adding a button take a week, it's just a button?!" is also very popular. Not sure w

I regularly hear a friend complain about BS like this and variants. "Why did adding a button take a week, it's just a button?!" is also very popular. Not sure what's worse, that or the recurring "that element should be 1px to the left, drop everything you're working on and fix it asap"...

silveroriole 6y ago
A funny side-effect of this that I ran into: customers who went to tortuous lengths to avoid requesting a new page or button, because they’d had that past experience of ‘just a button’ taking 2 weeks. They still wanted all the new functionality, but glued onto the existing pages/buttons because they thought it would save time! An interesting misunderstanding :)
- MBCook 6y ago
  See that all the time. It’s why you need proper requirements gathering, to get past that kind of thing.
touristtam 6y ago
Try changing the colour and getting told it isn't the same shade of red as the drawings presented by the designer on his PDF presentation.
- flukus 6y ago
  "It looks different on my iPad, we need it to look exactly the same everywhere" No, No you don't.
- detaro 6y ago
  I mean, that's totally reasonable if that's the spec (not to mention hopefully trivial to fix). Now if there's 5 drawings with different colors, or asking "what color do you want it?" leads to a 5-week email chain...
  - reaperducer 6y ago
    that's totally reasonable if that's the spec I don't think you grok what's happening. Some middle manager sees a shade of red on his screen in a PDF, and the dev is expected to reproduce the content in that shade of red. There are simply too many variables. Even if you have access to the PDF, the red will often be rendered differently by the browser than it is by the PDF engine. I've had middle managers tell me to "fix" a web site because the colors looked different on his office CRT than it did on the laptop screen of a person in another building. trivial to fix Everything is trivial when someone else has to fix it.
    - hedora 6y ago
      https://m.youtube.com/watch?v=BKorP55Aqvg https://m.youtube.com/watch?v=BKorP55Aqvg
  - Izkata 6y ago
    Oh, that's actually also pretty reasonable (sorta): https://bugs.chromium.org/p/chromium/issues/detail?id=44872 https://bugs.chromium.org/p/chromium/issues/detail?id=44872 I discovered that bug report after our designer noticed at a glance walking behind me (I use Firefox) that the colors on our site were far darker than she intended, somewhere around 2017-2018 (that bug was opened in 2010).
    - deathanatos 6y ago
      Yeesh my blood started to boil just reading that. I've left companies because of devs like that. People who just stand in the way of getting the software to do the correct thing. I do not understand what makes these people tick.
seamyb88 6y ago
I sometimes battles with myself over things like this. I code for my job and for recreation, the latter being where UI comes in. In order to get anything done in recreational programming you have to concede that you're not building an app with bells and whistles. Yet I lose so much time over $hit that does not matter. Usually aesthetics.

silveroriole 6y ago

A funny side-effect of this that I ran into: customers who went to tortuous lengths to avoid requesting a new page or button, because they’d had that past experience of ‘just a button’ taking 2 weeks. They still wanted all the new functionality, but glued onto the existing pages/buttons because they thought it would save time! An interesting misunderstanding :)

MBCook 6y ago
See that all the time. It’s why you need proper requirements gathering, to get past that kind of thing.

touristtam 6y ago

Try changing the colour and getting told it isn't the same shade of red as the drawings presented by the designer on his PDF presentation.

flukus 6y ago
"It looks different on my iPad, we need it to look exactly the same everywhere" No, No you don't.
detaro 6y ago
I mean, that's totally reasonable if that's the spec (not to mention hopefully trivial to fix). Now if there's 5 drawings with different colors, or asking "what color do you want it?" leads to a 5-week email chain...
- reaperducer 6y ago
  that's totally reasonable if that's the spec I don't think you grok what's happening. Some middle manager sees a shade of red on his screen in a PDF, and the dev is expected to reproduce the content in that shade of red. There are simply too many variables. Even if you have access to the PDF, the red will often be rendered differently by the browser than it is by the PDF engine. I've had middle managers tell me to "fix" a web site because the colors looked different on his office CRT than it did on the laptop screen of a person in another building. trivial to fix Everything is trivial when someone else has to fix it.
  - hedora 6y ago
    https://m.youtube.com/watch?v=BKorP55Aqvg https://m.youtube.com/watch?v=BKorP55Aqvg
- Izkata 6y ago
  Oh, that's actually also pretty reasonable (sorta): https://bugs.chromium.org/p/chromium/issues/detail?id=44872 https://bugs.chromium.org/p/chromium/issues/detail?id=44872 I discovered that bug report after our designer noticed at a glance walking behind me (I use Firefox) that the colors on our site were far darker than she intended, somewhere around 2017-2018 (that bug was opened in 2010).
  - deathanatos 6y ago
    Yeesh my blood started to boil just reading that. I've left companies because of devs like that. People who just stand in the way of getting the software to do the correct thing. I do not understand what makes these people tick.

seamyb88 6y ago

I sometimes battles with myself over things like this. I code for my job and for recreation, the latter being where UI comes in. In order to get anything done in recreational programming you have to concede that you're not building an app with bells and whistles. Yet I lose so much time over $hit that does not matter. Usually aesthetics.