Root Cause? Yer Mama Didn’t Raise You Right!
Whoa, people! Two whole days, and no fresh new posts at all?!? Whazzzup with that??!
…
Lemme stir it up a bit. There’s been a lot of posts here about bad office politics at HPE, mostly-probably caused by “forced distribution reviews” causing much eating of the dogs, by the dogs, and for the dogs, in a dog-eat-dog world. Make the other doggies look doggone bad, so that they’ll get laid off first!
…
Well anyway, what I’ve seen at the intersection of hardware, software, and firmware, design in general, is the engineers don’t do a good job of commenting their code, so that only THEY can fix it. Job security. That’s been mentioned here before. What has NOT been mentioned here before, is this: All the other rein-engineers who don’t want to play nicely with You-dolf the scapedeer engineer, will, after you get their uncommented lousy spaghetti code to work much better, spew a bunch of buzzwords at you, and, since you cannot explain, down to the molecular or atomic-physics level, WHY your new code works much better, you are then accused of “not having found the true root cause”, and of issuing “band-aide fixes”. Y’all been there, done that?
So my favorite fantasy is to talk back at the design review: “Well, the root cause is that we’re dealing here with lousy code that you inherited from lousy code-writers, and now you’ve added yet twice the lice on top of the old lousiness! And if you want yet a deeper root cause than that, I do firmly believe that it is that yer Mama didn’t raise you right!”
…
Has anyone tried that, and if so, what were the results?