2 ms·
> And why do you care? That's the employer's money and their waste. You're getting paid to code what your employer wants, why do you care if they want you to co
by kelnos 5y ago
> And why do you care? That's the employer's money and their waste. You're getting paid to code what your employer wants, why do you care if they want you to code for Google? You have the option to quit, and your employer has the option to switch to another service.
Exactly. We live in a world of limited options. "Perfect software that never fails" isn't a thing, and even "really good software that has the best support" isn't that common.
If you have a closed-source client and the company won't fix their bug, and you can't find a workaround, your only option is to search for an alternative that meets your needs (which may or may not exist), throw away a bunch of integration work, and start from scratch, possibly needing to heavily refactor or rearchitect your application. At least if the client is open source, you have one more option to consider before taking that big step.
I still get paid either way. If the project ends up being late because of problems with a dependency, that's life.