![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
I think it's safe to say that today was not the best day I've ever had. This morning my mom had an appointment to see a local doctor, with the goal of finding someone local to manager her blood disorder instead of calling back to Seattle all the time. The appointment was not what you would call a success. Kind of in the same sense that the voyage of the Titanic was not entirely successful. I'll skip the details; suffice to say that my mom will not be returning to that doctor's office.
On the work front, I solved the puzzle of the issue that was blocking any other coding from getting done. So I should be pretty happy about that, right? Well, I guess I'm pleased that I figured out what was going on, and how to keep it from happening in the future. But it's the same piece of crap component that has been the bane of my existence for over a year now, and I am annoyed to have lost another two days of work to it. Tomorrow I will check in one minor change, wrapping the offending component in a try/catch block that will just swallow any exception, and be done with it. If it breaks in production down the road, and it takes months for anyone to notice that it is failing silently, well then I guess that's just fine by me. I have resolved to never, ever touch this component again under any circumstances. If it breaks, someone else will just have to deal with it because I am done.
I've got at least three developers breathing down my neck to get their hands on some new code I finished last week, but which I have been blocked from being able to check in. That blockage was finally removed late in the day today, so I'll finally be able to get that out tomorrow. That should make people happy. It will allow us to break out of our existing framework, while still being able to seamlessly move back and forth between the old and new stuff. I am pleased I got it working, but I fully expect the dev who is now going to be handling maintenance work to take my stuff and improve it to the Nth degree. He does amazing work, and I'm looking forward to seeing how he tweaks this piece.
So that's it. The ibuprofin has finally kicked in so I don't feel like my head is going to explode.
On the work front, I solved the puzzle of the issue that was blocking any other coding from getting done. So I should be pretty happy about that, right? Well, I guess I'm pleased that I figured out what was going on, and how to keep it from happening in the future. But it's the same piece of crap component that has been the bane of my existence for over a year now, and I am annoyed to have lost another two days of work to it. Tomorrow I will check in one minor change, wrapping the offending component in a try/catch block that will just swallow any exception, and be done with it. If it breaks in production down the road, and it takes months for anyone to notice that it is failing silently, well then I guess that's just fine by me. I have resolved to never, ever touch this component again under any circumstances. If it breaks, someone else will just have to deal with it because I am done.
I've got at least three developers breathing down my neck to get their hands on some new code I finished last week, but which I have been blocked from being able to check in. That blockage was finally removed late in the day today, so I'll finally be able to get that out tomorrow. That should make people happy. It will allow us to break out of our existing framework, while still being able to seamlessly move back and forth between the old and new stuff. I am pleased I got it working, but I fully expect the dev who is now going to be handling maintenance work to take my stuff and improve it to the Nth degree. He does amazing work, and I'm looking forward to seeing how he tweaks this piece.
So that's it. The ibuprofin has finally kicked in so I don't feel like my head is going to explode.