Software developer fired by toxic boss without warning gets full 20 vacation days after termination letter mistake, leaves critical project unfinished

For two years, a software developer at a small company was the entire engineering department. He was not a team member; he was the team. He built most of the codebase from scratch. Then, in March, he released an update with a bug in it. It happens to every developer at some stage. But his boss didn't see it that way.

After that, the yelling became a daily ritual. The loud, regular, desultory calls of being called stupid. When the working day was over, the phone started ringing, with his boss demanding fixes that were usually the boss’s own fault. The pressure was relentless and it was taking its toll on him. He had several mental breakdowns. As a result, the quality of his code began to deteriorate.

The developer posted his story on Reddit and the internet came together to share similar incidents that happened to them.


What does research say?
Research published by the National Institutes of Health validates what he was going through. A study on toxic workplace environments and employee engagement found that harassment and bullying at work lead directly to burnout, depression and anxiety, all of which destroy a person's ability to perform. It’s close to mechanical: the worse the treatment, the worse the output, and some bosses use that declining output to justify more abuse.

"Find another job" but make it complicated
By early May, the boss said something to him that was in an awkward grey area. He didn’t want to fire him, but strongly suggested he start looking elsewhere within the next month. So the developer started applying to companies, and waited for responses.

Two weeks later, not a single conversation; there was a termination letter at his home address. No warning. No discussion. Just a letter, effective July 1st, telling him to take his remaining 20 days of vacation in June.

Understanding the fine print
This is where it got interesting. Under German labor law, an employer is only obliged to grant a full year’s annual leave if the employee has worked for more than six months in the calendar year. He hadn't crossed that threshold. In theory, that could have cost him weeks of paid time off.

But the letter of termination stated 20 days. In writing. Signed and delivered.

He wrote to his boss saying he would take his vacation immediately as the letter mentioned. However, if the boss needed help finishing up a major project that was still ongoing, he was open to having those vacation days paid out instead. It was a good trade-off.

The boss was quick to reply, dismissing the 20-day figure as a "minor spelling mistake" and saying only 6 days were really owed.

The attorney started laughing
The developer called in an attorney, a family friend, who found the case almost comically straightforward. The termination letter was legally binding as to its terms. The developer sent his boss a formal email informing him of this and rescinded his previous offer to help with the project in exchange for a payout.

Legal experts say employees often have far more rights than they realize when a termination occurs, including everything from final pay to accrued leave and what an employer puts in writing is legally powerful. Interpreting your termination paperwork is not just helpful; it can be a matter of leaving with what you earned, or leaving with nothing.

The boss had no choice but to grudgingly accept. All 20 days.

The real cost of firing the only person who knew how things worked
The developer was building a major project that was due mid-June and had been in the works since February. It wasn’t close to done mostly because the boss had been pulling him onto other tickets for months, deprioritizing it. He had never bothered to find out how the system worked. The boss's standing motto was telling: “As long as it works, I don't care.”

He had also taken out a loan to fund it.

The developer was on forced paid leave and had no incentive to help. The project was headed for failure. The boss's face said it all on the last day of work: the slow realization that the project he'd borrowed money for was about to fall apart, and the one person who could have saved it was walking out the door, completely unbothered.

The bigger lesson here
This story, which quickly resonated with workers everywhere, isn't just about one bad boss. Toxic leadership, sudden firings, and the idea that employees won’t fight back are patterns seen in workplaces across the US and beyond. The lesson is the same, whether you’re a developer or otherwise: read every document you’re given, know what you’ve earned, and never assume your employer got it right or acted in good faith.