I wrote a post about this a while back. I think one of the problems that engineers (including my past self) contribute to this issue is to put code on a pedastal. Refactoring sounds like a bad thing. Deleting code that isn't legacy code sounds like a bad thing.
What happens when you put working software in front of users though? You get feedback that will result in either a bit of refactoring, or just wholesale throwing out some stuff and rewriting it. Code is a means to an end, not the end itself. The end is to make something useful.
That's not wasted work in my opinion. That's part of gathering requirements. It goes a lot faster when we put working software in front of users, even if that software isn't quite production ready.
I wrote a post about this a while back. I think one of the problems that engineers (including my past self) contribute to this issue is to put code on a pedastal. Refactoring sounds like a bad thing. Deleting code that isn't legacy code sounds like a bad thing.
What happens when you put working software in front of users though? You get feedback that will result in either a bit of refactoring, or just wholesale throwing out some stuff and rewriting it. Code is a means to an end, not the end itself. The end is to make something useful.
That's not wasted work in my opinion. That's part of gathering requirements. It goes a lot faster when we put working software in front of users, even if that software isn't quite production ready.