(no subject)
Does having goals really help one with the apparent pointlessness of large parts of life? Maybe there's something to being able to cross an item off of your list, or maybe some of us just need more proactive direction. I did laundry and shopping today, yet I don't feel accomplished. If anything, I am more aware of those things that did not get done today, whether on a list or not. I also can't help but think about those things that I must do tomorrow, or a week from now. The Dogs need to get to the vet for annual shots. Dress code policy has changed at work and I need to go clothes shopping. Dragon Con is 20 some days away and I need to plan for that. Mom's Birthday is 11 days away and I without a gift or a card at this point.
Perhaps that's part of my problem, my focus is in the wrong place. It just feels like there's never rest between things that need to be done . . . no sense of a break.
And work is starting to get busy again with ridiculous amounts of things that can go wrong such that it's a wonder anything gets done at all. Yep, new deploys with new requirements . . . the exceptions to the rule. I'm dreading tomorrow because I'll have 5 pans in the fire and something will be wrong with one or more of them. The programmers will state that the project works on their machine, but the one deployed to the DEV system will have problems. But there will be something funny going on even though I'm building the same code they are and it will consume large amounts of time trying to figure out what.
Meanwhile I'll have several other builds coming in that I also need to tend to, each of which may have problems of its own. Happiness is completing a build and putting it through to QA for TEST, even if it comes back with errors, for in those moments it is in QA it is out of my hair.
And these are systems that are designed to work together and it will be glorious when they do, although not perhaps as originally designed. And I will keep building and deploying them until they do.
Should I keep playing the game and pretending to give a damn? Pretending to have specifications and requirements in advance and time to comply? Or stating the obvious - I cannot do what you ask given such short notice of this. And OH, here's another system that has non-stadard deploy practices making it that much more difficult to manage or operate.
Maybe I should make a list . . .
Perhaps that's part of my problem, my focus is in the wrong place. It just feels like there's never rest between things that need to be done . . . no sense of a break.
And work is starting to get busy again with ridiculous amounts of things that can go wrong such that it's a wonder anything gets done at all. Yep, new deploys with new requirements . . . the exceptions to the rule. I'm dreading tomorrow because I'll have 5 pans in the fire and something will be wrong with one or more of them. The programmers will state that the project works on their machine, but the one deployed to the DEV system will have problems. But there will be something funny going on even though I'm building the same code they are and it will consume large amounts of time trying to figure out what.
Meanwhile I'll have several other builds coming in that I also need to tend to, each of which may have problems of its own. Happiness is completing a build and putting it through to QA for TEST, even if it comes back with errors, for in those moments it is in QA it is out of my hair.
And these are systems that are designed to work together and it will be glorious when they do, although not perhaps as originally designed. And I will keep building and deploying them until they do.
Should I keep playing the game and pretending to give a damn? Pretending to have specifications and requirements in advance and time to comply? Or stating the obvious - I cannot do what you ask given such short notice of this. And OH, here's another system that has non-stadard deploy practices making it that much more difficult to manage or operate.
Maybe I should make a list . . .