The real reason was not his fatigue after coding complex things. The real reason was his freelance project. Each evening he resold what he learned from teammates and earned 2x more than teammates. His mediocre performance was not a big problem itself. The problem was the conflict of interests.
Some colleagues felt friction with the team goals and pointed to our principles. So he needed to protect his lucrative status quo and started a tacit war against the principles. He started backtalk to solicit others to violate Code of Ethics and the Principles. He said the Principles are slavery, and the company do not follow them. Now, his work become to explain others why loyal teammates and company are immoral and deserves to be cheated.
Those who wanted more comfort quickly become his friends to avoid responsibility and hard work. Here is a team maximizing their benefits and minimizing efforts and risks to be fired. They had 2 lives - one was to show to others about hard problems they struggle to solve which none can understand with blurred stories. And another life was messing code and gossips against loyal to the company colleagues. They had strong incentives to sabotage interviews and newcomers to ensure they are irreplaceable.
They were proud of their ability to take advantage over the company. They felt like: Now, the company is the slave and we are the rules.
So we have the Long hour rule and we fire for failure to report on a conflict of interests or backtalk/gossips.
THE LONG HOURS RULE
We work long hours and often over weekends. Why one would work short hours?
ether is not committed to change the world with a product or
have a side project and conflict of interest
Here is how Long hour rule detect the conflict early at the onboarding process:
Learnings 2
1
I am aware that side projects can be a reason to attack the company
👍
105
Show 85 more
2
I will report any discussion or solicitation to work on side projects
👍
104
Show 84 more
3
I will immediately report any potential conflict of interest
👍
104
Show 84 more
There are no rows in this table
Want to print your doc? This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (