<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Engineering on Akshay Deshpande</title>
    <link>https://akshayd-dev.pages.dev/tags/engineering/</link>
    <description>Recent content in Engineering on Akshay Deshpande</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 14 Sep 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://akshayd-dev.pages.dev/tags/engineering/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Design Philosophy: Observability</title>
      <link>https://akshayd-dev.pages.dev/posts/philosophy-of-design-observability/</link>
      <pubDate>Sun, 14 Sep 2025 00:00:00 +0000</pubDate>
      <guid>https://akshayd-dev.pages.dev/posts/philosophy-of-design-observability/</guid>
      <description>&lt;p&gt;I enjoy philosophy. Stoic philosophy in particular.&lt;br&gt;
Philosophy, I think, helps us revalidate our purpose. It acts as a yard stick and makes sure that we are not moving away from our First-Principles.&lt;/p&gt;
&lt;p&gt;Applying the same to Software Engineering, in my opinion, every team should have a &amp;ldquo;Design Philosophy&amp;rdquo;. What is that one yard stick which teams can use for making better decisions.&lt;br&gt;
Infact, it is done in some forms in a few cases. Some call it Guiding-Principles. Some call it MVPs. I call it &amp;ldquo;&lt;code&gt;Design Philosophy&lt;/code&gt;&amp;rdquo;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
