OutOfMemoryException is a common and frustrating bug, and one of the prime causes of unexpected app shutdown. “Why is this happening now, if the app was working perfectly yesterday?” It’s a question which perplexes both rookie and advanced Android developers the world over. There are a variety of potential causes of OutOfMemory Exceptions, but one of the most common is the memory leak — the allocation of memory in the app which is never released.
One of the challenges when you’re starting out with Development is getting the lay of the land. There are a lot of tools out there. And when one of the goals of Development is continually improving your processes, it’s important for you to understand how those tools might fit in your infrastructure. At the same time, you want to be efficient. You don’t want to add tools that overlap with one another. Or tools that cost more than other effective alternatives.
Lambdas are a powerful feature of the Ruby language. They allow you to wrap logic and data into a portable package. In this post, we’ll cover how and when to use lambdas. You'll also learn about the difference between lambdas and Procs, and the performance profile of lambda functions. The code examples have been tested with 2.6 and 2.7 and should work with most modern Rubys.
Nowadays, the term ‘remote debugging’ instills fear into even the bravest of dev hearts. Palms sweaty, knees weak, and arms ready (to code) they dive into what they’re sure will end in much pain and possibly a few broken pieces of code. This scenario and these feelings are common to devs everywhere, where many opt to take the trusted path of debugging on their *own* machines.
Last week, we announced NSolid 3.11.1, which introduces Role Based Access Control along with support for Node.js Erbium v12.16.2 and Dubnium v10.20.1. You can read here for more information. NodeSource’s Role Based Access Control feature empowers Org Admins to create, define, manage and assign roles that provide access privileges to distinct user-actions and/or views in the NSolid Console and accounts.nodesource.com.
We've all been there. You're clicking around your Rails application, and it just isn't as snappy as it used to be. You start searching for a quick-fix and find a lot of talk about caching. Take your existing app, add some caching, and voila, a performance boost with minimal code changes. However, it's not this simple. Like most quick fixes, caching can have long-term costs.
If there’s one thing SRE professionals and Development engineers lack, it’s time. After all, engineers need to oversee a variety of processes—like ensuring operational stability, conducting integration testing, and maintaining cybersecurity—to make sure their apps are working optimally. The list goes on and on. With heavy workloads and tight deadlines, there’s little time to waste on software issues stemming from internal collaboration issues.
