<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Go on RetakeData</title><link>https://retakedata.com/tags/go/</link><description>Recent content in Go on RetakeData</description><generator>Hugo</generator><language>en</language><copyright>&lt;a href="https://creativecommons.org/licenses/by-nc/4.0/" target="_blank" rel="noopener">CC BY-NC 4.0&lt;/a></copyright><lastBuildDate>Fri, 20 Jun 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://retakedata.com/tags/go/index.xml" rel="self" type="application/rss+xml"/><item><title>Building tools from operational pain</title><link>https://retakedata.com/posts/2025/06/building-tools-from-operational-pain/</link><pubDate>Fri, 20 Jun 2025 00:00:00 +0000</pubDate><guid>https://retakedata.com/posts/2025/06/building-tools-from-operational-pain/</guid><description>&lt;p>Every tool we build starts the same way: a recurring operational pain that no existing product solves well enough. This is the story of two tools that came directly from production infrastructure work, and the AI-assisted workflow that made them possible.&lt;/p>
&lt;h2 id="the-centreon-gap">The Centreon gap&lt;/h2>
&lt;p>At a previous engagement, the team managed monitoring configuration through Centreon. The only Terraform provider available targeted the legacy CLAPI API, unmaintained for over five years. The V1 API provider lacked features needed for modern infrastructure management.&lt;/p></description></item></channel></rss>