|
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| ||||||||||||||||||||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
#1
|
||||
|
||||
|
When is something finished?
At what point do you consider a personal project finished/complete?
* Is it when it has all the basic functionality you need - though you can still think of more to add? * Or is it when it has all the bells and whistles? * How about when it runs bug free 95% of the time in production? * Or when it simply runs? * Or is it simply when you turn it over to the "other guy" (buyer, other programmer, friend, whatever)? * Or simply when you get bored with it? * Or when you learn/get whatever you wanted to? I have written a basic cms that works perfectly well (in basic testing scenerios) with all basic functionality (login, add articles, display articles, create categories for articles, ect.) but I can think of a million other things to add to it (all of which are easy to do)... but I'm tired of working on it and want to move on to something different. I HATE leaving something only partially done. So I want other opinions. |
|
#2
|
|||
|
|||
|
RE: When is something finished?
you'll never, ever be done. congratulations, you're a programmer.
|
|
#3
|
||||
|
||||
|
RE: When is something finished?
I was afraid you would say that.
|
|
#4
|
|||
|
|||
|
RE: When is something finished?
but its oh so true. What you have to do is establish a goal, somewhere you want it to be, and make it concrete. Yuo can't just say "I want it to be the best", a concrete goal is a requirement, then you keep working at that goal until you get there. Then, you look at other things to allow you to expand upon that goal. That way, you achieve your goal, and are done, but just because you're done doesn't mean you can't improve on it
|
![]() |
| Viewing: Codewalkers Forums > General > General Chat > When is something finished? |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|
|