I think there’s a kernel of truth in this post, it does make the correct observation that 2 weeks is not always the correct time. I think it’s deeper than that, there are multiple correct times that are incompatible with each other.
This is because there are multiple ways you are integrated into the company and the correct wind-down period for each is different. A few months to find and train a replacement, a few weeks to document all your organizational knowledge, a few days to say goodbye to your colleagues - and for companies with valuable secrets it’s obviously desirable that your access to their information is revoked instantaneously.
Ultimately, for a senior software engineer, quitting is just complicated. I think if you want to try a variable-length notice of resignation you need to find someone in the chain of command you trust to be level-headed and pragmatic, approach them with your thoughts of leaving, and (matching their level-headedness and pragmatism) discuss how to make your departure as successful and effective for the company as possible - maybe you start documenting knowledge now, wind down day-to-day fire-fighting responsibilities a week from now, and formally announce your two weeks notice a week after that.
But you have to go into that discussion prepared to roll with the decisions they make, all the way from “immediate dismissal and escort from the building” to “they do not want you to quit and try to offer you more money or different responsibilities”. If that gives you trepidation, maybe it’s better to stick to the business standard of two weeks notice. It’s not optimal, but it is well-trodden ground.
This is because there are multiple ways you are integrated into the company and the correct wind-down period for each is different. A few months to find and train a replacement, a few weeks to document all your organizational knowledge, a few days to say goodbye to your colleagues - and for companies with valuable secrets it’s obviously desirable that your access to their information is revoked instantaneously.
Ultimately, for a senior software engineer, quitting is just complicated. I think if you want to try a variable-length notice of resignation you need to find someone in the chain of command you trust to be level-headed and pragmatic, approach them with your thoughts of leaving, and (matching their level-headedness and pragmatism) discuss how to make your departure as successful and effective for the company as possible - maybe you start documenting knowledge now, wind down day-to-day fire-fighting responsibilities a week from now, and formally announce your two weeks notice a week after that.
But you have to go into that discussion prepared to roll with the decisions they make, all the way from “immediate dismissal and escort from the building” to “they do not want you to quit and try to offer you more money or different responsibilities”. If that gives you trepidation, maybe it’s better to stick to the business standard of two weeks notice. It’s not optimal, but it is well-trodden ground.