<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Protobuf on Pauls Blog</title><link>https://prule.github.io/pauls-blog/tags/protobuf/</link><description>Recent content in Protobuf on Pauls Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 14 May 2026 00:00:00 +1000</lastBuildDate><atom:link href="https://prule.github.io/pauls-blog/tags/protobuf/index.xml" rel="self" type="application/rss+xml"/><item><title>Building an ACC Dashboard with AI-Assisted Development</title><link>https://prule.github.io/pauls-blog/post/coding/2026/ai-assisted-development-1/</link><pubDate>Thu, 14 May 2026 00:00:00 +1000</pubDate><guid>https://prule.github.io/pauls-blog/post/coding/2026/ai-assisted-development-1/</guid><description>&lt;p&gt;Building useful software is the best way to learn. Building useful software &lt;em&gt;for a problem you actually have&lt;/em&gt; is even better.&lt;/p&gt;
&lt;p&gt;I race in Assetto Corsa Competizione. I wanted a proper dashboard for analysing lap times. So I started building one.&lt;/p&gt;
&lt;h2 id="the-real-goal"&gt;The Real Goal&lt;/h2&gt;
&lt;p&gt;Two goals, really. First: something genuinely useful. Second: a vehicle for practising software development - and increasingly, for understanding how AI tools fit into a real workflow.&lt;/p&gt;</description></item><item><title>Remote-controlling a simulator with gRPC and Protobuf</title><link>https://prule.github.io/pauls-blog/post/coding/2026/protobuf-and-grpc/</link><pubDate>Tue, 12 May 2026 00:00:00 +1000</pubDate><guid>https://prule.github.io/pauls-blog/post/coding/2026/protobuf-and-grpc/</guid><description>&lt;h1 id="remote-controlling-a-simulator-with-grpc-and-protobuf"&gt;Remote-controlling a simulator with gRPC and Protobuf&lt;/h1&gt;
&lt;p&gt;I have an Assetto Corsa Competizione (ACC) simulator that replays recorded UDP traffic. It is a useful test fixture, but it had a problem: to start or stop a session you had to be at the same machine, running the JVM process directly. Anything that wanted to drive the simulator as part of a larger pipeline — a Cypress test, a dashboard demo, a teammate on another laptop — had no way in.&lt;/p&gt;</description></item></channel></rss>