| ▲ | roosterIllusi0n 18 hours ago | |||||||
Let's not gaslight ourselves. This guy was clear. The CEO who knows the least about anything shouldn't be changing timelines. The real solution is to fire the CEO and hire another 1500 engineers as that would greatly increase shareholder value at no additional cost. The second best solution is to just reiterate your original timeline and say NO(even if you do it quietly) when anyone tries to change it. If they keep meddling and trying to get you to work off hours, let them lay you off. The important thing to remember is a CEO and execs are helpless. Don't sacrifice yourself to shield them from their own mistakes and incompetence. If they miss the deadline, they just spin another lie to the customers. To this developer, this work was the most important work of his life. To the ceo, firing him before anything is finished and spinning a lie to customers is just another tuesday. | ||||||||
| ▲ | mcv 16 hours ago | parent [-] | |||||||
Absolutely. Sometimes executives need to feel the impact of their own poor decisions. Do not accept timelines from people who have no idea of the issues. If they fire you, they're firing the person who best understands their code. Don't let them bully you. | ||||||||
| ||||||||