3 ms·
The only reason I do it is job security. I prefer to know a version of something inside and out, all the strengths and weaknesses. I don't want to spend the tim
by fma 10y ago
The only reason I do it is job security. I prefer to know a version of something inside and out, all the strengths and weaknesses. I don't want to spend the time to learn something new if the current tech stack suffices - it's a risk. I'd rather spend that time building something. But if I don't upgrade/rewrite every few years, and I need to find a new job, the interviewees will look at it and think I'm a dinosaur - despite the fact I follow the latest trends through blog's and podcasts.
My company is slowly upgrading all our application servers because what we were running is way past EOL. The ops team bitches and moans because the newer one is more unstable. Go figure.
- sotojuan 10y agoYep. In a lot of parts of the industry, old and stable is seen as a negative by many. Maybe that's why people don't consider programming "engineering".
- kochthesecond 10y agoYeah, well. A lot of those systems does it's job very well. But now they want to access it's data and calculations on an iOS and browser app. Suddenly it becomes unusable or blocks productivity.
- intrasight 10y agoThere's plenty of work available in wrapping legacy systems with modern APIs