<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Object-Oriented Programming on Nalar</title>
    <link>https://nalar.dev/tags/object-oriented-programming/</link>
    <description>Recent content in Object-Oriented Programming on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 03 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/object-oriented-programming/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Design Managed Attributes in Python with property</title>
      <link>https://nalar.dev/design-managed-attributes-in-python-with-property/</link>
      <pubDate>Thu, 03 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/design-managed-attributes-in-python-with-property/</guid>
      <description>&lt;p&gt;Python code often starts with plain public attributes. That is usually a good default: &lt;code&gt;order.total&lt;/code&gt; is simpler than a pair of trivial getter and setter methods when reading and writing the value needs no extra behavior.&lt;/p&gt;&#xA;&lt;p&gt;Requirements can change. A value may need validation, an attribute may become computed, or an existing public field may need to keep its interface while its internal representation changes. Python&amp;rsquo;s built-in &lt;code&gt;property&lt;/code&gt; type lets a class place method logic behind normal attribute access.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
