4 ms·
Even the best runbook culture can still trip over human nature. I have a co-worker who takes it upon himself to "discover" and "fix" things that are broken, bu
by cratermoon 6y ago
Even the best runbook culture can still trip over human nature.
I have a co-worker who takes it upon himself to "discover" and "fix" things that are broken, but to him, "broken" means "I don't understand this, or it's doing it in a way I don't like". He won't even read a runbook if it exists. What he will do is create a ticket, assign it to himself, and then declare it done when he's met whatever criteria he set for himself.
That's bad enough, but once he's done changing it to suit his personal tastes, that's usually it. He may, at times, write up something that more or less just reproduces what he did, but without any motivating context or explanation of the reasoning for going from A to B.
He strikes me as one of those "I'm trying to make myself irreplaceable by being the only person who understands this" people. In three years, management has nothing but praise for his "productivity", and they didn't even raise much of an eyebrow when he claimed "closed N tickets" as one of his accomplishments at his last yearly review.
- bombcar 6y agoThere's a surprising number of MAJOR CHANGES done at big name companies (changing programming language is a common one) because a senior engineer or other high ranking person didn't understand the existing one.
- 908B64B197 6y agoOften it gives a convenient excuse for a (much needed) re-write.
- imoverclocked 6y agoWithout understanding the current failings, an org is doomed to rewrite the same thing.
- cratermoon 6y agoIf there's a compelling need for a rewrite, then changing languages is acceptable. If the case can be made, and the rewrite is done with due attention to the pitfalls[1], then do it. If there's a sort of vague "this sucks, let's rewrite in language <foo> which is objectively better in my opinion", that's bad. [1] https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/ https://www.joelonsoftware.com/2000/04/06/things-you-should-...
- subpixel 6y agoI worked with an engineering leader who spent a year trying to recreate, via an e-signing company’s API, the same company’s off the self embeddable document product, because he didn’t understand that it would have solved the problem.
- cratermoon 6y agoOh yes, this same co-worker doesn't use existing libraries the organization has. The best I can say about that is that he hasn't bothered to learn them. I found another instance of his duplication of work just last recently. I don't know how often he's written the same functionality because he didn't like or understand the existing code. He may believe that LOC is a good productivity measurement.
- Rule35 6y agoPerhaps they've transcended and work only for themselves? I know a guy who spent years writing complex threading code, but well written, for the simplest things. Turns out it was just practice because we were underutilizing him. When we gave him more (better) work he did it without flourishes but brought the skill from his tinkering. Sometimes good corporate behavior even looks like sabotage. An old dev said something along the lines of "We reinvent everything because our review process rewards it. If you try to use an existing library you go to a review process and people undercut you and try to convince management you should use their pet library, only available on their stack of course, and you never get anything done. Instead just rewrite the bit you need and move on. Do what rewards you, not what you think is 'right'. Let the company decide." And indeed, some companies favor this because they can't get their process under control. Once I was in a design meeting and my product had a config file (10-50 settings, tops) which got noticed. A senior architect said I should put it in a database ... and that the DB should be Oracle. "Nothing else is as stable or respected." I argued a bit but when it was clear he was huffing and setting himself up for a win-by-authority I folded, left, and removed the config file so I never had to speak to that guy again. Now you set any changes in environment variables. It literally would have quadrupled the work and footprint to add Oracle, or any DB. Had it been a compliance-req and not an idiot-req I'd have used SQLite or something, but Oracle was insanity. And by contract with our customers, had we used it, we'd have had to hire a specific Oracle DBA who of course would do no useful work in any other area. Years later though, a friend asked me what would have paid better and I had to admit that I'd probably have gotten my promotion a project earlier by pointing to the big expensive parts we used.
- tayo42 6y agoI understand the scenario, part of me wonders why I it's so hard to understand in the first place
- bg4 6y ago> I have a co-worker who takes it upon himself to "discover" and "fix" things that are broken, but to him, "broken" means "I don't understand this, or it's doing it in a way I don't like" That's a dangerous individual who should be coached (Lesson 1: Chesterton's Fence), or fired.
- cratermoon 6y agoHe was a contract-to-hire, and should have been let go at the end of the contract, if not before.
- teddyh 6y ago> What he will do is create a ticket, assign it to himself, and then declare it done when he's met whatever criteria he set for himself. […] he claimed "closed N tickets" as one of his accomplishments at his last yearly review. So developers at your workplace can create tickets themselves, solve the tickets themselves, and then use the number of tickets solved as a measure of productivity? Only one word suffices to describe this situation: Minivan. https://dilbert.com/strip/1995-11-13 https://dilbert.com/strip/1995-11-13
- cratermoon 6y agoYes, EXACTLY. It isn't an official measure of productivity, but he managed to finesse it. There are management issues. There was some skepticism over this attempt to inflate productivity, but imho the response was overly forgiving and credulous. Something along the lines of, "well, he's a good developer, we aren't going to give him full credit for this, but he probably didn't create makework for himself". If he had reported to me, that probably would have led to downgrading his review and some minor disciplinary action for shenanigans.