|
I can't believe that almost 15% of people finishes all the projects they start.
Its really hard to accept.
No offense... please.
Life is a computer program and everyone is the programmer of his own life.
|
|
|
|
|
I'm not one of those. But still, I think it is their perception. What is "finish" and what is "all"? If "finish" means "bring to a clear end (which may be discontinue the whole project) and not walk away before that", then this is well possible.
There is certainly an difference in attitude of "endurance" versus "giving-up" 
Finishing does not necessarily mean to have a success-story.
Cheers
Andi
|
|
|
|
|
Hmmm,
If finish means discontinuing the project for whatsoever reason, then I agree.
But it should not be the case here.
...and you are right, its all about people perception.
Life is a computer program and everyone is the programmer of his own life.
|
|
|
|
|
It makes my tingle feel tingly and happy smile to think "IDEA IN MY HEAD, I WILL BE DEAD AND ROTTEN IT WILL STILL NOT BE FINISHED BUT I CAN DRAG A MAINFORM LOL"  
|
|
|
|
|
Every fiber of being would attack each other if I do not finish things I start. There is no other option
|
|
|
|
|
|
|
But a lot of project I do is for learning and finishing it means that I gained the knowledge I looked for...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
I'm a starter and a finisher. I won't start a project if I think I can't finish it. Why start and waste time if not finishing it? It makes no sense. If manager give me a impossible project, I will honestly tell him it is impossible and not start wasting time.
|
|
|
|
|
Leng Vang wrote: Why start and waste time if not finishing it? It makes no sense
Because you always learn something new.
And is it any better to finish a project that never gets used?
|
|
|
|
|
I like your reasoning. It is something I will definitely consider. Too often I've been put on time sensitive projects which I knew would fail, but thought I'd try and save the world. It can be very heartbreaking when your effort is put to waste.
|
|
|
|
|
I tend to want to fix everything.
I am extremely analytical, and often see simple stupid errors and just want to fix it or develop something better (Not that I ever end up doing it).
I like to scrutinise my work before it gets deployed, which gets me into trouble for missing the SLA. The problem often lies with sequesters not knowing exactly what they want. They tend to have a brain storm of an idea, but haven't got a clue of what's involved. To them it's simple,...
Requester: "I want a screen with text and some boxes where people can put answers to the questions and select options. Oh! and it must look nice. Oh! and can I have it done by tomorrow? It's urgent!!"
Me: What Questions do you want? What are your Lookup Fields? Where must it be deployed? On what server / database must it be stored? Who must have access? Who can modify / update the fields? What Pictures would you like? What validations populate other fields? etc...
Requester: I don't know! Let me find out and I'll get back to you.
Requester (16:30): Ok, this is what we have.
Me: I'll only be able to complete it by 12:00 tomorrow.
Requester: Ok, but please hurry! It's urgent.
Me (Next Day 12:00): There we go, here is the link to the QA site.
Requester: Business decided they don't need it any more!
Me (in my head): AAAAAAHHHHHHHHHHH!
Me (to Requester): Ok, No Problem, Have a nice (in my head - "FREAKING") day.
I Strongly believe in flow charts,... Start, If, Then, Else, Yes, No, End.
|
|
|
|
|
RaveWolf1 wrote: The problem often lies with sequesters
I can only wonder if it is deliberate or a fateful refuse 
|
|
|
|
|
R FLMA !... touché!
Hey! I can't be perfect all the time, gotta give others a turn too sometimes.
I'm generous that way.
|
|
|
|
|
on the project, the mood and the phase of the moon.
Some projects are (as Michael Ende's) the neverending story. Those are almost impossible to finish, but I always get them to deploy / production version, stable and operative. So that customers are happy with the results and consider to pay the bills. As they continue growing, then more sub-projects are created to add functionality.
Conclusion: As others below said, "finished" is relative. But once I start something I always bring it to a successfull point ("finished" or not)
Edit: The only thing it doesn't get ever finished is the CListCtrl (I'll go get my coat )
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
And I thought when you press F5 and if it runs without any problem, you have 'finished' that project...
I am a finisher... like a boss!
|
|
|
|
|
I finish what I'm allowed to finish. But when the feature requests are piling up, where is the finish?
Wrong is evil and must be defeated. - Jeff Ello
(√-sh*t) 2
|
|
|
|
|
Usually I have learnt and heard a lot from my fellow developers of my area, that "If you can write a program, you can make a fortune!". Well, I will disagree with them.
I, am a programmer and I have a good grip on almost all of the languages once can use to develop a software for most of the platforms. But, this is not the end, its not even half way through. Anyone can write a program that a computer can understand, any fool can, but only a programmer will write a program that another human will be able to understand too.
I donot write a software application, just to start another Microsoft, what I do, is to write more softwares to challange myself, to learn more. For example, last week I forced myself to create an email client which I did, it was in WPF (which I have a good grip on; alongwith Visual C#). But, the main thing I didn't know what how to make the UI responsive. I did create a bunch of other applications that used the WPF framework, but this application made me learn a lot. Most specially it gave me a chance to dive into Asynchronous programming and learn the actual code required to make a programming run as an async. Tasks, Threads, BackgroundWorkers, none of them actually work... async, await are the only way out.
This is the major thing, that I do! I write softwares for myself, and on the way, I learn a lot... I try a lot... I pull my hair a lot; exaggeration... This makes my a good programmer as compared to my friends, who just write an application to make money and usually they give up on the very first option (of this survey) and the catharsis I go through has kept me going to the 3rd option. I will make my way to the 5th one to complete all of the projects I start.
Very soon, because a programmer would only end his program, and will compile his release version of software if he has a good grip on the programming language itself and can talk to the compiler. Otherwise he will continue pulling his hairs only, till there is a single strand left to comb.
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
Afzaal Ahmad Zeeshan wrote: the actual code required to make a programming run as an async. Tasks, Threads, BackgroundWorkers, none of them actually work... async, await are the only way out.
You may want to rethink about that statement.
Your time will come, if you let it be right.
|
|
|
|
|
Yes, I've already given a second look at the statement of mine. Why I said that? Well, that is because the application I mentioned here used an HttpRequest to send the email from Gmail servers. That caused a freeze for the WPF UI, until the email was sent.
I used BackgroundWorkers, Tasks, Threads but they all did the same. Never let me do anything while the email was being sent. So, I had to learn these await and async stuff and then it let me work while the email was being sent. That is why I am saying, using these keywords is better, because once the application is loading the resources or downloading them, it won't exit the function it is inside, that is why the UI is frozen. await keyword lets the application to execute other set of commands and procedures when the resource is downloading. That is why, I myself will from now on always prefer the async and await methods.
Thanks anyways, for the reply.  If you find any error in my reply, or anything please do reply.
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
It depends on my spare time, the current projects I'm on, and the phase of the moon.<br />
Lest yer boss be watching what you post out into the cloud and use it for or against ya in an upcoming performance review. 
|
|
|
|
|
Yeah!!
And it applies to most of the people practically.
Whatever the option people choose in survey, this options applies to most of them.
Life is a computer program and everyone is the programmer of his own life.
|
|
|
|
|
I run a small software business and write bespoke systems for all sorts of business - I have no option but to finish what I start, on-time and on-budget. I always go the extra mile to ensure everything is double checked and as bug free as I can make it (even if a project overruns and I have to stand the cost), because remedial work always costs you more in the long run - you win on some and lose on others but ive grown my business steadily year on year for almost 25 yrs now so this works or me, and word of mouth/reputation can be everything - GL all
|
|
|
|
|
Every project I start has two goals:
1. Make a complete and working product
2. Learn something new
I always complete goal #2.
Completing goal #1 is a little more rare. Usually, after I've learned what I could I get bored implementing the details, shelve the project to get back to "later".
|
|
|
|
|
Exactly,
The definition of finishing is "interesting" here...
I don't start NEARLY as many projects as I used to. But I now admit that I will create something for the sake of learning. Once the learning phase is over, I don't care to "finish" (and support) a full project for it.
An example. I have a wonderful outlining tool for Windows. Would love it to work on the Mac and on the iPad. I have been thinking about implementing an HTML5/Javascript and Node.js in order to learn Node.js... Not sure if I would publish it when I got it working... That last 10% of polish takes 90% of the time!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
