|
Up until about 15 months ago, I was 80% engaged in supporting an MFC based desktop application. Myself and a couple of others had written about 95% of the app. Over the last year or so, that support effort has dwindled down to less than 10%. I'm still doing C++ development though for another software product the company sells. That product is not Windows based, though. 
Chris Meech
I am Canadian. [heard in a local bar]
Remember that in Texas, Gun Control is hitting what you aim at. [Richard Stringer]
Nice sig! [Tim Deveaux on Matt Newman's sig with a quote from me]
|
|
|
|
|
|
I guess its code from an other programmer. That's what I'm thinking.;)
|
|
|
|
|
exactly what i was wondering... my assumption is applications developed in now-obsolete languages / frameworks - so i would include ASP 3 as legacy (since currently we do everything in C#/.NET)
|
|
|
|
|
Legacy code: code written for a different era, often using old technologies, that must be maintained because systems depend on it.
Tech, life, family, faith: Give me a visit.
I'm currently blogging about: Conversation With a Muslim
Judah Himango
|
|
|
|
|
At what point does code become "Legacy"? My current company is a startup, we are 3 1/2 years old, and we have written everything in .NET/SQL 2000 (we started with VS.NET beta 2).
There is a significant amount of code that was written in the first 2 years that I hate to touch (it makes me cringe just looking at it).
|
|
|
|
|
Good question. Is it important to have a specific point in which code is called 'legacy'? To me, legacy code is any that I'd prefer to rewrite but leave in place because many systems depend on it.
So while that piece of code I wrote last week might break a few things when refactored, it is not legacy because I can rewrite it without it having huge implications. OTOH, the code I wrote 2 years ago might be rather touchy; I might decide to leave it in place for the sake of keeping things working.
I'm in a similar situation to you. I work for a small company, and we've been writing .NET and SQL code for almost 3 years now. Fortunately, we refactor so much that I don't consider any of my code 'legacy'; I've gone in and refactored and changed nearly every line of code since its original form. Because of that, we have a flexible (although often buggy) codebase that isn't fragile in the least. Personally, I like the flexible/buggy option rather than the fragile/stable way, at least until we near deployment time, at which time it's all fixing and stablizing the code base.
Tech, life, family, faith: Give me a visit.
I'm currently blogging about: Conversation With a Muslim
Judah Himango
|
|
|
|
|
... guess I'm lucky...
Norman Fung
|
|
|
|
|
I now only have one project still active that can be considered legacy code, and that is now slowly getting a MyXaml/C# makeover.
I do miss supporting old code sometimes. I miss the enjoyment of tracking down those obscure bugs. The kind where you have to step through code, one statement at a time, checking every value and wondering who the heck wrote the crap code... only to remember that it was yourself about five years earlier. 
Michael
CP Blog [^] Development Blog [^]
|
|
|
|
|
Michael P Butler wrote:
only to remember that it was yourself about five years earlier
 happened to us all at one stage i reckon!!
|
|
|
|
|
...is that counting Windows 98? 
You must be careful in the forest
Broken glass and rusty nails
If you're to bring back something for us
I have bullets for sale...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
