Ugh
I've made a mistake. I was tasked with going over one of my old projects (the first one that I wrote from scratch) and consolidating the code bases to bring everything up to speed. Of course, I couldn't just leave it at that. It's my baby. So I looked at the poor excuse for a resource management system that I had in place and decided I wanted to redo it. It couldn't POSSIBLY take that long to do, right? Silly me.
Here I am, I think over a month behind schedule with this, and I'm still chipping away. Bit by bit, piece by piece, redefinition by redefinition. It's agonizingly slow, and doing it this way mocks me, because I know it's my own poor planning that is making this take so damn long. I have an idea that I think will be quick to implement and I get about halfway through it before I realize that this change will require these other two changes. So I get to work on them, only to realize... etc. etc. etc.
This is exactly the type of behavior that I'm going to look to squash in other people if/when I move forward with this whole "efficiency" thing. I know better. This code-and-fix BS is for amateurs. Unfortunately I seem to have fallen into the same trap that's captured all of our engineering team. The mantra of "Get it done QUICKLY", instead of "Get it done RIGHT". Had I taken that first week planning out my changes, I could have seen how long it would have taken, known exactly what I needed to do, and I could have done it. Or I could have just said screw it, the resource management system is crappy but it works, let's just run with it. The damn game has already been sunsetted on two carriers (makes me sad :( ), and I doubt it's tearing up the charts on the rest of the carriers.
But it's my baby. It reflects my ability as an engineer. Yes yes, it was my first attempt at anything so large, but I still feel responsible for every hour of overtime people have had to put in just so they could get it to run on some device or another. So I'm going back and revamping it.
And I'm apparently eroding bits of my sanity away along with all the cleanup I'm doing.
Here I am, I think over a month behind schedule with this, and I'm still chipping away. Bit by bit, piece by piece, redefinition by redefinition. It's agonizingly slow, and doing it this way mocks me, because I know it's my own poor planning that is making this take so damn long. I have an idea that I think will be quick to implement and I get about halfway through it before I realize that this change will require these other two changes. So I get to work on them, only to realize... etc. etc. etc.
This is exactly the type of behavior that I'm going to look to squash in other people if/when I move forward with this whole "efficiency" thing. I know better. This code-and-fix BS is for amateurs. Unfortunately I seem to have fallen into the same trap that's captured all of our engineering team. The mantra of "Get it done QUICKLY", instead of "Get it done RIGHT". Had I taken that first week planning out my changes, I could have seen how long it would have taken, known exactly what I needed to do, and I could have done it. Or I could have just said screw it, the resource management system is crappy but it works, let's just run with it. The damn game has already been sunsetted on two carriers (makes me sad :( ), and I doubt it's tearing up the charts on the rest of the carriers.
But it's my baby. It reflects my ability as an engineer. Yes yes, it was my first attempt at anything so large, but I still feel responsible for every hour of overtime people have had to put in just so they could get it to run on some device or another. So I'm going back and revamping it.
And I'm apparently eroding bits of my sanity away along with all the cleanup I'm doing.