How to write robust code
How to write robust code
As software is one of the most important issues in our era, writing good
robust programs is essential. This article is an in-depth essay focused on
Object Oriented software and large projects. Everything said here, though,
scales well to good directives for small projects as well.
Our time is dominated by software. There is basically software everywhere
around us; most of the object you can see right now around you, have something
to do with software, probably because they were created using some sort of
machine. Given the importance of software nowadays, I just have to find bugs
unacceptable. Of course you might argue that a small and rare bug is a minor
software won’t harm anyone, and is not nearly as important as a bug that could
affect the software of an airplane, and I’m going to agree with that. But as
time goes by, everything has to be going towards perfection, and current trends
about software seem to be going nowhere: there were bugs in software 30 years
ago, and there are today. There was a time, in the beginning, where scientists
thought that it would be relatively easy to write bug free programs right away,
but then they realized pretty soon that it wasn’t quite so. After all, software
is written by us human beings, and we are doomed to make mistakes or omissions.
The point of this article is not that software should be always bug free, but
that we, coders, should always get them to the minimum, and here I’m going to
present some ways to deal with programming in general.
One huge problem, as I’ve faced quite often, is that as a program grows in size
and dependencies, its developers start losing trace of its components, get
further away from the big picture, and ease the introduction of bugs. Note, I’m
not talking here about bugs caused by a single human error that can be labeled
as a cheap error by anyone who would look at the code. I’m talking about the
sort of nasty bugs that nobody can spot right away with a glance at the code.
I’m talking about system wide bugs, usually emerging as a result of hardly
related subsystems of the program. Usually connections between dependencies and libraries.
Anyway, the path to write bug free code, is the one you step when you write
robust code. What do I mean by that? Robust code has some features:
- Well designed
- Neat and tidy
- Well named
- Well commented
- Well tested
- It never segfaults
- Exstensible
- Reusable
- Lasting in time
- referenced by :http://www.iovene.com
Comments
Post a Comment