Get the latest Laravel/PHP jobs, events and curated articles straight to your inbox, once a week
Source: matthiasnoback.nl
Do you have an exit strategy?
Posted on Oct14th2021 by Matthias Noback Famous examples are: And so on...
For a moment we are so happy that we can start using that new tool, but every time we need to change something in this area we have to roll out the same solution twice, for each tool we introduced.
Often developers defend such a decision by saying that the old things will be migrated one by one to the new thing.
When introducing a new thing that is supposed to replace an old thing we have to keep asking ourselves: If not, I think you owe it to the team to consider fixing or improving the old thing instead.
For a moment we are so happy that we can start using that new tool, but every time we need to change something in this area we have to roll out the same solution twice, for each tool we introduced.
Often developers defend such a decision by saying that the old things will be migrated one by one to the new thing.
When introducing a new thing that is supposed to replace an old thing we have to keep asking ourselves: If not, I think you owe it to the team to consider fixing or improving the old thing instead.
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