|
"All required functionality is functional. Some functional functionality may no longer be required."
|
|
|
|
|
I finish almost all of my projects, for work.
I have a tendancy to finish some of my projects, for play.
|
|
|
|
|
I work in the industrial field, we don't really have deployed products.
We have a standard software that may be customized for each and every customer (gods bless the ones who like the standard) and mantained. This means that for every standard version we deployed there are several branches of customization trees, some many of which incompatible with each other.
So my job consists in: making quick customizations (button positions, colors, log lines...), making deep customization (entirely new algorithms that work only on a specific product...), improving the standard software generalizing successful customization, adding required functionalities or refactoring for performance, and finally bugfixes.
Having thousands of customers worldwide and being only two people working on the software, finishing something is a luxury.
|
|
|
|
|
If finish means really Done, deployed, never touch it again... no, never worked on a project like that.
I've been always involved in products so they never actually finish.
So for me the concept of finish is when you reach a point when you have more maintenance tasks than actually new developments.
Usually when I reach this phase (or a bit before) it's time to move on.
My concept is to help give birth to the "child", see it do its first steps and move on to make a new one 
|
|
|
|
|
To me "finished" doesn't mean putting out the project to pasture and never see it again. It means I've achieved what I was setting to do for that phase of the project. Whatever you called them: goal, deadline, milestone, expectation, etc. Once it reaches that point, it is finished.
|
|
|
|
|
My open-source projects/articles are a form of A-B test. I can't know in advance what is or is not useful so I put stuff out there and, if it gets a lot of interest, I work on it.
However this does require letting things go as a "sunk cost" if they don't.
|
|
|
|
|
I have trouble starting most projects!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Microsoft never finished Windows and look where they are now.
|
|
|
|
|
OriginalGriff wrote: I have trouble starting most projects!
That's so weird because I'm the exact opposite. I can start anything, and I usually do. But then I get quickly bored with it when it's like an alpha stage and move on to the next adventure.
Jeremy Falcon
|
|
|
|
|
Once I get started, I usually finish - I may multi-task with a couple of projects, but I try to keep the number below about five.
But, getting started can be a pain - I've had a couple of projects just sitting there on the back burner waiting for me to start them (personal jobs, nothing paying money) for a couple of years now - mostly because I can't be bothered to start learning to code Android... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
