<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>RPC</title><description>Essays on engineering, hiring, and building organizations — by Phillip (RPC).</description><link>https://rpc3.dev/</link><item><title>Portability is not deployability</title><link>https://rpc3.dev/posts/portability-is-not-deployability/</link><guid isPermaLink="true">https://rpc3.dev/posts/portability-is-not-deployability/</guid><description>Making software portable is only half the job. What a failed deployment into a locked-down customer environment taught me about testing real capabilities, owning outcomes across boundaries, and the gap between running somewhere and running where the customer actually is.</description><pubDate>Tue, 21 Jul 2026 12:00:00 GMT</pubDate></item><item><title>Hire for the next transition</title><link>https://rpc3.dev/posts/hire-for-the-next-transition/</link><guid isPermaLink="true">https://rpc3.dev/posts/hire-for-the-next-transition/</guid><description>The first engineering team isn&apos;t a smaller version of the one the company will eventually need. Why I hire for range over resemblance, give every early hire a real mandate, and build a team that can make the next team legible.</description><pubDate>Tue, 21 Jul 2026 11:00:00 GMT</pubDate></item><item><title>Productionizing research is a boundary problem</title><link>https://rpc3.dev/posts/productionizing-research-is-a-boundary-problem/</link><guid isPermaLink="true">https://rpc3.dev/posts/productionizing-research-is-a-boundary-problem/</guid><description>Turning a research prototype into a production system isn&apos;t a code-cleanup project. It&apos;s the work of designing a boundary between a research loop optimized for learning and a service other people can depend on.</description><pubDate>Tue, 21 Jul 2026 10:00:00 GMT</pubDate></item></channel></rss>