<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
      <title>AdarshRust - backend</title>
      <link>https://adarshrust-blog.pages.dev</link>
      <description>Personal notes on Rust engineering, job applications, interviews, projects, and career growth.</description>
      <generator>Zola</generator>
      <language>en</language>
      <atom:link href="https://adarshrust-blog.pages.dev/tags/backend/rss.xml" rel="self" type="application/rss+xml"/>
      <lastBuildDate>Tue, 19 May 2026 00:00:00 +0000</lastBuildDate>
      <item>
          <title>Hello, World</title>
          <pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate>
          <author>Unknown</author>
          <link>https://adarshrust-blog.pages.dev/blog/2026/05/19/hello-world/</link>
          <guid>https://adarshrust-blog.pages.dev/blog/2026/05/19/hello-world/</guid>
          <description xml:base="https://adarshrust-blog.pages.dev/blog/2026/05/19/hello-world/">&lt;p&gt;This blog is where I will keep the engineering notes that are useful after the current sprint is over.&lt;&#x2F;p&gt;
&lt;p&gt;I write Rust, build backend systems, and keep notes while the details are still sharp. The goal is simple: document the code, tradeoffs, debugging paths, and mistakes that are worth remembering.&lt;&#x2F;p&gt;
&lt;p&gt;Most posts will be one of three things:&lt;&#x2F;p&gt;
&lt;ul&gt;
&lt;li&gt;Deep dives into Rust and backend behavior.&lt;&#x2F;li&gt;
&lt;li&gt;Build journals from projects like the &lt;a href=&quot;&#x2F;now&#x2F;&quot;&gt;Async Job Queue&lt;&#x2F;a&gt;.&lt;&#x2F;li&gt;
&lt;li&gt;Career notes that are specific enough to be useful later.&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;
&lt;p&gt;Here is the shape I want from a post:&lt;&#x2F;p&gt;
&lt;div class=&quot;code-wrap&quot; data-code-block&gt;
  &lt;div class=&quot;code-toolbar&quot;&gt;
    &lt;span&gt;en&lt;&#x2F;span&gt;
    &lt;button type=&quot;button&quot; data-copy-code&gt;Copy&lt;&#x2F;button&gt;
  &lt;&#x2F;div&gt;
  &lt;pre&gt;&lt;code class=&quot;language-en&quot;&gt;use std::time::Duration;

struct Job {
    id: u64,
    timeout: Duration,
}

impl Job {
    fn should_retry(&amp;amp;amp;self, attempts: u8) -&amp;amp;gt; bool {
        attempts &amp;amp;lt; 3 &amp;amp;amp;&amp;amp;amp; self.timeout.as_secs() &amp;amp;gt; 0
    }
}&lt;&#x2F;code&gt;&lt;&#x2F;pre&gt;
&lt;&#x2F;div&gt;
&lt;p&gt;The code should be small enough to inspect and real enough to matter.&lt;&#x2F;p&gt;




&lt;figure class=&quot;figure&quot;&gt;
  &lt;picture&gt;
    &lt;source type=&quot;image&#x2F;webp&quot; srcset=&quot;https:&amp;#x2F;&amp;#x2F;adarshrust-blog.pages.dev&amp;#x2F;processed_images&amp;#x2F;terminal-workspace.570214659fc56d98.png 800w, https:&amp;#x2F;&amp;#x2F;adarshrust-blog.pages.dev&amp;#x2F;processed_images&amp;#x2F;terminal-workspace.28139b166272f227.png 1200w, https:&amp;#x2F;&amp;#x2F;adarshrust-blog.pages.dev&amp;#x2F;processed_images&amp;#x2F;terminal-workspace.ee5ef2a268ebef51.png 1600w&quot;&gt;
    &lt;img src=&quot;https:&amp;#x2F;&amp;#x2F;adarshrust-blog.pages.dev&amp;#x2F;processed_images&amp;#x2F;terminal-workspace.28139b166272f227.png&quot; alt=&quot;A dark terminal workspace with Rust code and build logs&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;
  &lt;&#x2F;picture&gt;
  &lt;figcaption&gt;The starting point: small notes, working code, and a static site that stays out of the way.&lt;&#x2F;figcaption&gt;
&lt;&#x2F;figure&gt;
&lt;p&gt;I am starting with a static blog because the workflow should stay boring. Markdown in Git. Zola for builds. Railway for deploys. No database, no login, no admin surface.&lt;&#x2F;p&gt;
&lt;p&gt;If a note helps me rebuild context faster, it belongs here. If it only sounds impressive, it does not.&lt;&#x2F;p&gt;
</description>
      </item>
    </channel>
</rss>
