4 ms·
> I'd consider a PHP job, but only if they quarantee they don't have any of those legacy maintaining things lying around. I see your point, but there is lots o
by chinathrow 5y ago
> I'd consider a PHP job, but only if they quarantee they don't have any of those legacy maintaining things lying around.
I see your point, but there is lots of legacy code (in any language) laying around and making shit tons of money for their owners - hence the need to maintain these systems.
- herbst 5y agoI love maintaining old rails projects. No worries with that, MVC is making it easy to work with any project done by someone who knows the language. The language allows and encourages updating as well. It can be fun even. PHP had no common way to do anything for a long time and you still see it from people writing PHP today.
- chinathrow 5y agoMy point was more that if there's money being made with some chunk of code, a sensible product owner would allow a modern refactor or even a rewrite in the same language to not endanger the long term success of said app.
- herbst 5y agoI see. Well personally I never witnessed such a product owner. My whole carrier with PHP legacy code evolved around 'never touch a running system' But I like the idea that these people may exist out there :)