<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Career on kmcd.dev</title><link>https://kmcd.dev/tags/career/</link><description>Recent content in Career on kmcd.dev</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>All Rights Reserved</copyright><lastBuildDate>Sun, 06 Sep 2026 10:00:00 +0000</lastBuildDate><atom:link href="https://kmcd.dev/tags/career/index.xml" rel="self" type="application/rss+xml"/><item><title>Joining Buf</title><link>https://kmcd.dev/posts/joining-buf/</link><pubDate>Sun, 06 Sep 2026 10:00:00 +0000</pubDate><guid>https://kmcd.dev/posts/joining-buf/</guid><description> 
                
                A check-in for my career
                </description><content:encoded><![CDATA[<p>I&rsquo;ve started working at <a href="https://buf.build/" rel="external">Buf Technologies</a>! This will come as no surprise to those who have been following me for a while. I&rsquo;ve been writing about schema-first development, have made tools to enable protobuf-driven development (<a href="https://fauxrpc.com/" rel="external">FauxRPC</a> and <a href="https://github.com/sudorandom/protoc-gen-connect-openapi" rel="external">protoc-gen-connect-openapi</a>), and I&rsquo;ve been a big fan and user of the ConnectRPC stack for a long time.</p>
<p>I joined Buf to work in developer relations. This is a change from what I have been doing. I&rsquo;ve usually been making in-house tooling and API services, and writing was related to side projects. I started writing this blog as a hobby and as a vehicle to develop my skills (both in writing and as a SWE). For a long time, I felt writing was a weak area of mine. I previously shied away from it because I figured I had nothing useful to say. I think that used to be true, but over the years, I have gained enough real experience to add some genuine flavor to my ideas here.</p>
<p>I have tracked down bugs that were unknowingly causing millions of dollars in lost revenue per month. I have contributed features to open source projects and run a few of my own. I have dug into obscure TLS extension issues and maintained forks of Go to support legacy network equipment. I have performed every role needed to get real services into production. While I&rsquo;d rather not share a lot of specific details or name the companies where these events took place, I have worked at enough places that stories like these just&hellip; happen. I&rsquo;m sure many other experienced software engineers would be able to share similar stories over a beer.</p>
<p>Since starting at Buf, I&rsquo;ve posted several blogs on the <a href="https://buf.build/blog" rel="external">Buf blog</a>. I&rsquo;ve also adapted protobuf.kmcd.dev to be suitable for <a href="https://protobuf.com" rel="external">protobuf.com</a>. That&rsquo;s right, <a href="https://protobuf.com" rel="external">protobuf.com</a> is now a learning website for Protobuf. I have a few more ideas on how to expand it to be a bit more engaging. The goal is to introduce Protobuf in a way that is approachable to people. The language-focused tutorials do a good job of getting people generating and running code, but with WASM, my idea is that you can start getting real experience with Protobuf with zero setup.</p>
<p>That said, with this new role, my posting cadence on this blog will change. I will likely be publishing here less often, probably around once a month. My focus will also shift more toward network protocol exploration rather than Protobuf and ConnectRPC. If you want to read more about schema-first development and Protobuf/gRPC/ConnectRPC, you can find that on <a href="https://buf.build/blog" rel="external">buf.build/blog</a>. There will be plenty to read about those subjects there!</p>
]]></content:encoded></item></channel></rss>