"“We'd built a billing application for a telco client in Macau, and it had been running happily for some time,” he told On Call. “By the time the system needed its first major OS upgrade, Jemaine was therefore happy for the local crew to handle the job.”"
"“A couple of friends ended up crashing my room, and we spent the weekend watching insane drivers hurl cars around an absurdly tight street circuit,” Jemaine admitted. “The client never called or paged, so after the race Jemaine was confident the upgrade was going well.”"
"“Dessert had just arrived when my pager went off,” he told On Call. Jemaine poured himself into a cab to his client's office and found a situation he described as “vague but clearly serious” because the billing application wouldn't start. “Judging by the silence and the stoic expressions, everyone was quietly panicking,” Jemaine wrote."
"He soon learned that the client had already tried to fix the app by reinstalling the OS twice and had now decided the database was the source of the problem. Jemaine was told t"
A database specialist in early 1990s Hong Kong worked on VAX/VMS systems for a telco billing application in Macau. After the system ran for some time, the first major OS upgrade was scheduled. Local staff were initially expected to handle the upgrade, but the client required the specialist to attend despite providing hotel accommodations with a view of the Grand Prix track. The weekend passed without client contact, leading to confidence that the upgrade succeeded. After the race, while eating dessert and drinking wine, a pager alerted him. He arrived at the office to find the billing application would not start, with staff showing quiet panic. The client had already reinstalled the OS twice and concluded the database was likely responsible.
Read at theregister
Unable to calculate read time
Collection
[
|
...
]