3 ms·
And it's not even necessarily due to a bad spec. I work on a very large and evolving code base. And part of the R&D process is to throw difference features at
by Spellman 11y ago
And it's not even necessarily due to a bad spec.
I work on a very large and evolving code base. And part of the R&D process is to throw difference features at the product to see if it improves the health. But at the same time we can't break prior features.
It isn't that we had a bad spec. It's that the spec changes as we discover new methods and try out different ideas to continue towards incremental improvement.
I personally have had to forcibly break a script and tell other developers to stop using a particular function because it was archaic and wasn't used in production for several months. And yet, somehow, a month later people would come to me complaining I broke their scripts since it was relying on an old feature we had long depreciated in favor of a much better version.