<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>BitKode</title><description>BitKode is a bilingual publication on software engineering: articles, guides, references, and notes in English and Spanish.</description><link>https://bitkode.dev/</link><language>en-us</language><item><title>hlab: Turning a Proxmox Homelab into a Tiny Platform</title><link>https://bitkode.dev/articles/hlab-proxmox-homelab-platform/</link><guid isPermaLink="true">https://bitkode.dev/articles/hlab-proxmox-homelab-platform/</guid><description>A hobby project that turns Proxmox VM creation into a self-service platform experience: plans, templates, a dashboard TUI, and a headless CLI for automation and AI agents.</description><pubDate>Thu, 09 Jul 2026 00:00:00 GMT</pubDate><category>Homelab</category><category>Virtualization</category><category>Internal Developer Platforms</category><category>proxmox</category><category>terraform</category><category>ansible</category><category>go</category><category>cli</category><category>tui</category><category>open-source</category></item><item><title>Which LLM Would I Use for Backend Development?</title><link>https://bitkode.dev/articles/which-llm-would-i-use-for-backend-development/</link><guid isPermaLink="true">https://bitkode.dev/articles/which-llm-would-i-use-for-backend-development/</guid><description>I gave several LLMs the same Go backend assessment to see which one is actually useful in day-to-day software development. The result was less about who writes the most code and more about who survives verification.</description><pubDate>Wed, 08 Jul 2026 00:00:00 GMT</pubDate><category>Evaluations</category><category>Agents</category><category>Prompt Engineering</category><category>llm</category><category>go</category><category>backend</category><category>benchmark</category><category>agents</category></item><item><title>Eventual Consistency Is a Product Decision</title><link>https://bitkode.dev/articles/eventual-consistency-is-a-product-decision/</link><guid isPermaLink="true">https://bitkode.dev/articles/eventual-consistency-is-a-product-decision/</guid><description>Consistency is usually filed under &apos;backend detail,&apos; but staleness leaks straight into the interface and the business rules. Deciding how stale is acceptable is a product decision — here is how to treat it like one.</description><pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate><category>Eventual Consistency</category><category>Distributed Systems</category><category>Event-Driven Architecture</category><category>cap-theorem</category><category>ux</category><category>consistency</category><category>trade-offs</category></item><item><title>Why Event-Driven Architectures Exist</title><link>https://bitkode.dev/articles/why-event-driven-architectures-exist/</link><guid isPermaLink="true">https://bitkode.dev/articles/why-event-driven-architectures-exist/</guid><description>Direct calls between services are simple until they aren&apos;t. Event-driven architecture is the answer to a specific failure of tightly coupled systems — here is the problem it actually solves.</description><pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate><category>Event-Driven Architecture</category><category>Distributed Systems</category><category>events</category><category>kafka</category><category>decoupling</category><category>asynchronous</category></item><item><title>Why Platform Engineering Matters</title><link>https://bitkode.dev/articles/why-platform-engineering-matters/</link><guid isPermaLink="true">https://bitkode.dev/articles/why-platform-engineering-matters/</guid><description>Every growing engineering org quietly builds a platform — the only question is whether anyone owns it. Platform engineering is the decision to treat that platform as a product, and here is the problem it solves.</description><pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate><category>Internal Developer Platforms</category><category>Golden Paths</category><category>backstage</category><category>devops</category><category>developer-experience</category><category>idp</category></item><item><title>Building Your First MCP Server</title><link>https://bitkode.dev/guides/building-your-first-mcp-server/</link><guid isPermaLink="true">https://bitkode.dev/guides/building-your-first-mcp-server/</guid><description>A practical, reproducible walkthrough: build a minimal Model Context Protocol server in TypeScript, expose a tool an AI client can call, and verify it end to end.</description><pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate><category>MCP</category><category>AI Agents</category><category>mcp</category><category>typescript</category><category>ai</category></item><item><title>Deploying an Astro Site to Cloudflare Workers</title><link>https://bitkode.dev/guides/deploying-an-astro-site-to-cloudflare-workers/</link><guid isPermaLink="true">https://bitkode.dev/guides/deploying-an-astro-site-to-cloudflare-workers/</guid><description>Ship a static Astro build to Cloudflare&apos;s edge with Workers static assets: wrangler config, GitHub CI, per-branch preview URLs, and an honest look at the limits.</description><pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate><category>Static Hosting</category><category>Edge Computing</category><category>astro</category><category>cloudflare</category><category>ci-cd</category></item><item><title>What Is CQRS?</title><link>https://bitkode.dev/references/what-is-cqrs/</link><guid isPermaLink="true">https://bitkode.dev/references/what-is-cqrs/</guid><description>A canonical explanation of CQRS: treating reads and writes as two different problems with two different models, why that split exists, and when it is worth the cost.</description><pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate><category>CQRS</category><category>Event-Driven Architecture</category><category>cqrs</category><category>read-model</category><category>write-model</category><category>scalability</category></item><item><title>What Is Event Sourcing?</title><link>https://bitkode.dev/references/what-is-event-sourcing/</link><guid isPermaLink="true">https://bitkode.dev/references/what-is-event-sourcing/</guid><description>A canonical explanation of event sourcing: storing the full history of what happened as an append-only log of facts, and deriving current state by replaying it.</description><pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate><category>Event Sourcing</category><category>Event-Driven Architecture</category><category>CQRS</category><category>events</category><category>state</category><category>cqrs</category><category>kafka</category></item><item><title>What Is the Outbox Pattern?</title><link>https://bitkode.dev/references/what-is-the-outbox-pattern/</link><guid isPermaLink="true">https://bitkode.dev/references/what-is-the-outbox-pattern/</guid><description>A canonical explanation of the outbox pattern: how to update a database and publish an event without the two silently drifting apart when one of them fails.</description><pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate><category>Outbox Pattern</category><category>Event-Driven Architecture</category><category>Distributed Systems</category><category>outbox</category><category>messaging</category><category>consistency</category><category>kafka</category></item><item><title>TypeScript&apos;s satisfies Operator Is Underrated</title><link>https://bitkode.dev/notes/typescript-satisfies-operator-is-underrated/</link><guid isPermaLink="true">https://bitkode.dev/notes/typescript-satisfies-operator-is-underrated/</guid><description>A type annotation validates a value but widens it. The satisfies operator validates without widening — so you keep the exact type you actually wrote.</description><pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate><category>TypeScript</category><category>Type Systems</category><category>typescript</category><category>types</category></item></channel></rss>