Using data to make decisions is actually really hard. Yet nearly every tech company, business, and team touts “data-driven” as the de-facto way that they operate. In practice, this intention to be data-led is often just aspirational—only about a quarter of organizations report that they are actually data-driven, according to Harvard Business Review. It’s easy to see why organizations strive to more effectively use their data.
In this Kongcast episode, Danielle Dias, Software Engineer at Just Eat Takeaway.com, talks about how her team creates a seamless customer experience by using Kong Gateway for rate limiting, monitoring, alerting, and more. Check out the transcript and video from our conversation below, and be sure to subscribe to get email alerts for the latest new episodes.
Discover best practices for creating well-defined test scenarios to improve test coverage for your apps.
Look for the following must-haves when you want to move data seamlessly between sources and destinations of all kinds.
In software testing, a test plan is a must-have. A well-defined and comprehensive test plan provides all stakeholders involved with necessary information of the testing roadmap. Through it all members gain a shared vision for the testing approaches, strategies, objectives, resources, and timelines. In this article, we will deep-dive into what a test plan is, why it is so important, and how to create a good test plan that truly improves the overall efficiency of your testing activities.
Software development is a complex process that involves a variety of activities, including design, development, testing, and deployment. Among these, testing is one of the most critical phases, as it ensures that the software product meets the desired quality standards and functions as intended.
When Plastic SCM (now Unity Version Control) was acquired by Unity in 2020, game dev and VFX studios already using the Unity Engine started considering it more seriously for version control. Why? On the surface, Plastic SCM is an attractive solution. It offers a friendly UI for artists and handles the basics of version control at low scale. But what happens when your projects grow and get more complex? Does Plastic still hold up? Read along or jump ahead to the section that interests you most.
This article will teach you how to monitor Ruby errors without using a service like Honeybadger! Learn about Ruby's built-in errors, how to use log levels and tagging to customize the log output, display errors on the front-end, and more.
