Get the latest Laravel/PHP jobs, events and curated articles straight to your inbox, once a week
Source: matthiasnoback.nl
Successful refactoring projects - Prepare to stop at any time
Posted on Feb17th2021 by Matthias Noback A common case of refactoring-gone-wrong is when refactoring becomes a large project in a branch that can never be merged because the refactoring project is never completed. The refactoring project is considered a separate project, and soon starts to feel like "The Big Rewrite That Always Fails" from programming literature.
They want to see it before they believe it, and review every single part of it before it can be merged.
One way to make sure that you always add value to the project is to establish goals for which the following is true: We'll take a closer look at refactoring goals in the next article.
They want to see it before they believe it, and review every single part of it before it can be merged.
One way to make sure that you always add value to the project is to establish goals for which the following is true: We'll take a closer look at refactoring goals in the next article.
Newsletter
Glimpse
Glimpse streamlines Laravel development by seamlessly deploying GitHub pull requests to preview environments with the help of Laravel Forge.
Community Partners
Laravel/PHP Careers