3 ms·

Haha, I used to be an employee like that. You know those methodologies like DDD, that say: 'understand the business problem before coding'. Well when I was doin

Haha, I used to be an employee like that. You know those methodologies like DDD, that say: 'understand the business problem before coding'. Well when I was doing it managers would go crazy and say I should not create confusion, but start working. Once to find 6 months later that a 15 men team hasn't done anything useful ... In all cases I can remember thinking and asking at the beginning was/would have been worth the time.

phlux 16y ago
The difference here was that the guy liked to try to be specifically obtuse and difficult. It wasn't a matter of thinking through a problem before hand - it was an exercise in proving/looking smart. Spending 5+ minutes consternating over the type of screws that came with the shelf is not "thinking ahead" :)
- bugsy 16y ago
  Sounds like he was a conscientious designer with an intuition for usability. I can relate to him, I also analyze screws and designs of trivial things. Is this really the optimal screw for this sort of task? If you didn't want this level of analysis, why the hell would you take a $150/hr engineer and have him screwing in shelves rather than call in the $12/hr maintenance man? I know the answer already. Your company thinks it is saving money by not having janitorial or secretarial staff and just have the engineers do all the menial cleaning and shelving tasks.
  - Muzza 16y ago
    > If you didn't want this level of analysis, why the hell would you take a $150/hr engineer and have him screwing in shelves rather than call in the $12/hr maintenance man? At the time of the incident with the screws, the guy was an intern...