<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Engineering on Arash Taher</title>
    <link>https://arashtaher.com/tags/engineering/</link>
    <description>Recent content in Engineering on Arash Taher</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 28 Oct 2026 10:19:54 +0000</lastBuildDate>
    <atom:link href="https://arashtaher.com/tags/engineering/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Just give me a cookbook</title>
      <link>https://arashtaher.com/blog/just-give-me-a-cookbook/</link>
      <pubDate>Wed, 28 Oct 2026 10:19:54 +0000</pubDate>
      <guid>https://arashtaher.com/blog/just-give-me-a-cookbook/</guid>
      <description>&lt;p&gt;One of the biggest problems I have working in a big company is the amount of documentation, and the expectation that everyone has the time, energy, and mental bandwidth to go through &lt;em&gt;very detailed documents&lt;/em&gt;.&lt;/p&gt;&#xA;&lt;p&gt;In many cases I just want a &lt;strong&gt;step-by-step guide&lt;/strong&gt;. Give me a clear and concrete layer of abstraction on top of what you’ve built, and let me use it. I don’t need to know how your system handles configuration, or what the topology of the architecture looks like. Just give me a cookbook I can follow so I can get the thing I need to do done.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
