Customer experience (CX) is becoming an increasingly strategic part of any company’s brand as businesses become more customer-centric. And thanks to technologies that give customers more options than ever, right at their fingertips, consumers expect a flawless CX, anytime and anywhere, regardless of medium. In other words, customer retention and satisfaction is intertwined with CX.

With over 50,000 active organizations and 250 million workflows, CircleCI is one of the most popular networked CI platforms. When getting started with CI pipelines, teams typically want to ensure that code will compile, pass unit tests, and build a container image. After catching these low hanging fruit of syntax errors, engineering teams need to dig much further to find business logic and scalability errors.

In August 2011, Marc Andreessen wrote an article in The Wall Street Journal entitled “Why Software Is Eating the World.” Andreessen predicted that the leading companies in any industry would be software companies. And indeed, a wave of online software companies arose in which Netflix ate Blockbuster, Apple and Spotify ate Tower Records and the CD, and LinkedIn disrupted the recruiting industry.

This post is the second in a series of deeper dive articles on the four DORA metrics. The first metric we looked at was Deployment Frequency, which is about how often code can get released to end users. In this second article, we’ll look at Change Lead Time, arguably the metric most familiar to developers.

Bitbucket Cloud is making changes to pull request diff functionality that will improve diff performance, particularly on complex diffs. We are changing our diff algorithm from what we call a '3-way' diff to a 2-way 'three-dot' diff, which will show the difference between the tip of a source branch and the commit from which it branched off the destination, as shown below. This new diff will be implemented on the Pull request page and Branch page in the coming weeks.

Most organizations that make software — from small startups to multi-billion-dollar behemoths — use third-party libraries and tools to develop their applications. Modern apps depend on many external components to build and deliver software to customers. These libraries and tools are collectively called the software supply chain. A software supply chain for a typical web app may include components like these.

Our last Qovery Demo Day took place on a live on the first Thursday of May. This event aims to give you some insights into what we did during the past month and what’s next and showcase some of our new features. During this demo day, Bilel (Software Engineer at Qovery) and Romain (Software Engineer at Qovery) joined me to talk about Terraform Improvements demo and Docker Build Improvements demo.

We are excited to announce that PagerDuty® Runbook Automation and PagerDuty® Process Automation On Prem are now available on the AWS Marketplace, the leading global cloud provider. With more than 200 different cloud services, AWS makes it simple and attractive to build and grow your cloud-native business and/or migrate your existing infrastructure to the cloud, so you can begin to take advantage of the unlimited scale, agility, and flexibility the cloud offers.

Axios is a promise-based HTTP library that lets developers make requests to either their own or a third-party server to fetch data. It offers different ways of making requests such as GET, POST, PUT/PATCH, and DELETE. In this tutorial, I will explain how Axios interacts with applications, describe the structure of Axios requests and responses, how to make requests to an API, and how to write tests for your requests using CircleCI.

Hive smart meters revolutionized the way customers control their energy use. But since their launch in 2012 by UK energy company British Gas, advances in cloud technology and a rapid increase in the number of smart homes has led to an explosion of data.