|
i am working in product based organisation and here we keep updating products.Integrating modules and creating builds,demos and certification...continue and continue...
|
|
|
|
|
it won't end until you quit or the company goes belly up. Neither has happened yet.
--
Kein Mitleid Für Die Mehrheit
|
|
|
|
|
Well, keep trying Jörgen. 
I hope you realise that hamsters are very creative when it comes to revenge. - Elaine
|
|
|
|
|
Dammit, I'm working on it! No matter how much money and resources they throw at me, they keep coming back with more!
--
Kein Mitleid Für Die Mehrheit
|
|
|
|
|
It all depends on the complexity of the project. My engineer assigned me to finish his project that involves heavily on windows messaging. I have very little understanding in that part. Sheesh! That enlongates my completion of the project.
|
|
|
|
|
I'm current working on 3 new projects.
I'm also rewitting and adding new features to at least 6 others. I'm sure some of you are in the same position.
I write software and design the hardware to boot for production line manufacturing across europe so there is a lot of different products to surport.
Why is it when you are busy everyone whats it yesterday, But when your not no-one has any work for you?
|
|
|
|
|
...they get new names and carry on.
And just when you think it's finished they decide to get new hardware or a new language, so you can start again.
------------------<;,><-------------------
|
|
|
|
|
I have been working more or less continually on the same product since I joined the company five years ago; the product was some years old even then.
If the product is the project then it is never ending. We are, sort of, proposing a whole new structure and a complete re-write to take advantage of newer technologies but that could take at least two, perhaps three years to accomplish; it is a big product.
If a new or improved feature is a project then from a few days to a few months is a typical development cycle.
We (a team of five) tend to release a new product version to our customers two or three times a year.
|
|
|
|
|
We've done coding for approx 8 months .. but the stabilization is going on from the last 6 months .. with approx 7200 bugs.
|
|
|
|
|
goddamit, that's the age of a good whisky.
Personally, I love the idea that Raymond spends his nights posting bad regexs to mailing lists under the pseudonym of Jane Smith. He'd be like a super hero, only more nerdy and less useful. [Trevel]
| FoldWithUs! | sighist | µLaunch - program launcher for server core and hyper-v server
|
|
|
|
|
No whisky is old enough to taste good. That's all I have to say about that.
--
Kein Mitleid Für Die Mehrheit
|
|
|
|
|
Well, it's an aquired taste.
Personally, I love the idea that Raymond spends his nights posting bad regexs to mailing lists under the pseudonym of Jane Smith. He'd be like a super hero, only more nerdy and less useful. [Trevel]
| FoldWithUs! | sighist | µLaunch - program launcher for server core and hyper-v server
|
|
|
|
|
|
Only when you get fired or you resign. 
|
|
|
|
|
No, not even then. I got laid off in January and now they have me adding features on a contract basis.
|
|
|
|
|
Actually, about a month to recode the upgrade, BUT the genius director of I.T. stonewalled the user testing and installation for eight months.
I'll not burden you with the tales of woe that an exceptional version of the Peter Principle can cause to the IT department and entire corporate environment.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"As far as we know, our computer has never had an undetected error." - Weisert
"It's a sad state of affairs, indeed, when you start reading my tag lines for some sort of enlightenment. Sadder still, if that's where you need to find it." - Balboos HaGadol
|
|
|
|
|
Our product is for resale rather than bespoke, so there's no obvious (I hope!) endpoint.
Here's our timeline (so far):
Sep 2004 - *The Big Idea*
Oct 2004 - Feasibility Study
Jan 2005 - First internal build
May 2005 - Added a page about our new product to our public website; potential beta testers started contacting us to ask for information
Nov 2005 - v1.0 public release and first sales (VS2002/VS2003/VS2005 supported)
Nov 2006 - v1.5 public release (added a Professional Edition product and support for VC6)
Jan 2007 - Added support for eMbedded Visual C++ 4.0
Oct 2008 - v2.0 public release (added an Enterprise Edition product and support for IncrediBuild)
Jan 2010 (?) - v2.5 public release (adds support for Visual Studio 2010)
modified on Monday, October 26, 2009 7:28 AM
|
|
|
|
|
Actually in product based small scale organization product versions are updated frequently ....
so projects either taking LONNGGGGGGG time to finish or has an endless program.
what abt your organisation ???
regards
koolprasad2003
If the message is useful for U then please Rate This message...
Be a good listener...Because Opprtunity knoughts softly...N-Joy
|
|
|
|
|
Well I have done several projects in last two and half years, but over 80% of my work was put into one larger.
Project itself was conceived in 2006 and it went through several hands, I feel like I am stuck in it. Generally speaking it was finished some 10 months ago, but managements wants more features even though people were willing to pay for it while it was in beta.
modified on Thursday, April 14, 2011 7:23 AM
|
|
|
|
|
My last project took less than a month, so did the one before that... but I also have projects that have been ongoing since I joined the company back in 1998 -- I just finished moving one module from BC5 (including a db library Btrv++) to VS2008...
So, some projects are over quickly, others will follow you to the grave, throwing dirt on your casket...
Projects never die, they'll just enter maintainance phase...
|
|
|
|
|
Jonas Hammarberg wrote: others will follow you to the grave, throwing dirt on your casket...
and the bug reports are the maggots eating your corpse...
Software Zen: delete this;
|
|
|
|
|
What bugs?
--
Kein Mitleid Für Die Mehrheit
|
|
|
|
|
This survey is just limited to the last project only.
While this should be general.
Cause what happened - the last project that I worked take 6 months and the previous last took 1.5 yr.
IMO the question should be like this,
- The longest project ever you worked on. or something which is related to the longest time taken for a project to finish.
I think you also intended the same.
Believe Yourself™  ™
|
|
|
|
|
|
For me the largest was 4 years and 250K lines of code that I wrote. There were two other programmers on the project briefly that wrote about 3 libraries for the project that totaled about 25K lines. I can tell you that I spent so many 80 hour weeks on this to get everything working but I was young. This was my first large scale project.
The project was a telemammography system that included a lot of different technologies. SQL, ADO, COM, RAS, modems, TCP/IP, encryption, directdraw.
John
modified on Thursday, October 29, 2009 9:13 AM
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
![Rose | [Rose]](https://www.codeproject.com/script/Forums/Images/rose.gif)
