3 ms·
They are paying you to do a full-time job, so do a full-time job. No less, no more, and record your time carefully. Remind people, if necessary, that retaliat
by notacoward 13y ago
They are paying you to do a full-time job, so do a full-time job. No less, no more, and record your time carefully. Remind people, if necessary, that retaliatory termination of someone who is fulfilling their employment contract is illegal. Do what you can to keep that kind of talk from going up the chain any further than necessary - ideally only to your immediate and somewhat sympathetic superior.
In "extra" time, start Plan B. Find the parts of the code that might be usable for another project (possibly this one's successor). Make sure their interfaces and dependencies make that easier - which is good software engineering anyway, and can be justified as such if you don't want to explain the real reason. That way you and your employer will both be able to extract maximum benefit from the project when it does fail, helping you both to survive the aftermath.
You will be criticized for not committing enough to the project. You might even be blamed for its failure. It's very unlikely that you'll ever get any credit for helping the phoenix rise from the ashes. That sucks, but it's a bad situation all around and you have a duty to try if that's what you think is best for the company in the long term.
(P.S. To be perfectly honest, I'd already be out of there if I felt that way about a project, but that's the sort of advice the OP was explicitly not seeking.)