Old department demanding me to work

LegacyUser

listermint wrote: »

Did the OP not put together a hand over document before moving departments.

If not then you had to have known youd be called upon to assist.

You brought this in yourself tbh .

Was the OP not requested to put together a hand over document during the notice period before moving department.

If not then the previous manager had to have known they may end up having to call upon an ex employee to assist.

Previous manager brought this upon themself tbh .

OMM 0000

Another thing to remember, the managers in a company tend to be friends with each other. (There are exceptions of course; some managers are at each others throats).

For all we know "new manager" and "old manager" are friends, or perhaps trust each other due to years of working for the same boss.

The way to get promoted and trusted is by building relationships with people. Being difficult does not work. It never ceases to amaze me how so many tech people cannot grasp this.

Avatar MIA

Re ownership, some contracts state that practically anything developed (even after work hours, because presumably you're still benefiting from work experience etc) is their property, but I digress.

Good advice above. Clearly training up someone to use the company's software you developed and introduced is the answer.

ted1

CruelCoin wrote: »

Any product of your work done during work hours is the property of the company.

Did you write it at home or at work?

You’ll probably find that his contract includes stuff outside work hours too

osarusan

The source code is most likely their property, they can reasonably ask you to provide it.

What they can't reasonably ask you to do is continue to do the maintenance on it without making allowances for it in terms of your new schedule and responsibilities.

My advice is to go to your new manager and explain the situation and that your proposed solutions are either:

that time for you to regularly maintain it is scheduled into your new work and routine.

or that you (are allocated time to) train somebody how to maintain the software, and that person takes over the responsibility for it and you are finished with it.

The second option would probably be your preferred outcome, by the sounds of it. If that is the case, make that clear to your new boss also - you might even emphasise how much of an inconvenience it would be for everybody including your new boss if you are regularly required to disappear for maintenance, perhaps even at short notice.

jethrothe2nd

When you are moving to a new role the right thing to do is to give a proper handover before you leave your old job. The op knew when he walked away that this would cause an issue. Frankly that's unprofessional and smacks at having a petty parting shot at a manager he did not get on with.

Nothing good will come of this op. Sort it out like an adult instead of being petulant.

kurtainsider

jethrothe2nd wrote: »

When you are moving to a new role the right thing to do is to give a proper handover before you leave your old job. The op knew when he walked away that this would cause an issue. Frankly that's unprofessional and smacks at having a petty parting shot at a manager he did not get on with.

Nothing good will come of this op. Sort it out like an adult instead of being petulant.

On the other hand you could just tell him to go f**k himself.

Perhaps there is a way to progress somewhere between the 2 fairly outrageous extremes above.