We recently came across a piece of our application that hasn’t been working for two years or more. I would say, that since it hasn’t been working for so long, and obviously it hasn’t been a high enough priority to fix, that we should just remove that crusty old code. However, instead of doing that, we are resurrecting that piece of functionality, of course.
At what point can you say “You know, this isn’t really a core piece of our platform, it hasn’t been useful to the majority of our customers for years, let’s just dump it and not spend cycles clearing out the cobwebs”? If you build it they will come; if you fix it, they will flock back to it. Is that how this is supposed to play out?
Originally Posted on my Blogger site June of 2017