<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Maintainability on Kaan's Blog</title><link>https://kaanbardak.com/tags/maintainability/</link><description>Recent content in Maintainability 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/maintainability/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><item><title>The Interface Segregation Principle (ISP) with explicit interface implementation</title><link>https://kaanbardak.com/posts/the-interface-segregation-principle-isp-with-explicit-interface-implementation/</link><pubDate>Thu, 30 May 2013 15:17:27 +0000</pubDate><guid>https://kaanbardak.com/posts/the-interface-segregation-principle-isp-with-explicit-interface-implementation/</guid><description>&lt;p&gt;The project I am currently working on is a product development project. Our daily work is to add features (or fixing bugs) to our code base which has been around for over 10 years, this is why I’ve been encountering legacy code daily. As one might imagine, when the &lt;strong&gt;maintainability and testability&lt;/strong&gt; of a project of this caliber is low-prioritized, refactoring becomes near impossible after a point. There are of course exceptions to this, some subsystems do renew themselves periodically, lucky for them!&lt;/p&gt;</description></item></channel></rss>