Software complexity grows exponentially, developer efficiency grows far slower. And debugging often takes up 20-50% of development time. More complex, connected systems means increased data flow at the edge, and in the cloud. That leads to increased exposure to vulnerabilities, cyber threats, malfunctions, and bugs with risks that are hard to assess.

Jaeger, the popular open-source distributed tracing system, is getting a major upgrade with the upcoming release of Jaeger v2. This new version is a new architecture for Jaeger backend components that utilizes OpenTelemetry Collector framework as the base and extends it with Jaeger’s unique features. It promises to bring significant improvements and changes, making Jaeger more flexible, extensible, and even better aligned with the OpenTelemetry project.

The proliferation of managed LLM services like OpenAI, Amazon Bedrock, and Anthropic have introduced a wealth of possibilities for generative AI applications. Application engineers are increasingly creating chain-based architectures and using prompt engineering techniques to build LLM applications for their specific use cases.

Most of us are aware that generative AI offers opportunity for innovation and efficiency where it is revolutionising how businesses operate. However, its impact is not fully understood. Earlier this year, Console Connect conducted a survey by Arlington Research which engaged 1,000 global CTOs and senior leaders to gain a better understanding of the challenges and demands associated with gen AI adoption.

If you bet on end-to-end testing or even synthetic monitoring, there’s a high chance that you use Microsoft's Playwright. And if you have Playwright in your toolchain, you probably adopted TypeScript, too. It's an easy choice because of its rock-solid auto-completion and type safety. With this setup, you can enjoy the beautiful DX (developer experience) and safely refactor your ever-growing code base without worrying about runtime exceptions because of TypeScript's type checking, right? Wrong!

Persisting to flash is a necessary evil for many embedded devices. Let’s take a look at some of the pitfalls and how they may be avoided.