Hacker News new | ask | show | jobs
by touristtam 1449 days ago
Argue that legacy system needs to be kicked off the kerb, that you do not wish to be the sole owner of these. By making it someone else's problem you will share the pain, and therefore add a voice of "discontent" to change.

For time management, there isn't any silver bullet, and we just have to work around hard constraints. Btw one solution might work for you, but not necessarily.

2 comments

> legacy system needs to be kicked off the kerb, that you do not wish to be the sole owner of these

I'd agree. I'd love to say this to people. I'm in a similar position in that I need to offload legacy production code to my successor, but due to successive company policies of cutting staff to basically 1-person-1-job I have literally no-one to hand over to. It's going to get messy...

This can be a gamble.

Until the migration is eventually fully complete (which can really drag on forever in some places) they will be in a way worse position to argue for other people spending time on understanding it. Basically no one will be motivated in doing so.