Continuous Integration (CI) allows you to continuously integrate code into a single shared and easy to access repository. Continuous Delivery (CD) allows you to take the code stored in the repository and continuously deliver it to production. CI/CD creates a fast and effective process of getting your product to market before your competition as well as releasing new features and bug fixes to keep your current customers happy.

The launch of Signals has been a complete game-changer for us this year. Yellowfin is doing something completely unique in the marketplace and we’re winning some great deals because of it. Signals is an automated data discovery product that delivers alerts to users about critical changes in their business. It’s not about dashboards - this is a completely different way of consuming analytics.

The flow of data can be perilous. Any number of problems can develop during the transport of data from one system to another. Data flows can hit bottlenecks resulting in latency; it can become corrupted, or datasets may conflict or have duplication. The more complex the environment and intricate the requirements, the more the potential for these problems increases. Volume also increases the potential for problems. Transporting data between systems often requires several steps.

Today I’m going to do something different and not talk about a specific visualization as I’ve done in my last blog posts, but rather a technique that we use within visualization. How to create multiple views that each show a different part of your dataset?

We live in a digital age which is increasingly being driven by algorithms and data. All of us, whether at home or work, increasingly relate to one another via data. It’s a systemic restructuring of society, our economy and institutions the like of which we haven’t seen since the industrial revolution. In the business world we commonly refer to it as digital transformation. In this algorithmic world, data governance is becoming a major challenge.