|
That's what they said about COBOL programmers until year 2000 came around.
Same thing for supporting legacy C++ applications - someone needs to do it, with millions of lines around. You just can't write everything from scratch!
Inexperienced new hires seem to be really good at screwing up legacy code
|
|
|
|
|
Blake Miller wrote:
That's what they said about COBOL programmers until year 2000 came around.
True, and some old Cobol programmer made a lot of easy cash.
Blake Miller wrote:
Same thing for supporting legacy C++ applications - someone needs to do it, with millions of lines around. You just can't write everything from scratch!
True, but that why you migrate applications to different platforms/language it's not the code, it's the ideas/design and logic that make up a computer application - maybe I'm wrong, I only have 18+ development experience
Blogless
|
|
|
|
|
Sure, if you are migrating. Where I am working, we do not consider a new version of Windows to be a new platform. Nor is the announcement of 'Windows <whatever>' sufficient reason to rewrite 1,500,000+ lines of code. Nor is the announcement that C# or .NET is the 'latest shiny thing' a reason to rewrite 1,500,000 lines of code - ideas or no ideas. So, we need skilled, experienced C++/MFC people to maintain the product that generates this company 80 million dollars a year, and they are getting harder and harder to find. That's all I meant.
I agree, an endagnered species, but also the question implied is there a market out there, and I think the answer is that there is. Not the largest market, but there is a market.
When the time comes to migrate some mission critical code, and no one else out there can understand MFC any more, then sign me up in line to get the $500 an hour 'consulting' to the guys who only know some higher level language or construct to help them inteprpret the existing code base that they have. I would also think with 18+ years experience, you are as familiar as I am about how poorly things are documented, except perhaps in some military systems, where they are perhaps overly documented. I have only been coding since 1981 myself.
|
|
|
|
|
Blake Miller wrote:
then sign me up in line to get the $500 an hour 'consulting'
And me, that's what my retirement plan is
Blake Miller wrote:
you are as familiar as I am about how poorly things are documented
Oh very much so, even the comments in some of the code I have seen and no help.
I suppose my real point is, people who are clinging onto MFC, hoping it has a long and healthy future as disillusioned, it's best to brush up your stills for the technologies that are gaining maturity - that is .net. As you know with your years of experience, you don't want to back yourself into a corner only to find when you finally move to another the company, your MFC skills are somewhat redundant.
Blogless
|
|
|
|
|
Blake Miller wrote:
and they are getting harder and harder to find
Any jobs going?
|
|
|
|
|
|
I Believe, Still people here in India learn there ABC for Visual or Windows programming in Visual Studio 6.0.... so i believe VS6.0 still a mature product
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
cheers,
Alok Gupta
VC Forum Q&A :- I/ IV
|
|
|
|
|
ThatsAlok wrote:
'05
I Believe, Still people here in India learn there ABC for Visual or Windows programming in Visual Studio 6.0
Maybe
ThatsAlok wrote:
so i believe VS6.0 still a mature product
Aged, it's now come to it's end product lifecycle.
Blogless
|
|
|
|
|
norm.net wrote:
Aged, it's now come to it's end product lifecycle.
According To Marketing research product faces four phases in product life cycle:- Introduction..( 1998) Growth(1999-2002) .... Mature(2003--- onward
and Last over ( Still have to come)..
So I believe Vs6.0 still in it Mature Phase
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
cheers,
Alok Gupta
VC Forum Q&A :- I/ IV
|
|
|
|
|
|
norm.net wrote:
Visual C++ 6.0 Product Lifecycle[^]
That's nice but still 3 days to 30-09-05....
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
cheers,
Alok Gupta
VC Forum Q&A :- I/ IV
|
|
|
|
|
ThatsAlok wrote:
That's nice but still 3 days to 30-09-05....
You've got 3 days to hurry up and finished that project, then you can move to VS 2003
Blogless
|
|
|
|
|
norm.net wrote:
You've got 3 days to hurry up and finished that project, then you can move to VS 2003
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
cheers,
Alok Gupta
VC Forum Q&A :- I/ IV
|
|
|
|
|
The downloads we're seeing from our site indicate that about 50% of VC++ developers are still using VC6.
That's scary for us as VC6 is a real pig to develop add-ins for...we've seriously looked into making Visual Lint support everything from VC5 to VS2005, but right now there just isn't enough time to do it!
Anna
Riverblade Ltd - Software Consultancy Services
Anna's Place | Tears and Laughter
"Be yourself - not what others think you should be"
- Marcia Graesch
"Anna's just a sexy-looking lesbian tart"
- A friend, trying to wind me up. It didn't work.
|
|
|
|
|
2000, XP and 2003 are the only systems I'll support for my legacy MFC apps. Whilst Vista isn't out yet, I obviously can't support it on that version. And probably won't even when it comes out, unless there is a a real business need to do so.
Support for the 9x series was abandoned 4 years ago and I won't touch that platform again.
Michael
CP Blog [^] Development Blog [^]
|
|
|
|
|
Michael P Butler wrote:
Support for the 9x series was abandoned 4 years ago and I won't touch that platform again
eee... never will I.
Truth to tell I can't approach a win9x system, makes me dodgy...
|
|
|
|