Too Many Changes
I've been working on a few changes to the code for these projects at work and I've gotten myself to a point today that I've tested everything, but there is so much to release it's going to be a pain in the morning. I've changed more than I probably should have for one day, and while I'm not worried about the changes working (I have tested them), there are still a lot of things to do when rolling out new versions of the apps that it's going to be a very busy morning tomorrow to get everything done in time for the first traders.
Thankfully, I stopped changing things when I realized that I'd pushed the limits, and so I've had time to write everything up, update the docs, and make a good To Do list for tomorrow morning. I'm pretty sure I've got everything covered, but it's going to take a bit of final testing to make sure that everything's OK in the morning.
Yikes!
On a lighter note, it's interesting to see how interdependent everything is when you build a large number of large systems and each feeds data into the other. Yup, it's circular data time, and it just makes keeping things straight that much more important. However, it is interesting to see that all these systems work together to get the complete job done. Of course, no user is really interested in the least, but they aren't really supposed to either.
From here on out, I'll be planning my daily changes a little more carefully so as not to get into this spot again. Just a little bit uncomfortable this afternoon keeping everything straight.