Use source control as much as you can so you can return to a working version when this happens and try again. I also keep copies of the "broken" classes to use as guides for retries
Use source control as much as you can so you can return to a working version when this happens and try again. I also keep copies of the "broken" classes to use as guides for retries
When making architecture changes you'll run into prior decisions that seemed innocuous but now are in your way.
This big a change should take at least a few weeks to finish, keep it small at first and migrate in small steps to avoid getting overwhelmed.
When making architecture changes you'll run into prior decisions that seemed innocuous but now are in your way.
This big a change should take at least a few weeks to finish, keep it small at first and migrate in small steps to avoid getting overwhelmed.
I am very much an architecture purist, and I also know how tempting it can be to start working on that next feature but tech debt can't be avoided for ever on big gam
I am very much an architecture purist, and I also know how tempting it can be to start working on that next feature but tech debt can't be avoided for ever on big gam