|
|
|
|
|
RESOURCES
|
|
CGI Inc.
Identify
12.12.05
AppSight helps IT consulting firm improve application performance, meet service level agreement with top telecom company.
As a rule, cell phone customers are not big on delayed gratification. Especially when they’ve just signed a new contract and are trying to get the phone activated so they can place their first call. Then, every minute feels like an eternity. So when one of the world’s largest telecom companies found that its new wireless service activation software threatened to make customers wait an average of 18 minutes for activation, they knew there was room for improvement.
|
|
| |
Alphabet Street
Each month we try our hardest to cover every angle and aspect of software engineering. Indeed, we pride ourselves on our platform-agnostic wide ranging view of the development landscape. How then could we push ourselves even further and really broaden the spectrum of our editorial coverage? The answer had to be – the complete A to Z of software. Well, not complete, but a rip roaring twenty-six letter technology tour to provoke some interest and thoughts in areas you might not normally think about.
But first, a personal confession so that you know how all this started. I actually got the idea from reading a cookery magazine that had done something similar. You know the kind of thing – A for apples, B for bread, C for custard and so on. But those pesky food journalists have it easy don’t they? When they get to X, Y and Z they can just use X for Xérès Sherry, Y for Yeast and even Z for Zabaglione.
Now, X is simple enough with plenty of XMLs out there, Z for zero tolerance we reckoned, but Y, wow - now that is a hard one.
So, please dive in and jump to your favourite letter. It was always going to be the case that we would miss out on a few key areas, but we think it’s pretty cool to be able to work your way through the whole alphabet and just stay within the world of software development. Next month, 1001 aspects of application development and how you can implement them in your daily working schedule. Joke – ok?
Happy coding!
Adrian Bridgwater
Editor

|
|