Production debugging, as the name suggests, takes place when one must debug the production environment and see the root cause of this problem. This is a form of debugging that can also be done remotely, as during the production phase, it may not be possible to debug within the local environment of the application. These production bugs are trickier to resolve as well, because the development team may not have access to the local environment when the problems do crop up.

Going into the new year, we had several exciting things in the works: expanding our office space, growing the team, attending and hosting events, and releasing a ton of new features for our users.

It’s no exaggeration to say that today’s internet is built on JavaScript. Around 95% of all websites have been built using the language, according to the latest figures. JavaScript has evolved beyond the client side and is now used to construct entire technology stacks, not to mention support databases like pouchdb and RethinkDB.

Welcome to 2020: the year in which having a business simply can’t happen without having a website. And, in recent years, not just ANY website. Business owners must have THE website: an online virtual space that is so magnificently created and intuitive to use, not to mention flame up emotions we never knew existed that users simply can’t forget. But how do you achieve this in a world with SO MANY WEBSITES without having to spend weeks if not MONTHS creating it?

There comes a time in every developer’s life (or daily routine, we’re not here to judge) where they have to go and fix a bug. Back in the days when I used to be a developer, I distinctly remember how each time I would go face to face with a bug, my favorite method to fix it was to add log lines. I mean, why not, right?

Let’s talk about SPAs. It all starts from a blank page which is subsequently filled with HTML and JavaScript. If we take PHP pages as an example, they already come bundled with the server, which is an advantage in terms of performance, right? For situations like these, server-side rendering frameworks (such as Next.js) come to the rescue. They process the code on the server-side to pre-fill the HTML result page with something (if not the whole page) before it reaches the browser.

The last 3,650 days of my professional life have been focused on making Rails apps faster. Below are five lessons I've learned the hard way.

As engineers, we continuously aim for perfection. The drive to deliver the perfect product sometimes defines how good we are as engineers. We often discuss and fine tune the term and the essence of our product’s perfection. Some claim that a perfect product is one that handles all the edge cases, works flawlessly, and can do everything.

We are excited to announce N|Solid v4.3.0, which delivers Import/Export functionality allowing users to easily match configuration settings across and covers the security patch to coincide with Node.js v15.2.1, v14.15.1, and v12.19.1. N|Solid Console users can now export configuration settings using either NSolid Console or the CLI, the result is a JSON format file which can be used to import settings across different setups.

This autumn launch for Tideways includes new features and improvements that we worked on the last three months. These are (in no particular order): Aside from this blog post explaining the new features in detail and the documentation, we also invite you to sign up for our 30 minute webinar "New Features and Improvements launched in autumn 2020" scheduled for 25th November 2020, 15:00 Europe/Berlin.