Over the past few years, we’ve witnessed a couple of key trends in the performance monitoring space. Adoption of single-page applications (SPAs) has continued to grow and as such performance monitoring is evolving. SPAs don’t offer the same existing web metrics like load time or first paint from the browser performance API. As a result, developers require more flexibility to track the metrics that matter to their end-users and business.
Earlier in the year, we launched the request details page in Raygun Real User Monitoring. This update brought the instance-level insights into page performance to help you understand exactly what caused poor performance and how to improve it. To complement instance-level insights, this latest launch brings the Latest slowest requests module to Real User Monitoring.
We all want lightning-fast websites and applications, but how do we prioritize our efforts in order to have the biggest impact on performance? We interviewed our own front-end team so we could share some best practices we use every day to improve and maintain the performance of Raygun.
You’ve spent years scaling your infrastructure alongside your business growth, and day-to-day, your application performance is thriving. But what happens when your traffic spikes out of your predicted “normal” range, heading into unchartered territory? Are you prepared to support this new influx of customers? Or will you crumble under the pressure of it all - leaving customers dissatisfied at the poor user experience?
Over the last few years, more developers have taken Ruby as their staple programming language. Who can blame them? It certainly has a lot of appealing features. For one, the syntax is easy to read and debug. A default MVC architecture within most Ruby frameworks is another alluring factor that may have had you using it as well.
Remote pair programming is an Extreme Programming (XP) methodology which is a part of the Agile software development model. It takes the principle of pair programming to the remote workplace. Pair programming leads to higher quality code and fewer bugs by making continuous code reviews and synchronous collaboration possible. In traditional pair programming, two programmers sit side by side in front of the same computer.