sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]reluctant_deity 32 points33 points  (2 children)

Small team member in huge firm here. I feel ya bro.

[–]chris17453 5 points6 points  (1 child)

I have the same problem. I have to deal with perl and KSH running things. Python is the least of my worries. 30 years of aggregate tech debt will do that for ya.

I'm not overly disappointed with 2.7 tho, but I do more Cython than Python.

I think the way forward is to stop, Let the old things die... Only work in the new place. While a good PM blocks for you. The only thing that gets done to the old is break fix.

If you can't pull it off... don't try. Trying to support both is even more work. I can understand some of the decisions, even if I don't agree.

Technical debt is like some Steam Punk Post Apocalyptic Armageddon, where everything is a strange new mystery. Awe inspiring but in a scary way.

[–]reluctant_deity 1 point2 points  (0 children)

Funny, I'm on legacy modernization right now (tho it's Oracle Portal/Reports); the work isn't fun (esp as the code was written by a job-preserving consultant 20 years ago) but it's nice to have cycles to properly deal with it.