As we mentioned in the previous article, at NodeSource, we are dedicated to observability in our day-to-day, and we know that a great way to extend our reach and interoperability is to include the Opentelemetry framework as a standard in our development flows; because in the end our vision is to achieve high-performance software, and it is what we want to accompany the journey of developers in their Node.js base applications.
Mobile teams need to consider these four things to ensure they are measuring and managing code quality. Because at the end of the day, good code is clean and well-managed code.
State management is a very controversial topic in the Flutterverse, with many holding strong opinions on it. In the last few weeks, my Twitter feed has been overwhelmed with threads about state management, covering the entire spectrum of opinions, from GetX/BLoC/Riverpod fanatics on one side to a few rare enlightened ones on the other side who recommend not using any state management at all. While I personally enjoyed almost all of them, the impact on the Flutter community has been quite severe.
Bitrise acquires Flare.Build. By adapting Flare.Build’s advanced caching and CDN technology to tools beyond Bazel, Bitrise can speed up feedback loops, iterate faster, and multiply app build performance by up to 10x.
In this blog post, we’ll be taking a closer look at Hyper-Datasets, which are essentially a supercharged version of Clear-ML Data.
In this post I'll explain how to use a cloud pubsub service such as Ably to visualize the progress of a serverless workflow in realtime. You'll learn.