This question already has an answer here:
- How do I survive a failed project? 5 answers
As the title say, I was assigned to a project which other guy was managing 2 months ago, I was supposed to help him in whatever he needed.
A few weeks back the guy just straight out quitted, leaving me the as the unspoken 'lead' of project with the added pressure of a close date in which to show the project working and two new hires in the same project, which skills are orthogonal to mine..
The thing is I'm WAY way out of my comfort zone, I'm expected to do stuff in a short period of time that I don't even have a remote idea on how to do.
The project was (is) all kinds of f' up.. big codebase, I fixed most of the bugs I could, but now the problems left are from functionality, not bugs, ie: Its not working as intended. I even think this project is an open problem in the area where it is from..
Add it to boot that we are testing the code in the void and not where it should be (a machine) and I'm expected it to JUST WORK because and I quote 'How can it not work?'. And we don't even have the proper tools!
My boss even lied about a functionality to the client that wasn't implemented (its not even working now) at the time, and even showed it "working"..
So I have a few questions on what is going on and what to do.
- Am I being set up to fail as a scapegoat?
- Should I talk to my boss and say I'm not capable of pushing through this project? (I don't think anyone in this startup is, and I think he will insist I keep trying)
- Should I just quit? (Same as above)
And by the way I wouldn't even call myself a jr dev..
I'm really stressed.
Sorry if the exposition is all over the place. And thanks for reading :).