Jeroen Moons shares his advice for getting a legacy codebase under control. It’s full of great information, and my favorite quote is on how the code base came to this: (Emphasis added)
As you poke and prod the area just past the warning sign with a stick, you might wonder: how on earth can anyone have let this happen? Someone must have seen this coming, surely? Were the people who wrote this code that incompetent?
Possibly. But not more so than anyone else. When push comes to shove, however confident people might seem, nobody else knows what they’re doing either.
The whole article is a great read and should be beneficial for when you are tasked with taming the legacy beast.
Join the weekly newsletter and never miss out on new tips, tutorials, and more.
Trouble installing Laravel? You may need to update your composer.json file
Composer recently made a change with the way pre-update-command works and it can cause Laravel to fail to install. Jo…
Stress-free refactoring with Scientist
Shameer C. has a tutorial on refactoring with Scientist. Scientist is an experimental framework for PHP that allows y…