3 ms·
> But there was a huge positive as well. Without worrying about breaking the original use case, we could hack on the new tool all we wanted without regard for s
by nonethewiser 3y ago
> But there was a huge positive as well. Without worrying about breaking the original use case, we could hack on the new tool all we wanted without regard for stability or reverse compatibility. We got a thorough understanding of how to serve the new use case and why the original tool was designed the way it was
Maybe good for your understanding, but this is pure waste.
- christophilus 3y agoEnhancing understanding is not waste.
- Kinrany 3y agoThis is no more wasteful than discarding a prototype, the only possible problem here is putting too much effort into throwaway code.
- jimbob21 3y agoHow is more thoroughly understanding an important service pure waste? I could agree with inefficient, but definitely not pure waste.
- nonethewiser 3y agoWhat did thoroughly understanding it produce? It consumed a shit ton of resources - what was the product?
- jonfw 3y agoWhat is software development if not thoroughly understanding the problem? Implementation is rarely the hard part