Two Tips to Avoid Big Refactorings in Laravel

Some thoughts and two tips how to avoid big code changes in the middle of the project.
Related links:

- - -

[TristanBailey]

When approaching a Refactor, always try and move one part at a time to change. So if you refactor the frontend, keep the backend stable, if want to change an api, try not to change in the internal code at the same time. It makes testing and understanding the scope of the change so much easier.
Sometimes this can mean pausing other teams or at least not merging and releasing at the same time.

[VaidasLungis]

Use policy / gate instead of scope admin?