> This is killing me. You should absolutely not continue doing something that is literally or figuratively killing you. > If so, how do you deal with it? Psyc

> This is killing me. You should absolutely not continue doing something that is literally or figuratively killing you. > If so, how do you deal with it? Psychologically and physically. Handling shitty code doesn't affect me mentally and honestly I don't see how it could affect anyone physically. It's not like it causes you nausea or stomach pains, is it? However, feeling that my talents are wasted negatively affects my mood. I would not stand "duct taping" someone's trash unless I were given the authority to refactor and fix the underlying problems with it. Bottom line is that you should leave jobs that make you feel bad. I will share a contrarian experience I had. I once had to maintain the tcp/ip stack for an esoteric device running Linux. The stack was insanely complicated, with C code calling ksh scripts, etc. I was able the code's authors why it was designed this way: Because Linux doesn't let you assign more than one ip address to an interface. Except it does... The architect didn't want to believe me when I told him that Linux has had this feature for over two decades. Eventually he realized I was right and apologized. So, all code is written the way it is for a reason, but that reason may not be a good reason.