• Posts

Pattern Languages

I have replied a linked-in question about the Pattern Languages and since it is a brief information, and people are interested more on this topic, I decided to paste here as well. Pattern Languages are the combination of patterns which address the design coverage for specific (sub)domains. There are pattern languages for parallel programming, distributed computing, resource management and for some others. Nevertheless Pattern languages do not exist for all possible domains yet. A pattern language should cover all the design problems of the targeted domain. They include alternative pattern sequences for the specific areas of the domain. Therefore they are also very useful for reminding us of alternative solutions. Another benefit is to explore and learn the design space of the particular domain which may be new to us.

Friday, June 3, 2016 Read

Effective Code Review

As we all know, code review is maybe the oldest technique to stepping into the software quality assurance realm. Because of the variety of the technologies, project and team sizes, there is no code-review standard. Nevertheless, I would like to share my version I did practice. Disclaimer: This practices make more sense for the projects which use same code-bases over years (product lines) with high maintainability targeted. Peer Review Everybody is familiar with the peer review. Once a developer feels that his/her job is done and ready for check-in; he/she

• Clean Code
• Internal Quality
• Quality Assurance

Wednesday, February 17, 2016 Read

Habitability: A Software Quality Attribute

The term Habitability 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. Readability, 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.

• maintainability
• software architect

Tuesday, June 18, 2013 Read

The Interface Segregation Principle (ISP) with explicit interface implementation

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 maintainability and testability 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!

• maintainability
• testability

Thursday, May 30, 2013 Read

Clean Coder needs more mastery

I would like to share my thougths about this book I’ve read recently. The book is titled The Clean Coder, and its written by Robert C. Martin. Robert C. Martin (aka Uncle Bob) is known to host seminars and articles he posts on his site. And of course the books he published. I presume, the Clean Code and the Agile Patterns, Principles and Practices are well known. I’ve encountered many discussion forums and blogs with the subject of having the Clean Code, based on rules and principles in the book. I also participate in one of these groups that focuses on Clean Coding in our company. I’ve seen groups which categorize his rules and assign ranks similar to the belt system in martial arts for target achievements. I find that going a bit too far as in only following the rules blindly and completely disregarding other elements of software design. I suggest them to read another book of Uncle Bob named “The Pattern, Principles and Practices”

• Clean Code
• Motivation

Sunday, December 30, 2012 Read