|
Define "legacy"
(Other than a concatenated qualifier of one's walking appendage[s] and connected gluteus maximus...)
Especially if yer the only programmer at a locale for 7+ years!
|
|
|
|
|
And I quote: "code that relates to a no-longer supported systems or features".
You'll never get very far if all you do is follow instructions.
|
|
|
|
|
Except for that the stuff I wrote over the last two years has been labeled "legacy" as we move on to "Phase 2" of the project.
You'll never get very far if all you do is follow instructions.
|
|
|
|
|
|
My last job was so bad that I was no longer a software developer and eventually had to leave because of it. I had 6 hours a week allocated for development, the rest was for the 12 to 15 systems I maintained. The worst was a web site with 547 tables, the 2nd worse was a client server application with around 4000 input boxes, most without field validation. When I left it was split up between 4 people.
I don't believe in rewriting software because it is bad or old, but I do believe is software development process and testing disciplines. If we can get it out of the door with near zero bugs, the software will be easy to maintain and eventually become forgotten.
|
|
|
|
|
We have products with long lifetimes. We have products originally developed with Visual C++ 6, now being maintained using Visual Studio 2003, and are still under active maintenance.
One of our current generation products, developed and maintained using Visual Studio 2008, has a current development branch, two maintenance branches, and five branches for OEM development.
I've had library bug fixes that required updating over a dozen branches of code.
We weep for joy when the pointy-haired-bosses finally end-of-life a product, because that means there's one less chunk of legacy code to deal with.
Software Zen: delete this;
|
|
|
|
|
|
Since I strongly believe in the importance of Refactoring I constantly try to implement it whenever I find it possible. Either if it is a bug fix or some new feature which has any sort of dependency on legacy code, I try to get rid of legacy code, aiming to avoid future maintenance nightmares and set the correct basis for more flexible and extendable development. I see it as investment which is certain that will payoff.
Good knowledge of Design Patterns is a great help when trying to minimize legacy code. Of course there are deadlines and priorities which set limitations on the time that you can invest on Refactoring, but if someone gets used on refactoring he can achieve constant decreasing of legacy code.
|
|
|
|
|
|
Though I always try to get rid of legacy codes and implement the new way, Sometimes the way the application was developed and time constraint forces me to stick to the legacy code
|
|
|
|
|
|
when I was trying to move from .NET framework 2.0 to 4.5 I thought I just want to compile code with 4.5 and it will ready to deploy But ... 
There are lot of changes I need to do to just compile my project and after deployment I can see my gridview child controls ID's are created with fashion and it gives me error at many places.
So I say its Increasing...(for old code)
n its Decreasing...(for Just developed code  )
Find More .Net development tips at : .NET Tips
The only reason people get lost in thought is because it's unfamiliar territory.
|
|
|
|
|
.Net framework 2.0 to 4.5? I am pretty sure that you were frustrated with,
"this method is obsolete, it has been replaced by....." at many instances..
|
|
|
|
|
.NET 3.0 was released in 2008, was your company asleep for 6 years?
|
|
|
|
|
DannyVarod wrote: was your company asleep for 6 years?
I was about to be sent to a customer with hardware that got out of stock like 15 years ago (or maybe a bit more). And it is still running several times a month (they don't produce that product each day).
The problem is... whenever something brakes, they will probably have to replace the full monster. Because the hardware is not sold anymore (if you don't have the big luck to find it in Ebay, a garage shop or something like that).
So, yes... pity but yes. There are a lot of companies in the real world that get stick in something with the moto "if it works, don't touch it", it doesn't matter if it is a good or a bad idea.
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.
|
|
|
|
|
DannyVarod wrote: was your company asleep for 6 years?
Visual studio is a product so versioning is must ? mostly on each year they has new version of Visual studio,
Tell me, how many companies are shift instantly to new version ?
I have seen many companies running their 10 years old product still on VB, can we say such companies are still in a deep sleep ? basically expenses on Visual studio license is the decision of management and it is purely depend upon the income/profit come by that product for which we need up gradation.
Find More .Net development tips at : .NET Tips
The only reason people get lost in thought is because it's unfamiliar territory.
|
|
|
|
|
I haven't worked on any.. 
But I was lucky enough to escape from a couple of classic ASP and VB projects.. 
Whether I think I can, or think I can't, I am always bloody right!
|
|
|
|
|
yep, same here. Haven't worked on any
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
