We came up with the idea for On Location for two main reasons. First, our editors wanted to continue leveraging their unique, peer relationship with you, our readers. Our staff's real-world IT experience lets us answer the questions and cover the topics that are most important to you, and write about the technology other companies are implementing in language you're most familiar with. It's that peer insight that makes Network Computing different.
Second, no one else was doing case studies the way we thought they should be done. Before On Location, there were two types of case studies. The customer testimonial, written by a vendor to showcase its product, usually goes something like this: Customer is in dire need of a solution; vendor rides in on white horse to save the day; customer implements vendor's solution with ease; everyone lives happily ever after. If it were only that easy.
The other type of case study, found in both the business and the traditional technology press, typically is less glowing than the vendor variety but is still light on substance. Its authors just don't have the perspective to know how tough it is to make technology work. No project is without its problems and obstacles, and that's the most valuable information to readers, so you can avoid making the same mistakes. But traditional case studies never seem to talk about those things in much depth.
It's easy to understand why a vendor would want to keep a lid on technology problems, but the press should be able to deal with the good and not-so good. That's where Network Computing and our On Location series step in. Our editors have the technical and IT organizational experience to dive into these projects to find out what really helped or hurt their success.
And while we're at it, why wait for the project to be finished? We jump in near the start and follow along with the customer as the project evolves, not knowing how things will turn out. That's exactly what we do this issue with Life Time: We chart the history of the company's Member Management System, explain where Life Time is now and pose some questions about the future. And we'll be there, in print and online, to see that those questions get answered. We are in this for the long run, just like Life Time.
To realize the benefits of cloud-native software, an application must actually be cloud-native—designed to run in the cloud, interacting with disaggregated cloud services, fully manageable as code—to deliver the expected benefits.
By combining resources and expertise, the AI-Enabled ICT Workforce Consortium will offer a blueprint for how industries can adapt to an AI-dominated future.
IT leaders should heed the guidance of cybersecurity insurance providers who think businesses should prioritize security education, incident preparedness, regular internal audits, and ongoing vulnerability scanning and patching.
