> I guess the source of the confusion is that you didn't specify what the sabotage actually is. I mean, deleting all your code before leaving is sabotage. Leaving without notice isn't. What did you have in mind when you wrote that?
There are three main sections in the article:
- Your reasons for leaving shouldn’t be a surprise to your boss
- Match your notice period to the handover period
- Set the team up to flourish without you
The "don't sabotage" subsection is under the "Set the team up to flourish without you" section, not the "Match your notice period to the handover period" section.
Seems fairly common sense that the author did not intend to conflate lack of notice with sabotage, considering that the subject of sabotage is completely independent and separate from the section relating to notice.
There are three main sections in the article:
- Your reasons for leaving shouldn’t be a surprise to your boss
- Match your notice period to the handover period
- Set the team up to flourish without you
The "don't sabotage" subsection is under the "Set the team up to flourish without you" section, not the "Match your notice period to the handover period" section.
Seems fairly common sense that the author did not intend to conflate lack of notice with sabotage, considering that the subject of sabotage is completely independent and separate from the section relating to notice.