<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Hariom Sharma</title>
    <description>The latest articles on DEV Community by Hariom Sharma (@harryy2510).</description>
    <link>https://dev.to/harryy2510</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F616046%2F3e77768a-1d3e-4ae5-9e77-70fcd02cec13.jpeg</url>
      <title>DEV Community: Hariom Sharma</title>
      <link>https://dev.to/harryy2510</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/harryy2510"/>
    <language>en</language>
    <item>
      <title>Hello World</title>
      <dc:creator>Hariom Sharma</dc:creator>
      <pubDate>Fri, 24 Apr 2026 06:21:08 +0000</pubDate>
      <link>https://dev.to/harryy2510/hello-world-581f</link>
      <guid>https://dev.to/harryy2510/hello-world-581f</guid>
      <description>&lt;p&gt;I have been writing notes for years. Architecture decisions, debugging war stories, things I wish someone told me before I shipped that thing to production. All sitting in private docs nobody reads.&lt;/p&gt;

&lt;p&gt;That felt like a waste. So here we are.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why bother?
&lt;/h2&gt;

&lt;p&gt;I have shipped 15+ products across 10+ industries over the last decade. Google, Telefonica, startups you have never heard of. Every project taught me something. Most of those lessons live in my head or in scattered docs. A blog gives them a permanent home and forces me to think clearly about what I actually learned vs what I think I learned.&lt;/p&gt;

&lt;p&gt;A portfolio shows what I built. A blog shows how I think. If you are deciding whether to work with me, both matter.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to expect
&lt;/h2&gt;

&lt;p&gt;Short posts on real engineering problems. Architecture decisions where both options suck and you pick the less painful one. AI tooling -- I have been deep in Claude Code, building plugins, automating my own workflow. Performance work. Shipping fast without shipping garbage.&lt;/p&gt;

&lt;p&gt;No listicles. No "ultimate guides." No sponsored content. Just notes from building things.&lt;/p&gt;

&lt;h2&gt;
  
  
  This blog's stack
&lt;/h2&gt;

&lt;p&gt;Astro with MDX on Cloudflare Workers. Zero client JavaScript (except a tiny search filter). Content Collections for type-safe frontmatter. Shiki for code highlighting. The whole thing scores 100 across Lighthouse.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;posts&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;getCollection&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;blog&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="nx"&gt;data&lt;/span&gt; &lt;span class="p"&gt;})&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="nx"&gt;data&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;draft&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="nx"&gt;data&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;publishDate&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;=&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;Date&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
&lt;span class="p"&gt;})&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Every post is an &lt;code&gt;.mdx&lt;/code&gt; file committed to the repo. Git is the CMS. No database, no build-time API calls, no dependencies that will break in six months.&lt;/p&gt;

&lt;p&gt;First real posts coming soon -- starting with how I set up my AI development stack and why most people are burning tokens for nothing.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://harryy.me/blog/hello-world" rel="noopener noreferrer"&gt;harryy.me&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>meta</category>
    </item>
  </channel>
</rss>
