Quote:
Originally Posted by activeStick
OR they don't even have a test environment for that product (or an environment wasn't available), so they decided it'd be okay to test directly in production. It's concerning how often I hear this from clients during business development chats. "Things seem to work fine this way".
|
Yeah, continuous delivery doesn't mean just shipping code directly to prod and hoping it works lol.
I've worked at places where the prod deploy method was for the dev to use an FTP window to drag and drop the files from his computer to prod. Not even any version control!
I worked on one product where the build process was broken and I had to manually compile individual files and copy them up to the right place on the server. They paid for that extra time but wouldn't pay me to fix the build.
Heck one product I had to use a diff utility to copy/paste the changes to a massive single file perl script to have the new functionality but maintain the prod-specific tweaks. Brutal, but the fact it worked made them not want to spend any money on improving the process.