Wow, 9 answers in short order, very much appreciated.
There are differing opinions here, most of which I have been going over myself before posting - I actually already walked away, but wanted to be absolutely sure I hadn't missed a great opportunity by being too up my rear end.
On a couple of points:
They wanted to contract me for expertise in a niche platform they don't have - the product expertise is a nice plus for them.
The 'reverse engineering of the schema' is just connecting up (eg. via normal db/erd tools) and working out the schema and what the fields do. Then mapping and extracting via (eg.) an SQL connection which will remain in place. There is nothing innovative in there, but the schema is presumably as proprietary as the code? It is part of the application.
There are no extended export capabilities (afaik) in the FromCo application, just the normal reporting, and that's not what they want me to use anyway.
I figured it goes on all the time, but I wasn't sure as to the legal okness of this particular approach, or my exposure as a non-employee.
Although the product is still in development, the end client is using a version from my era at FromCo.
The getting a lawyer to go over the contract advice is sound, but there has been enough conflicting opinion here for me to remain uncomfortable ethically about the contract, particularly as regards my history with FromCo, so I'm going to stay out I think, though will take on board any further discussion.
Thank you all.
There are differing opinions here, most of which I have been going over myself before posting - I actually already walked away, but wanted to be absolutely sure I hadn't missed a great opportunity by being too up my rear end.
On a couple of points:
They wanted to contract me for expertise in a niche platform they don't have - the product expertise is a nice plus for them.
The 'reverse engineering of the schema' is just connecting up (eg. via normal db/erd tools) and working out the schema and what the fields do. Then mapping and extracting via (eg.) an SQL connection which will remain in place. There is nothing innovative in there, but the schema is presumably as proprietary as the code? It is part of the application.
There are no extended export capabilities (afaik) in the FromCo application, just the normal reporting, and that's not what they want me to use anyway.
I figured it goes on all the time, but I wasn't sure as to the legal okness of this particular approach, or my exposure as a non-employee.
Although the product is still in development, the end client is using a version from my era at FromCo.
The getting a lawyer to go over the contract advice is sound, but there has been enough conflicting opinion here for me to remain uncomfortable ethically about the contract, particularly as regards my history with FromCo, so I'm going to stay out I think, though will take on board any further discussion.
Thank you all.



Comment