<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software Architect on Kaan's Blog</title><link>https://kaanbardak.com/tags/software-architect/</link><description>Recent content in Software Architect on Kaan's Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 18 Jun 2013 04:18:20 +0000</lastBuildDate><atom:link href="https://kaanbardak.com/tags/software-architect/rss.xml" rel="self" type="application/rss+xml"/><item><title>Habitability: A Software Quality Attribute</title><link>https://kaanbardak.com/posts/habitability-a-software-quality-attribute/</link><pubDate>Tue, 18 Jun 2013 04:18:20 +0000</pubDate><guid>https://kaanbardak.com/posts/habitability-a-software-quality-attribute/</guid><description>&lt;p&gt;The term &lt;strong&gt;Habitability&lt;/strong&gt; is a “Quality Attribute” that isn’t pronounced often in the coding world. In general the word “Readability” is used because the subtle differences between the two isn’t well known, and this breeds “Maintainability” issues.&lt;br&gt;
&lt;strong&gt;Readability&lt;/strong&gt;, is a “Quality Attribute” that ensures the code can be read by any developer easily. For example: The meanings of the terms Variable, Method and Class and their compliance with readability will improve its understandability and learnability for your team. This becomes more important if your team is large or multi-sited.&lt;/p&gt;</description></item></channel></rss>