TheCodeWorksForYou

GeePawHill says, "The code works for me, I don’t work for the code. If me and the code disagree about how things should be, the code loses, every time, and I win."

You're the one writing the code, so it should serve your goals—both the instrumental ones (does the software do what my employer wants?) and the terminal ones (does working on this code feel good?) You get to decide how to balance those goals—or, preferably, how to arrange things for MutualBenefit. If you don't make these decisions, who will?