<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Methods on Nalar</title>
    <link>https://nalar.dev/tags/methods/</link>
    <description>Recent content in Methods on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 11 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/methods/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Composed Method: Keep Each Routine at One Level of Abstraction</title>
      <link>https://nalar.dev/composed-method-keep-each-routine-at-one-level-of-abstraction/</link>
      <pubDate>Fri, 11 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/composed-method-keep-each-routine-at-one-level-of-abstraction/</guid>
      <description>&lt;h1 id=&#34;composed-method-keep-each-routine-at-one-level-of-abstraction&#34;&gt;Composed Method: Keep Each Routine at One Level of Abstraction&lt;/h1&gt;&#xA;&lt;p&gt;A routine becomes hard to read when it mixes two different jobs: describing a process and implementing every mechanical detail of that process.&lt;/p&gt;&#xA;&lt;p&gt;Consider an order checkout function that validates the cart, calculates a total, writes SQL, formats an email, and records metrics in one long block. A reader must move constantly between business intent and low-level mechanics. The code may be correct, yet its structure hides the story of the operation.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
