I think it would be hard to master programming without developing such an attachment -- emotion is what motivates people. You've become emotionally attached to

I think it would be hard to master programming without developing such an attachment -- emotion is what motivates people. You've become emotionally attached to the operation of the program, it seems, in being "simple and effective". I suppose then you have mastered, or are mastering, a kind of engineering. It isn't clear to me why working with you would be any more or less pleasant than the other kind of a person. Sometimes a master of one craft is needed to repair/supplement the oversights of another. Arguments you cause about the "efficiency" of some approach are no doubt a problem, and may injure the long-run intelligibility of the project. Those who master programming as such are the frontal lobes of teams who master engineering -- providing a global, planning, synthesizing, rationalizing perspective which keeps the program intelligible.