"Hi, I see you're the owner of this 6000-line mess of a component, could you answer some questions for me?"
"I don't own it, I didn't write it, and I don't understand it even slightly. I just made a one-line bug fix for one function in it a year ago and nobody has touched it since, so my name is on top of the git history."
Yeah at work I’m paid to own some components that I didn’t write and don’t entirely understand, so I figure my job is to help discover answers for the questions that arise.
I would not want to be a public maintainer though. I don’t have the patience or motivation to use my spare time for that.
"Hi, I see you're the owner of this 6000-line mess of a component, could you answer some questions for me?"
"I don't own it, I didn't write it, and I don't understand it even slightly. I just made a one-line bug fix for one function in it a year ago and nobody has touched it since, so my name is on top of the git history."
"Cool, so as the owner could you tell me..."
I'd be tempted to try to trick them into merging a small change so then they're the new owner and have to figure it out themselves.
The Passing of the Curse
Yeah at work I’m paid to own some components that I didn’t write and don’t entirely understand, so I figure my job is to help discover answers for the questions that arise.
I would not want to be a public maintainer though. I don’t have the patience or motivation to use my spare time for that.
I like this, turning software maintenance into a long-running game of tag.
I like to refer to it as the cooties ownership model. I.e. once you touch it you have cooties.
1 reply →