Currently working on a rewrite of an old application (PHP 5.6, was probably written in an even earlier version) by building a new one in PHP 8.3 and migrating all the data across.
I don't usually recommend rewrites but occasionally it's more cost-effective than trying to fix really old code.
Even though I work with legacy code every day, the changes in 8.3 (and libraries that require it) make life so much nicer.
@mctwist My vice is #refactoring other team members’ code when reviewing their merge requests, especially when they’re making a small fix to some grotty #LegacyCode. (Spoiler: it’s all grotty legacy code)
To get started with the new gig, I wanted to take a step back from the existing services and projects to think through what the jobs of the ideal Postgres extension ecosystems of our dreams might look like, and then the tools to do those jobs. I wrote up all that I could think of, plus ideas and recommendations from my Tembo colleagues, in this Gist. I'd love your feedback and additional ideas — especially for anything I missed! LMK what you think!
@ascherbaum@BRicker@theory Is it that they don’t want to work with #Perl, or that they don’t want to work with your particular Perl codebase?
What I’ve seen time and time again is that management doesn’t want to devote enough resources to control the risk of lifting grotty #LegacyCode to a better state. So it just keeps accreting and discouraging those who could make it better.
Dumb question here, I'm looking at tools to find compatibility issues with a project moving from PHP 5.6 -> 8.2.
Does anybody have experience with PHPStan and can explain how I could use that for this task? Is it just a matter of specifying a certain level to run it at? I'm running it but I think it's showing existing problems unrelated to PHP 8.2 compatibility and I'd like to just focus in on problems related to PHP 8.2 compatibility
Someone suggested an alternative name for "legacy code" that reflected the fact it is still providing value long after it was written. I can't remember the alternative name... can you remind me?
The fairytale of legacyland! – want to know more? Holger und Boas haben in Lille ihre Erfahrungen bei der Migration des Backend-Teils einer Legacy Single Page Application auf Symfony und API Platform mit euch geteilt.
Does anyone else enjoy working with legacy code and systems? I really like improving them, or working under the constraints (most of the time). It's often more fun than just installing the latest all-singing, all-dancing framework that does everything for me. But clients with old systems say they really struggle to get support.
You were never much more than a sad slashdot knockoff with less interesting dupes. Nice shitting all over #perl for your complete lack of keeping stuff up to date to add to the class of the place. Byeeeeeee
Note the first two words in the definitions of both “we need to rewrite it” and “#LegacyCode”: “It works.” If it’s profitable, you can pay down #TechnicalDebt with minimum “interest.”
But @ncommander admits #SoylentNews never had a sustainable business or community governance model.
Does #Perl lack millions of cheap commodity #programmers? Yes. But the ones it has are force multipliers.
Bin Softwareentwickler im Bereich Hausautomatisierung/Smarthome/KNX, eher ausschließlich mit #ModernCpp unterwegs. Aber nicht nur neue Projekte (mit C++20) sondern auch #LegacyCode aus einem anderen Jahrzehnt.