3 ms·
>I am a maker. I build things for people to use and maintain. So you're dev ops? Jokes aside, do you really have a passion for maintaining projects? This is
by proverbialbunny 7y ago
>I am a maker. I build things for people to use and maintain.
So you're dev ops?
Jokes aside, do you really have a passion for maintaining projects? This is something I deeply struggle with and any advice on the subject I would be deeply grateful for.
I thought I could deal with it and enjoy a project in the long run if it had no bugs, so I worked on some of the code the internet runs on, where even putting in one bug would make parts of the internet go down world wide. (Which I did do btw. Sorry.) I both hated and loved that job, but in the end, even in a "bug free" code base, so maintaining it was only feature requests for the most part, I still lost passion over time.
I switched to Data Science, writing code I know will be scrapped. I write mockups to analyze data. It's a lot of fun! But to me it's just running away from the issue.
How did you gain passion for maintaining code bases? If you have a story, it would mean a lot to me. I'd love to hear it.
- dllthomas 7y agoYou don't need passion for maintaining projects to have compassion for the people who need to maintain your projects (whether or not that's also you). As you point out, though, some code actually doesn't require maintenance. But at the same time, that's not always the code you think.
- deleted 7y ago[deleted]
- hinkley 7y ago> do you really have a passion for maintaining projects? I don't. I have a passion for clearing roadblocks and that means different things at different times. Sometimes that means automation. I think you parsed that sentence in a different way than I intended. I think a legitimate handoff is part of building a tool for someone. We have people who run the gamut from rent-seeking to dropping the mic and walking away.
- proverbialbunny 7y agoI did interpret incorrectly. Thanks for the clarification.