3 ms·
I have a similar experience in industry (software development) that I relive weekly, but I never learn. When I help someone solve a problem, I like to show the
by dotancohen 4y ago
I have a similar experience in industry (software development) that I relive weekly, but I never learn.
When I help someone solve a problem, I like to show them how I got to the solution. In the end, my hour invested was "we did it together" and not appreciated by anyone, least of all the manager. But on the few occasions that I just bang out a function quickly for somebody because I don't have the time, I'm hailed as a lifesaver critical to the business and my name is mentioned in the Daily Standup the next day.
Explaining how we work trivializes our work. It's better to remain mysterious.
- vmilner 4y agoMr. Jabez Wilson laughed heavily. “Well, I never!” said he. “I thought at first that you had done something clever, but I see that there was nothing in it after all.” “I begin to think, Watson,” said Holmes, “that I make a mistake in explaining. ‘Omne ignotum pro magnifico,’ you know, and my poor little reputation, such as it is, will suffer shipwreck if I am so candid. - "The Red Headed League", (The Adventures of Sherlock Holmes)
- dotancohen 4y agoThat's brilliant. This time, maybe I've learned. Thank you.
- NoWizards 4y agoJust remember: Dev works in mysterious ways.
- abecedarius 4y agoReminds me of a favorite compliment about some of my code: a friend told me he didn't realize the job it did was tricky, after reading it, until later he implemented the same thing.
- sitkack 4y agoI had a manager take my 500 lines and turn in into 1500 lines. He said it looked too-simple and that it needs to be more complex to be accepted by the other teams.