If your experience as a developer is anything like mine, the best moments are those known as the "flow state.” When distractions drift into the background and all your energy is going in the creative direction of solving the problem at hand. Your brain is directly connected to your users through your code. Months of progress happen in hours. Unfortunately, those moments are rare. But it’s not emails or Slack messages that are the biggest distractions.
Imagine you’ve been working on a new feature for weeks. Finally—after exhaustive QA and testing, and more late coding sessions than you care to count—you release with a feeling of both accomplishment and relief. Only to be woken up at 3am that something’s wrong. Or worse, you get flooded with customer complaints that it’s not working properly. Well, it’s probably a scenario you don’t need to imagine. Every developer has a version of this story to tell.
In this article, we’ll cover the key differences between APIs and microservices as answered by our contributors consisting of senior decision-makers and CTOs from technology companies around the world. One of the most popular ways to consume data from a web service is through a web application programming interface (API). By interface, we are referring to an agreement, or schema, that anyone using this API must abide by.
As developers, we’ve traditionally rooted out errors in our programs (we’ll call them bugs from now on if that’s ok) by using meaningful log statements. JavaScript has the famous console.log() method for that. But while log statements are good, they are less efficient than a tool that enables you to carry out step-by-step debugging. So in this article, we will learn how to use Google Chrome developer tools (also known as DevTools) to debug any JavaScript application effortlessly.
NodeSource is excited to announce N|Solid JS API! 🥳 With this new API you can use all the power provided by the N|Solid console and CLI using your own JavaScript code programmatically. In other words, now it is not necessary to listen to events from the console, but from your own code you can decide when to run a certain command under your chosen conditions.
One of the struggles developers face is how to catch all Python exceptions. Developers often categorize exceptions as coding mistakes that lead to errors when running the program. Some developers still fail to distinguish between errors and exceptions. In the case of Python application development, a python program terminates as soon as it encounters an unhandled error. So, to establish the difference between errors and exceptions, there are two types of errors.
Apple just introduced Apple M1, it’s new processor, along with their latest product versions. Back in June, when Apple had first announced the transition to Apple silicon, we applied for their Universal App Quick Start Program and, eventually, received an Apple Developer Transition Kit (DTK) so that we could try out our Rollbar-iOS and Rollbar.NET (via Xamarin) SDKs on the Apple new platform.
Are you planning moving to data-driven software management to keep on top of your quality assurance status, your security findings and development velocity? Thinking about building it yourself using Elasticsearch, Logstash and Kibana or maybe just using your Splunk instance for this? Read more to find out why this may or may not be a good idea.
