Separate “debug” and “release” builds are very common in embedded development. Typically the notion is improved debug capabilities (less aggressive compiler optimizations, more debugging information like logs) vs. highly optimized and hardened production release builds. I’m here to describe disadvantages to this practice, and why it might make sense to consolidate to a single build! Like Interrupt? Subscribe to get our latest posts straight to your mailbox.

Internet-of-Things (IoT) devices and technologies have penetrated into our life. Nowadays, we can easily find IoT devices around us. Home appliance manufacturers produce IoT products for smart homes. Car makers invest in smart vehicles that can communicate with other smart cars and IoT objects nearby. Governments allocate huge resources to build smart cities with IoT technologies to improve the quality of life for people and promote economic growth.

IoT devices open the door to all sorts of computing potential, but they can also produce a flood of telemetry data that users need to properly collect and monitor to ensure those devices are working properly. It’s no wonder so many individuals and businesses use Grafana for IoT use cases, whether they’re starting an aquaponic farm in South Africa, managing an industrial-scale electroplating factory in Ohio, or simply keeping tabs on Pretzel the python at its home in the UK.

Many industrial operators find themselves amid yet another industrial revolution. Deeper insight through artificial intelligence (AI) and machine learning (ML) integrations characterize this fourth wave (or Industry 4.0). Data is no longer just a record occupying server space. It’s alive and providing value. Real-time insights work in tandem with historical records, painting a complete picture of the lifespan of a piece of machinery and/or its components.

As IoT (Internet of Things) device form factors have got smaller and batteries have got better, use cases for IoT applications have expanded into every sector. From trucks, to shipping containers, people, to cattle, an organisation’s assets can be fixed, mobile, autonomous and even sentient - relaying information that can deliver new business insights and competitive advantage. But these benefits only come if the information is able to get to the right place at the right time.