Why not replace that manual process with a robot to prevent missing something, as well as save us all more time? This is the thought behind the Sonar Reviewer that we created as part of our Continuous Integration (CI) Pipeline.

Testing our software is ingrained as an essential part of the Belvedere procedure before a code change gets delivered to the hands of the traders.

The article describes the process of migrating a basic SysVinit script for the Splunk Forwarder service to a systemd.service configuration file. It highlights the key differences between the two service management systems and demonstrates how to translate essential functionality while leveraging systemd's features.

Belvedere, a company with significant proprietary code, explains how they integrated their internal Gerrit code review system with a public GitHub account. This allows them to contribute non-proprietary code upstream while minimizing the risk of exposing trade secrets.

Managing R packages is challenging as ensuring specific versions across numerous servers is difficult. While SaltStack's built-in commands offer solutions, custom execution and state modules provide a much more readable and efficient approach, allowing management through pillar data and internal CRAN servers.

Market makers, like Belvedere, constantly push technological boundaries to ensure market stability and customer satisfaction. Recognizing the power of collaboration, Belvedere embraces open source software and aims to "pay it forward" by contributing their own solutions.