Photoblog update
Really not writing to say much, other than I'm going to be posting some pictures of the new appartment on the photoblog....
On a side note, apparently Jon and I quitting MIS ended up costing the company quite a bit of money... It seems that an interaction between some of his code and one of my systems caused our system to run up a bill of tens of thousands of dollars from test data... I guess the jury is out on what actually caused it, but I'm betting it has to do with a modification someone else made to my order entry system... Copax, if you're reading this, I ***have*** to know what happend... This is just ***to*** damn good...
On a side note, apparently Jon and I quitting MIS ended up costing the company quite a bit of money... It seems that an interaction between some of his code and one of my systems caused our system to run up a bill of tens of thousands of dollars from test data... I guess the jury is out on what actually caused it, but I'm betting it has to do with a modification someone else made to my order entry system... Copax, if you're reading this, I ***have*** to know what happend... This is just ***to*** damn good...
2 Comments:
According to Accurev, the last person to modify the order bucket was you, perhaps it was just a situtation the bucket wasn't designed to handle.
Have you & copax checked for modifications to any of the support libraries used by the RealEC delayed order thingy (bucket). When something similar happened durring the intial rollout the issue was not caused by flawed logic in the bucket but a syntax error in a support library which halted processing the new order before it was marked complete. If the delayed order processor is causing the issue then this would be the most likely explanation.
Post a Comment
Subscribe to Post Comments [Atom]
<< Home