Post
Tue Aug 14, 2018 2:34 pm
#113
by Triscopic
@Talvieno Thanks for posting the log.
@Josh I don't post much but I thought it might cheer you up to know what you've done - it happens to big software houses too. I work for a company which has employs several hundred software engineers building pretty complex software.
Recently we needed to rework a particular area. Several approaches were suggested and small teams went off to prototype stuff. A couple of solutions stuck out, and one was deemed optimal. About a dozen people people worked on it, and... it just didn't scale up as expected. The sprint was basically a write off, and we ended up implementing the other idea which scaled much better. Lessons were learnt, and senior management just had to accept that sometimes, to be the best, you end up going down the wrong path. Being the best isn't about getting it right first time every time, it's about being willing to throw away your sub-optimal first try and starting over if and when that is the right idea.
Basically, welcome to the "aah, balls, that was a costly mistake" club. Even big software teams do that sometimes.