3 ms·
Seems super annoying, so I develop something and I can't even test what I've done because it's impossible to deploy to a QA environment? Wouldn't want to work
by user5994461 6y ago
Seems super annoying, so I develop something and I can't even test what I've done because it's impossible to deploy to a QA environment?
Wouldn't want to work there. Worst case scenario I leave. Best case scenario I become totally disinvested in the project/company because I can't work anyway so why care about anything? Take the salary and do as little as possible, bet every project is de facto late anyway.
By the way, what happens when the manager is away for a day or on holiday? Nobody can deploy anything?
- bob1029 6y agoWe test locally on our machines. QA is to validate that what worked locally also works for other internal employees. In our organization, we have strong discipline regarding locally validating changes before pushing up PRs. Iterating through QA usually means you don't know how to manage local development environments. We have written mocks & simulators to ensure that the local development experience very closely matches a live environment. Also, there are multiple individuals who are able to manage the build process, so we have appropriate redundancies in place. BTW, I don't think you would have to worry about working in my organization. We prefer to work with individuals who take a charitable approach to unfamiliar ideas.
- user5994461 6y agoI take a more charitable approach in job interviews than in HN messages :) I consider unlimited free access to a QA environment a requirement to develop (critical) software. Local development does not reflect the production environment. Testing/Mocking is not representative of a real database or any dependency the software relies on. Do you have QA people to test the software integration in QA or is it the developer/manager who's expected to QA after the release?