NockerGeek (![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
nockergeek) wrote2005-06-13 04:11 pm
nockergeek) wrote2005-06-13 04:11 pm
(no subject)
What was supposed to be a silky-smooth launch on a new project, for which I prepped several days in advance, has gone not unlike having a cheese grater rubbed over my nether regions.
1) A couple of small bits of information for integrating into the client's live legacy system were overlooked. We had draft versions, and those had been working smoothly, but we don't have new live versions. In the middle of getting those now.
2) A program that had been tested successfully (or so I was told) on our draft server failed utterly on the live server. A minor program, but one that was linked in an email going out to 7000+ customers. Got it fixed halfway through the send, but still...
3) A pair of vital JavaScript controls don't work properly, but only on the main client's computer. One, because there's a bizarre interaction between Internet Explorer, Microsoft Word's "smart quote" characters, and a spellchecking library; the other, presumably because the security settings on the client's browser are too high to allow it to run.
Add to this a half-dozen or so things that should have been caught during the client's testing period 2-3 weeks ago, but weren't actually tested (despite the client repeatedly telling me, "This looks great, Rob, everything looks great"), and it's been a frustrating day. Also, since it's solely my project -- been totally on my lonesome on this one, save for a few small pieces of code (see #2 above, but I still should have double- and triple-checked it) -- there's only one person to take the blame. Doubly frustrating as I took extra time on Friday and Sunday to make it a smooth transitional process and catch as many small details as I could remember.
1) A couple of small bits of information for integrating into the client's live legacy system were overlooked. We had draft versions, and those had been working smoothly, but we don't have new live versions. In the middle of getting those now.
2) A program that had been tested successfully (or so I was told) on our draft server failed utterly on the live server. A minor program, but one that was linked in an email going out to 7000+ customers. Got it fixed halfway through the send, but still...
3) A pair of vital JavaScript controls don't work properly, but only on the main client's computer. One, because there's a bizarre interaction between Internet Explorer, Microsoft Word's "smart quote" characters, and a spellchecking library; the other, presumably because the security settings on the client's browser are too high to allow it to run.
Add to this a half-dozen or so things that should have been caught during the client's testing period 2-3 weeks ago, but weren't actually tested (despite the client repeatedly telling me, "This looks great, Rob, everything looks great"), and it's been a frustrating day. Also, since it's solely my project -- been totally on my lonesome on this one, save for a few small pieces of code (see #2 above, but I still should have double- and triple-checked it) -- there's only one person to take the blame. Doubly frustrating as I took extra time on Friday and Sunday to make it a smooth transitional process and catch as many small details as I could remember.