Over the past twenty years I have been working in tech, I have seen a variety of products and solutions come and go. For many, it is because they overly complicate something that should’ve been simple. With SolarWinds, I am thrilled to work with solutions designed from the start to be simple for our customers to use. We focus on providing solutions built to integrate with other elements of your network and complement them, so they become more effective.

It’s increasingly common for service desk teams to perform some support operations over a live chat. This is a win for everyone. When using chat support, employees are looking for quick wins when it comes to solving their problems, and in many cases, the service desk can help them quickly without needing a site visit. I worked the service desk way before online chats were possible, but the truth is not much has changed since then.

Internal IT support teams are often the first place employees turn for help with technical issues, and it’s important for team members to be able to quickly understand problems, identify solutions, and enable the employee to get back to work. Though there are plenty of technologies and organizational practices capable of improving support service teams, team-wide skills are the heart of every great service provider.

Testing is commonly understood to be an essential and fundamental part of software development, but when and how to test is open to a wider variety of opinions. DevOps practitioners often advocate for performance and quality testing early in the development and deployment process. This is known as a “shift left” approach.

The pandemic hit manufacturing hard, with the workforce, supply chains, and investment all taking heavy blows. The bounce-back has also been punishing on the sector, with severe global competition for materials, disrupted logistics, and workforce shortages, all exacerbated by the human and economic disaster of Ukraine.

Why do some organizations excel in streamlining their database operations and applications development while others find it immensely challenging? Why can some database teams embrace agility while others take months of cycles to deploy even a single line of code? What secret sauce can allow some database teams to work smarter (not harder), streamline database development lifecycles better, get to deployment faster, and create an overall stronger alignment across departments?

 Change management methodologies are often seen as complex and clunky, which can lead to these initiatives having a high failure rate in many organizations—but why does change management have this stigma? At one point in my career, I was a regular at change advisory board (CAB) meetings and maintained our organization’s standard change catalog.