|
|
|
|
|
by jamesbrady
1629 days ago
|
|
Hmm, I hear you on the first point… Perhaps I'm blinkered to roles in tech (to which this post was aimed, but not explicitly enough)? In my experience at such companies, people certainly aren't walked if they express dissatisfaction in their role – but you're right that this doesn't necessarily transfer onto roles which are less competitive. I will think about how to tighten that piece up: thanks for the feedback. On the second point, I can only congratulate you if you manage to keep everything so organised and compartmentalised! It's something I've aspired to but always fallen short of. |
|
If your boss/company values it, you'll do it. If they don't, I don't feel obligated to wrap this up before I leave. Typically, they tend to reward folks who prefer not to write good documentation and rather code features. It shouldn't be up to these folks to fix the problem their manager/company culture has by suddenly writing docs when they have to leave.
I think training someone on work you've done in the last few weeks makes sense. But beyond that - no. If my manager wants me to work solo on a project for months and doesn't want me to train someone until I announce I'm leaving, then it's the manager's headache - not mine.