When you reach that stage there is no going back to a framework, the change would be too costly with minimal ROI. Its a decision you should make before writing code.
Which is fine when you already know why you want to choose a particular framework and that it will do the job you need.
I also hate being locked in to an approach which means your future options may be constrained.
There may be benefit in us refactoring as a training process and because the early apps really have some weaknesses!
But I get your point, maybe in the end we'll just switch to "the final solution" for the next iteration of development.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
When you reach that stage there is no going back to a framework, the change would be too costly with minimal ROI. Its a decision you should make before writing code.
Which is fine when you already know why you want to choose a particular framework and that it will do the job you need.
I also hate being locked in to an approach which means your future options may be constrained.
There may be benefit in us refactoring as a training process and because the early apps really have some weaknesses!
But I get your point, maybe in the end we'll just switch to "the final solution" for the next iteration of development.