Forgot your password?

Close
typodupeerror
Programming

When should we ditch our platform? 2

Submitted by
odoketa
odoketa writes "My organization recently had to replace our web developer. It took us an extremely long time to find someone with the necessary skill set. I don't know if this is because of the platform we are running (which I will leave anonymous), or simply the fates conspiring against us. It's easy to assume that languages or platforms are popular based on buzz, but the rubber hits the road when you have to hire someone to maintain that code. How are folks out there determining when they've backed the wrong horse, and getting back on track?"
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

When should we ditch our platform? More

When should we ditch our platform?

Comments Filter:
  • I am currently Project Manager over an area that puts the *L* in legacy. Software is 8-10 years old. Our entire LOB (Line of Business) runs on this and if it fails we might go out in the blink of an eye. I think that there are several things to consider when buying into a particular technology and also understanding that the lifetime is 2-5 years (this is optimistic). Another is that you have to keep the old systems running while building newer ones and also provide migration strategies and roll-out pla
  • The cost of finding, training and maintaining a staff of competent developers should always be calculated into your total cost of ownership. Don't get hung up on what language is "perfect" or the latest thing. FWIW, Microsoft implementations of languages have technical limitations compared to some other tools but the staff are generally easier/cheaper to find.

"He don't know me vewy well, DO he?" -- Bugs Bunny