Ask HN: advice for working with a bad programmer
We're working on two different applications which communicate through different API calls. The problem is the other guy has really bad coding practices(doesn't use version control, doesn't know how to debug code, writes overly complex code for simple things, ...), takes a lot of time to get something done and when he does the api doesn't work as intended. As my services depend on him, this results in a big waste of time.
I tried suggesting him to improve in person and by email but I keep getting ignored.
The project manager(and founder) doesn't seem to care or realize what's happening because I don't see him telling anything about this to the programmer.
It's an interesting startup, good networking possibilities, good pay, work at home, twenty hours per week so it's hard for me to quit. We both work at home.
What would you do in this situation?
1. Deal with it. If you're being paid well, like working from home and nobody is (yet) concerned that it's taking you longer to deliver because of the other developer's shortcomings, you can learn to live with the situation and do your best to be as productive as possible in the 20 hours you're being paid for each week.
2. Quit. If your happiness ultimately requires that you work with competent people, you should seek out other opportunities that will give you the ability to do so.
If they won't, you should probably just quit. You will be carrying this individual for a long time, and it may take a third or fourth person coming on before it becomes more obvious that this individual is a problem.
In situations like this, the founders should have hired on a technical lead and have both of you reporting to the lead. Or one of them should be technical enough to be the lead. I would suggest looking for opportunities that are managed in this way in the future.
Either, make them leave, or make them want to improve themselves.
"Because he's bad at his job" is not a defence for any kind of abuse.