4 ms·

First off, recognize that it wasn't the "firm" that did this, it was an individual developer. It never should have happened, but people love to blame the big co

First off, recognize that it wasn't the "firm" that did this, it was an individual developer. It never should have happened, but people love to blame the big corporation, and they do need to take responsibility for the actions of their employees, but you should thank the manager for taking down the code so quickly. That puts you on the right footing with the manager. Things went wrong, you've taken the first step of action, now what's next. Let them show you that they are a respectable company. They don't want you bad mouthing them. If they don't play ball, then you can take out a stick and see how far it will get you, but I'd start by asking them what other actions they've taken to ensure the security of your IP, etc etc. Act as if you've assumed they've done it and if they haven't, then you can have an open discussion about what you think should happen. You can take it as an opportunity to also help them make sure something similar doesn't happen to future customers. You don't want them out of business, just this contract didn't work out.

take_me_out_pls 5y ago
Maybe you are right and I'm making wrong assumptions. The reason I make them is that the github account that published it is not the same as the one that worked for us. In fact, the repo was created by another account and the code was actually published to the repo by a different one, but all from the same contracting firm. It just difficult not to think badly about all this
- pedalpete 5y ago
  Don't misunderstand me. It is BAD! I'm thinking more about how you approach it with them. They took down the repo, so they don't have their heads completely up their *s, but having a go at the manager won't help. He did the right thing to correct the wrong thing. Working WITH him to ensure it was removed correctly, and getting him on your side is all I am suggesting.

take_me_out_pls 5y ago

Maybe you are right and I'm making wrong assumptions. The reason I make them is that the github account that published it is not the same as the one that worked for us. In fact, the repo was created by another account and the code was actually published to the repo by a different one, but all from the same contracting firm. It just difficult not to think badly about all this

pedalpete 5y ago
Don't misunderstand me. It is BAD! I'm thinking more about how you approach it with them. They took down the repo, so they don't have their heads completely up their *s, but having a go at the manager won't help. He did the right thing to correct the wrong thing. Working WITH him to ensure it was removed correctly, and getting him on your side is all I am suggesting.