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
As a result of some of these, robust code is also:

Comments

Post a Comment

Popular posts from this blog

Java LinkedList class in Collection

-
Image
Java LinkedList class in Collection --  LinkedList class uses doubly linked list to store the elements and data. It provide a linked-list data structure.get free coins thetechieking --  It inherits the AbstractList class and implements List and Deque interfaces in java. --  LinkedList class is non synchronized. --  LinkedList class follow insertion order.  --  LinkedList class can allow duplicate elements to store data. --  manipulation is faster than ArrayList because no shifting needs. Declaration of LinkedList class in java : -- public class LinkedList<E> extends AbstractSequentialList<E>    implements List<E>, Deque<E>, Cloneable, Serializable   Constructors of Java LinkedList :  LinkedList()   LinkedList(Collection c) Methods of LinkedList class : 1) boolean add ( Object element ) : -- It appends the element to the end of the list. 2) void add ( int index, Object element ) : -- It inserts the element at the position
Read more

Java ArrayList class in collections

-
Image
Java ArrayList class in collections --  ArrayList class uses a dynamic array for storing the elements. It inherits AbstractList class and implements List interface in java.  --  ArrayList class can allows random access because array works at  the index basis.  --  ArrayList is non synchronized class in java. --  ArrayList class maintains insertion order to data --  ArrayList can contain duplicate elements. --  manipulation is slow in ArrayList class because a lot of shifting      needs to operation with data.   ArrayList class have three Constructor.    1) ArrayList ( )   2) ArrayList ( Collection c )   3) ArrayList ( int capacity )    Some Methods of  ArrayList class   1) void add ( int index, Object element )    -   insert the specified element at the specified position index in a list.   2) boolean addAll ( Collection c )    -  used to append all of the elements in the specified collection to the       end of this
Read more

Constructors in Java

-
Image
Constructors in Java. -- A constructor is a special method of function  that is used to   initialize an object in java. --  every class has a constructor by default. --  compiler build a default constructor for that class. --  constructor are executed at time of object creation of class.  --  there are no return type in java constructor --  An interface cannot have the constructor in java. --  Constructors cannot be private modifire. --  Constructors name must be similar to that of the class name.   There are 2 type of constructor in Java :     1) Default Constructor.  2) Parameterized constructor.     1) Default Constructor. --  A java constructor that has no parameter is known as default constructor. thats build by compiler. --  if we write a constructor with parameter or non-parameter then compiler does not create default constructor. example of default constructor : class JavaConstructor {        JavaConstructo
Read more