Welcome to Dream.In.Code
Getting Help is Easy!

Join 86,374 Programmers. There are 1,416 online right now! Ask your question and get quick answers from Dream.In.Code experts. Join the #1 programming help community on the internet! Registration is fast and FREE... Join Now!

Chat LIVE With a Expert
Powered by LivePerson.com

Register to Make This Box Go Away!

Coding Efficiently

 
Reply to this topicStart new topic

Coding Efficiently

tody4me
post 1 May, 2008 - 11:11 AM
Post #1


livin in a gamers wasteland

Group Icon
Joined: 12 Apr, 2006
Posts: 814



When looking at your old programs, or even your current projects, at what point do you say you are done? Where do you consider that you have effectively made the code work as efficiently as you possibly can in the language that you started the project in? On that same subject, when do you stop breaking code into functions? The way I have it, for the most part anyways, everything that is reusable is in its own function, and everything is related to its own objects. I wrote the code in C# to start with, and yeah it could be faster somewhat if I wrote it in C++, but then again it's been years since I've written something really functional in C++. What do you guys do when you're writing something for a company?

This post has been edited by skyhawk133: 1 May, 2008 - 11:13 AM
User is offlineProfile CardPM
Go to the top of the page
+Quote Post


Martyr2
post 1 May, 2008 - 11:34 AM
Post #2


Programming Theoretician

Group Icon
Joined: 18 Apr, 2007
Posts: 3,561

Well you must remember that coding programs and maintaining them is a continuous process that really has no end. But you can usually say that a program iteration is complete when it does a few things...

1) All the requirements laid out before the project was started is completed and the deliverables have been met with satisfaction.

2) The code is in a state where it would be easy for someone to come in later and modify if need be.

3) The code has been thoroughly tested for accuracy and completeness.

4) It is well documented for the future maintenance of the program.

5) It is as efficient as possible given the constraints of your resources (time, budget, hardware, company procedures)

So if you have done everything required of the software, documented it, it is easy to read, maintainable, tested, and as good as it can be given your constraints... then you could easily say it is "done".

smile.gif

This post has been edited by Martyr2: 1 May, 2008 - 11:34 AM
User is offlineProfile CardPM
Go to the top of the page
+Quote Post

mikeblas
post 4 May, 2008 - 07:36 PM
Post #3


D.I.C Head

**
Joined: 8 Feb, 2008
Posts: 94

At some point, you'll also need to consider the responses of your customers.
User is offlineProfile CardPM
Go to the top of the page
+Quote Post

baavgai
post 5 May, 2008 - 04:19 AM
Post #4


Dreaming Coder

Group Icon
Joined: 16 Oct, 2007
Posts: 1,078

“Art is never finished, only abandoned.” -- Leonardo da Vinci
User is online!Profile CardPM
Go to the top of the page
+Quote Post

Fast ReplyReply to this topicStart new topic
Time is now: 5/17/08 02:44AM

Live Help!

Tutorials

Programming

Web Development

Reference Sheets

Code Snippets

Bye Bye Ads

Free DIC T-Shirt

T-Shirt Example

Related Sites

Monthly Drawing

Thumb Drive

Partners

Top Contributors

Top 10 Kudos This Month