<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Posts on arvz</title>
    <link>https://arvz.tech/posts/</link>
    <description>Recent content in Posts on arvz</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <managingEditor>mail@arvz.tech (Arv)</managingEditor>
    <webMaster>mail@arvz.tech (Arv)</webMaster>
    <atom:link href="https://arvz.tech/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Architect-to-Builder: a reliable way to ship with agents</title>
      <link>https://arvz.tech/posts/architect-to-builder/</link>
      <pubDate>Wed, 12 Aug 2026 02:30:00 +0200</pubDate><author>mail@arvz.tech (Arv)</author>
      <guid>https://arvz.tech/posts/architect-to-builder/</guid>
      <description>As you interact more with LLM and agentic tools you start developing an intuition of sorts to make better use of the workflow and developing ideas to make them better.&#xA;One such simplest and neat ideas is Architect-to-Builder. It&amp;rsquo;s a pattern wherein you use a more capable model to write a proper plan of exactly what you want, it creates a plan, a proper summary of what is needed and also a phased plan of several subtasks with all edge cases thought through, definition of done etc.</description>
    </item>
    <item>
      <title>Service Evolution: From Monolith to Microservices</title>
      <link>https://arvz.tech/posts/service-evolution/</link>
      <pubDate>Wed, 24 Jun 2026 11:20:00 +0200</pubDate><author>mail@arvz.tech (Arv)</author>
      <guid>https://arvz.tech/posts/service-evolution/</guid>
      <description>Starting a new project? Unless you have a very strong reason, begin with a single node. This approach keeps things simple and allows you to focus on building your core functionality without unnecessary complexity.&#xA;Pro Tip: Ted Neward&amp;rsquo;s first law of distributed object design — &amp;ldquo;Don&amp;rsquo;t distribute your objects&amp;rdquo; — applies just as well to services: don&amp;rsquo;t distribute unless you must.&#xA;Premature Optimization: One of the biggest pitfalls in software development is premature optimization.</description>
    </item>
    <item>
      <title>K8S Cheatsheet</title>
      <link>https://arvz.tech/posts/k8s-cheatsheet/</link>
      <pubDate>Wed, 11 Mar 2026 19:40:00 +0200</pubDate><author>mail@arvz.tech (Arv)</author>
      <guid>https://arvz.tech/posts/k8s-cheatsheet/</guid>
      <description>Terminologies: k8s can use internally not just docker but also cri-o, container-d etc., Each pod must be located on the same server, i.e. it is not possible to spread containers of a pod across multiple servers Node: Is a server / computing unit; a pod always runs inside a node Cluster: Contains a bunch of nodes (can be across different data centers), but nodes are recommended to stay closer to each other; you need to set up this cluster, it is not automatic Node types: Master node and worker node; master handles control-plane duties (scheduling, API, etc.</description>
    </item>
    <item>
      <title>A Quick Intro to Golang</title>
      <link>https://arvz.tech/posts/go-intro-for-beginners/</link>
      <pubDate>Fri, 16 Jan 2026 16:10:00 +0200</pubDate><author>mail@arvz.tech (Arv)</author>
      <guid>https://arvz.tech/posts/go-intro-for-beginners/</guid>
      <description>Go is one of the most beautiful and efficient language i worked with so far. If you are an experienced programmer, you can learn to code in Go within few weeks, because the language is fairly small and concise. The purpose of this guide is to introduce the core tools and mechanics in Go and references are provided to dig more.&#xA;I wrote some code snippets in Go for additional reference: https://github.</description>
    </item>
  </channel>
</rss>
