Notices
Results 1 to 6 of 6

Thread: programming rules

  1. #1 programming rules 
    Forum Sophomore
    Join Date
    Feb 2008
    Posts
    111
    are there any rules for writing a program?
    if we define such rules that help the o/s and hardware to process the program effeciently and effectively.


    Reply With Quote  
     

  2.  
     

  3. #2  
    WYSIWYG Moderator marnixR's Avatar
    Join Date
    Apr 2007
    Location
    Cardiff, Wales
    Posts
    5,810
    that's a rather general question, don't you think ? can you be more specific ?


    "Reality is that which, when you stop believing in it, doesn't go away." (Philip K. Dick)
    Reply With Quote  
     

  4. #3 programming rules 
    Forum Sophomore
    Join Date
    Feb 2008
    Posts
    111
    by programming rules i meant rules formulated keeping in mind the internal structure of the hardware. optimum use of hardware resources. in what order the resources should be activated to give maximum throughput. to run the program in less time.
    Reply With Quote  
     

  5. #4  
    Forum Masters Degree Numsgil's Avatar
    Join Date
    Jan 2009
    Posts
    708
    Modern hardware is fast enough that the bottleneck is almost always the programmer, not the hardware. So most research involves writing code to be as clean and easily maintained as possible.
    Reply With Quote  
     

  6. #5  
    WYSIWYG Moderator marnixR's Avatar
    Join Date
    Apr 2007
    Location
    Cardiff, Wales
    Posts
    5,810
    don't forget database design : if not constructed with maximum retrieval speed in mind, this could also create a bottleneck
    "Reality is that which, when you stop believing in it, doesn't go away." (Philip K. Dick)
    Reply With Quote  
     

  7. #6  
    Forum Freshman Mach1ne's Avatar
    Join Date
    Feb 2009
    Location
    Miami, Florida
    Posts
    6
    Not sure if this really goes with the post but I felt that it may be a good idea to build a bit off of Numsgil idea (if I'm not mistaken, and if I am, please correct me) that having clean code is very important. Not only does it look nice but it does obfuscate your intentions for who ever is going to look over it next. In my opinion, slow progress on projects can often be caused by poorly written code which then means the next person to build on it has to sift through the code and make sense of it before any work can really be done.

    Also remember to clean up after yourself since some don't have garbage collection, but I'm sure you already knew this.
    Reply With Quote  
     

Bookmarks
Bookmarks
Posting Permissions
  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •