3 ms·
I'm not sure how (3) could go anything like you suggest in your revised scenario. If the young hacker in question had asked about pub-sub architectures being s
by Symmetry 14y ago
I'm not sure how (3) could go anything like you suggest in your revised scenario. If the young hacker in question had asked about pub-sub architectures being slow after the engineer responsible had already taken a political position on pub-sub then the answer is going to be "of course not!". At this point admitting that pub-sub can be bad would be a big embarrassment.
The way to fix this is to get people to think of stuff like that before they've taken public positions on the issue.
- ChuckMcM 14y agoMy experience has been that generally, even the most egotistical programmer, will listen to someone. Finding out who that is, and then working your way backward to someone who will listen can be a useful strategy. The point I was trying to make is that you can make change happen in highly political environments if you're willing to not get all the glory (and sometimes any glory). "The way to fix this is to get people to think of stuff like that before they've taken public positions on the issue." Absolutely great advice. The challenge some times is know what they are thinking before changing position would cause them to lose face (respect). In Russ' post he had inherited a system that was broken, it read like those choices had been made long before he got there. I once proposed a RAID device at NetApp which had similar functionality to but a different implementation than the way it had been done. Watching the anti-body reaction on that was particularly enlightening. I wasn't so invested in the idea that I was going off and beat them about the head and shoulders with a fait accompli, and it wasn't something I could build in a couple of months worth of weekends. I decided to move on instead. Life is too short to spend it fighting the system for something which is right but ultimately not your passion.
- chris_wot 14y agoI once was in a meeting where they had implemented a solution to a problem, but the solution was totally inadequate. I had an easy fix, but they didn't understand the problem correctly. I was treated pretty poorly in the meeting. Unfortunately, I took it badly and got annoyed. I eventually managed to force in my solution, which saved quite a lot of contracts from falling through. Sadly, this caused me issues later down the line with the remarkably arrogant developers (one in particular!). In the end, I would have been better not stressing about it and focus on other things. The company was later acquired by a large storage company who managed to throw away the secret sauce and keep the dysfunction, and eventually they sold it to a certain well known virtualisation company who has now dropped the product. So in the end, it probably wasn't worth it!