Systems | Development | Analytics | API | Testing

The JavaScript RangeError: Maximum call stack size exceeded is an error that occurs when there are too many function calls, or if a function is missing a base case.

Sometimes you have a task that is too slow for a typical web request, such as sending an email or parsing a CSV file. Laravel Queues are a great fit for that type of work. In this article, Farhan dives deep into the Laravel docs to help us understand all of the various options.

When it comes to the claims process, speed is of the utmost importance. However, too often, manual inefficient processes slow insurers down, resulting in settlement delays, a poor customer experience, and higher costs. And today’s economic climate only exacerbates claims leaders' challenges.

Internationalization means adapting your application to the language and culture of your users—a difficult task! Luckily, Rails provides the I18n API. In this article, Pavel Tkachenko shows us how to start translating.

One of the main attributes of low-code development is speed. With the Appian Low-Code Platform, building, modifying and executing enterprise applications is fast and easy. And data is what powers those applications. That data has to be organized and managed, and this can slow down the development process.

Modern technology has enabled businesses to collect all manner of data. Managing data as an asset includes website interactions to drilled-down explanations of what makes a company’s strategy successful, this information informs initiatives, aids decision-making, improves business processes, and provides a way to measure success toward specific objectives. However, having enterprise data is not a strategy or a competitive advantage in and of itself.

Complex modern systems are the new reality for infrastructure teams, and this is due to the evolution of Cloud Computing and working with Distributed systems, containerization, and microservices by default. The teams now have different infrastructures and virtual services with which they must take care of scalable, reliable, and performative applications.

In the first part of this two-part series on memory leaks, we looked at how Ruby manages memory and how Garbage Collection (GC) works. You might be able to afford powerful machines with more memory, and your app might restart often enough that your users don't notice, but memory usage matters. Allocation and Garbage Collection aren't free. If you have a leak, you spend more and more time on Garbage Collection instead of doing what you built your app to do.

An API is a unique product. There is no presentable UI or outcome a developer can show and market similar to a regular product in the marketplace. The only way to perceive its usefulness is to spend time testing and understanding the value it brings. Given these unique conditions, monetizing an exposed API requires a different approach compared to monetizing other products. This post discusses how to build a pricing strategy for your APIs and which aspects you should consider.