Systems | Development | Analytics | API | Testing

In the article “From Data to Insights: An Introduction to Product Analytics”, we walk you through the basics of product analytics, providing you with a high-level approach to get started with it. This time, we’d like to dig in deeper to dissect every step of the product analytics process, assuming that the main goal is to improve user engagement and retention.

Flaky tests are one of the most common and frustrating issues in software testing. These are tests that pass or fail sporadically, even if the code being tested has not changed. This can cause confusion and wasted time for developers who are trying to fix issues that may not even exist.

Today we’re pleased to announce a new strategic partnership and resale agreement with Imperva. Imperva customers will now be able to directly license Kong Enterprise, the fastest, most feature-rich, and secure API management solution. In addition, Kong customers will be able to use the Imperva API Security plugin within Kong Enterprise. This allows developers to comprehensively secure their APIs and protect their business applications and data against unauthorized access.

Despite its many advantages, Node.js comes with a set of potential pitfalls if you don't maintain your application properly, such as: In this post, we'll explore these pitfalls and how to avoid them. Let's dive straight in!

There are many ways to load code and access file-related constants in Ruby. We can create a clear architecture by separating and handling concerns into classes and pulling in only the classes we depend on. Many full-stack frameworks like Rails and Hanami offer a built-in method to access the classes we want, as long as we stick with a certain convention. How does this work? In this post, we will explore three different options for loading code: using load, require, and autoload.