Article Preview
Buy Now
| Print: | |
| PDF: |
Feature
Crystal-Clear Code
Issue: 6.2 (January/February 2008)
Author: Jens Bendig and Christian Frobel
Article Description: No description available.
Article Length (in bytes): 29,082
Starting Page Number: 14
RBD Number: 6209
Resource File(s):
6209.zip Updated: Tuesday, January 15, 2008 at 4:47 PM
Related Link(s): None
Known Limitations: None
Excerpt of article text...
Abstract
Today's interfaces support ambiguity. The reason lies in a poor understanding of the roles programmers and users have, combined with a poor understanding of the perspectives code should be looked at while taking those roles into account. This poor understanding surrounds a big black hole: the understanding of what we call a bug.
In the first half of this article, I will try to sharpen the terms: user, using-code, using-code programmer, donating-code, donating-code programmer. I'll try to show that we unfortunately have two separate channels mixed up in our applications: the information channel and the bug channel.
In the second half, I'll show a technical solution to get those channels strictly separated and gain much clearer interfaces. This will lead to code that's a lot easier to read: crystal-clear code.
Preface: Good Interfaces Make Good Using-Code
What is the secret of crystal-clear code? What makes it so easy to read?
When you write a piece of code you are using other code to do it. More precisely: you express what you want in terms of the interfaces other programmers are donating. You have to express your concepts that way.
...End of Excerpt. Please purchase the magazine to read the full article.
Article copyrighted by REALbasic Developer magazine. All rights reserved.
|
