5 ms·
I think it’s less an engineering culture issue than a management one. Do you reward people based on number of features, meeting rapid deadlines, quality, or som
by Retric 4y ago
I think it’s less an engineering culture issue than a management one. Do you reward people based on number of features, meeting rapid deadlines, quality, or something else like customer satisfaction?
People respond to an organizations actual priorities not whatever platitudes people toss out. If you want quality you need to sacrifice something even if
long term results improve in the short term quality takes time.
- wpietri 4y agoExactly. I recall one place where an exec pushed for something to be completed in a too-short timeframe. It launched on the schedule he announced to his higher-ups, so he was promoted and moved elsewhere. Woe be to the exec who inherited the project, though, as the code was basically a mound of turds wrapped in Christmas paper. And the team, of course, was fractured and burnt out. The cherry on top was watching the ladder-climber throw a lunch to thank the team; their reward for hundreds of hours of grueling overtime was lukewarm Chinese food dished out of large aluminum bins in a conference room. Plus $50 gift cards! This was a long time ago, but I still think about it as a moment when I learned what POSIWID really meant.
- tjrDL6MjB2Zwwa 4y agoheh, what is POSIWID?
- wpietri 4y agohttps://en.wikipedia.org/wiki/The_purpose_of_a_system_is_what_it_does https://en.wikipedia.org/wiki/The_purpose_of_a_system_is_wha...