3 ms·

Your third options sounds real good for a freelancer. He is giving you a pay-check, albeit indirectly.

• moron4hire 11y ago
  Yeah, if I calm down a little bit and try to think rationally, I start to think that way, too. I'm a little flustered right now because we've been having problems with performance on the project, problems I've been tasked to fix, but they keep pulling me off of it to firefight stuff that turns out to be the kid's fault. I'm just worried I'll end up spending all my time fixing his code and my client will wonder why the big features he expects me to build have ground to a halt. And I've been on the project for 3 years now. I'm pretty ready to move on. I'm not really getting anything of personal development out of it anymore. I've been working in VR stuff on the side and a LOT of people have expressed interest in my work. But I just don't have the momentum to do that fulltime yet.
  • hga 11y ago
    I would say you should leave. The programmer doesn't have a clue, most importantly the client doesn't have a clue, and it's seldom if ever worth the emotional, spiritual and mental toll to try to fix such a situation.
    • gorbachev 11y ago
      On the other hand, if he could get this guy straightened up, not only is that an awesome skill to possess (can you imagine working for/with someone like that, it'd be awesome), but he'd be doing his client and the bad programmer a huge favor.
  • c22 11y ago
    This is probably why he's their senior programmer--everyone else is too busy fixing his shit to appear productive while every feature he adds eventually ends up working great.