The rise of mobile devices
“I work in Wellington as a desktop support tech”, NZ Pilot Fish recalls.
“We often log into our helpdesk and take calls from our call centre staff. I have just received the following:
Me: “Hello, how can I help?”
User: “Hello, I just moved desk, and the computer time is wrong by half an hour.”
Me: “What time does your desk phone say?”
User: “That’s wrong too, it says 8.16.”
Me: “Your desk phone says 8.16?”
Me: “What time does your PC say?”
Me: “They both say 8.16?”
Me:: “Your PC and your phone both say it is 8.16?”
Me: “So does mine. That’s the time.”
User: “Is it?”
Me: “Yes, it is 8.16 in the morning.”
User: “Oh, my mobile must be wrong”.
Thanks for letting us know
Just after a software vendor ships a custom application to a big new customer, someone notices a line in the requirements document, reports pilot fish.
“It said, ‘The application shall support pooling.’ Pooling is an in-house methodology where related items can be aggregated if desired,” fish says.
The problem is, the user-interface developer had written about 40 complex queries and embedded them in his client-side application code — all without the pooling concept.”
The vendor’s head of development calls together the team. We have to fix this and get an updated version to the customer right away, he tells the group.
And with that, fish and his co-workers are plunged into a frantic effort to rewrite 40 complex queries into even more complex versions that include the pooling logic.
Developers and testers are working double shifts to get everything done. They’re pulling late-nighters and all-nighters.
And in just under a week, they get the job done.
“We posted the final build to the customer-facing download portal,” says fish. “Finally, some breathing room!”
And that’s when they get a piece of good news — just a little too late to help: “The customer decided to push off implementation until the next quarter, nearly three months away.”