I Don't Always Test My Code, but When I Do It's in Production!

I thought I'd solved the Memphis Forward site problem. But I ended up rewriting the code to get to the same problem from a different direction. The issue was passing the information from the browser to the server via socket over a port (ports being blocked on the shared hosting site that has our stuff). So I rewrote it utilizing a restful endpoint...which it turns out is also tied to a port so yeah. And the python I looked into looks like it handles the problem the same way. So will I be forced to use php after all? It's looking that way. I represented my team in a somewhat emergency deployment to production tonight. I've mentioned how the test database is broken (should be fixed next week, making it down for a total of two weeks). Well, there was an issue with something b2b was trying to push to production not working right (ended up that the initial requirements were changed). So I found what was causing that (only one parameter being set and saved to the database) so I made a fix that set all of them (it was initially supposed to only be the one). Never been able to test it because of the test database being down and all. But Lynn wanted to try it (it was a small change) and push it to production quickly and if it didn't end up working, we'd roll it back. So I came home and was on the call. Someone else always does the actual production deployments for us. But I was there to help walk him through it. Though he didn't need any walking through so I really didn't do anything except host the call (but that's something special, right?). Also, he ended up running late in traffic so the rest of us were on the phone waiting for almost an hour before he got on. Anyway, it was deployed, it didn't work and we rolled it back. Ended up nothing was getting saved so it was probably an exception getting thrown somehow. Well, that's what happens when you never get a chance to even run the code first. Anyway, that's that.