![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Lately I have found myself feeling like I am juggling chainsaws on a highwire. Taking care of Ben. Taking care of mom. Trying not to lose Kris in the shuffle. Tending to various and sundry crisis on either of the websites that I run (Look! A hacker defaced JamesAxler.com! Look! Someone went psycho on the Pat Pack board! *argh*). Have I mentioned work? I either find myself blocked (frequently because of the time difference, and having to wait until late afternoon for a particular meeting before I can do anything constructive), or else I find myself buried. Amidst all of this, I am finding more frequently that a message has dropped through the cracks that I really meant to respond to or deal with. Not so good.
A few days, however, someone asked a question in the green about taming their inbox. In one of the responses, somebody linked to a white paper on managing incoming email. One of the major points, which I had never really thought about before, was that what really matters isn't the volume of email, it's the message count (the number of emails currently sitting in the inbox). The comparison was made to the old video game Tapper, where you control a bartender trying to keep up with the increasing demands of customers. It's not how many beers he has served up that counts, it's how many thirsty customers he has currently waiting to be dealt with.
There was quite a bit more, but in a nutshell I have decided to try to archive my messages better and to not use the inbox as a storage area. Clearing out the message load in my personal email was fairly easy, I only had a few hundred messages in there to be scanned through. Cleaning out my work inbox is a different beast entirely. When I started the process two days ago I had nearly 8,000 messages sitting in my inbox. EEK! I have begun plucking away at them, and have reduced the count by over 1,000 messages so far. I'd say perhaps 3/4 of the messages I have deleted, with the rest being archived properly in relevant sub-folders where I can find them quickly in the future if need be. I would guess that it is probably going to take me several weeks to get through my work inbox.
But even with what I have done so far, it has reduced my stress at least a little bit. So that's good.
In other news:
Mom's PT level has been remarkably stable for the past three weeks. For three Thursdays in a row she has come in at either 4.4 or 4.5, which is exactly where the doctors want her to be. So that's nice. As for her back/leg pain, the muscles have at least finally loosened up. She is still having some pretty serious nerve pain, but the chiropractic seems to be making progress. The chiropractor gave her some different excercises to do this weekend, and hopefully by Monday she'll be able to bear some traction which will help relieve the current pressure points. I need to make an appointment with the chiropractor myself, my lower back has been bothering me a bit lately, and I'd rather catch it before it goes out completely and knocks me out of working for days on end.
My sister announced her engagement last weekend. She is getting married on June 25th to a guy she went to high school with. I remember him from way back when, and I am just assuming that he has grown up a bit in the past two decades. He would pretty much have had to... Seriously, from what I have heard he seems like a good guy, he makes my sister happy, and I think he will be a good influence on both of her kids in general and Miles in particular (he could really stand to have a strong, positive male influence in the house). So that's nice for her. I'll be up in Seattle for the week leading up to the wedding.
I will also be in Seattle for work from March 21st - 25th. The first night I definitely have booked, and probably the second night as well. If there is anybody who has a burning desire to see me while I am in town, drop me a line and we can figure out a time. Odds are I will be staying downtown right next to the Cheesecake Factory and I won't have a rental car, so you'll have to come to me.
It also looks like plans for Kris' and my wedding are starting to firm up. We're looking at the last week in July, but don't bother clearing your schedule; neither of us is interested in a big wedding (read: any kind of wedding in which people actually attend). We are happy to take cards and gifts (and cash!!!), but the extend of anybody sharing the day with us is probably going to be a friendly email from us mentioning that we got hitched. Then we are going to jet off to New York and spend a week or so seeing Broadway shows and wandering around the city. Yay!
Well, that's all I got for today. Time to go put Ben to bed. G'nite.
A few days, however, someone asked a question in the green about taming their inbox. In one of the responses, somebody linked to a white paper on managing incoming email. One of the major points, which I had never really thought about before, was that what really matters isn't the volume of email, it's the message count (the number of emails currently sitting in the inbox). The comparison was made to the old video game Tapper, where you control a bartender trying to keep up with the increasing demands of customers. It's not how many beers he has served up that counts, it's how many thirsty customers he has currently waiting to be dealt with.
There was quite a bit more, but in a nutshell I have decided to try to archive my messages better and to not use the inbox as a storage area. Clearing out the message load in my personal email was fairly easy, I only had a few hundred messages in there to be scanned through. Cleaning out my work inbox is a different beast entirely. When I started the process two days ago I had nearly 8,000 messages sitting in my inbox. EEK! I have begun plucking away at them, and have reduced the count by over 1,000 messages so far. I'd say perhaps 3/4 of the messages I have deleted, with the rest being archived properly in relevant sub-folders where I can find them quickly in the future if need be. I would guess that it is probably going to take me several weeks to get through my work inbox.
But even with what I have done so far, it has reduced my stress at least a little bit. So that's good.
In other news:
Mom's PT level has been remarkably stable for the past three weeks. For three Thursdays in a row she has come in at either 4.4 or 4.5, which is exactly where the doctors want her to be. So that's nice. As for her back/leg pain, the muscles have at least finally loosened up. She is still having some pretty serious nerve pain, but the chiropractic seems to be making progress. The chiropractor gave her some different excercises to do this weekend, and hopefully by Monday she'll be able to bear some traction which will help relieve the current pressure points. I need to make an appointment with the chiropractor myself, my lower back has been bothering me a bit lately, and I'd rather catch it before it goes out completely and knocks me out of working for days on end.
My sister announced her engagement last weekend. She is getting married on June 25th to a guy she went to high school with. I remember him from way back when, and I am just assuming that he has grown up a bit in the past two decades. He would pretty much have had to... Seriously, from what I have heard he seems like a good guy, he makes my sister happy, and I think he will be a good influence on both of her kids in general and Miles in particular (he could really stand to have a strong, positive male influence in the house). So that's nice for her. I'll be up in Seattle for the week leading up to the wedding.
I will also be in Seattle for work from March 21st - 25th. The first night I definitely have booked, and probably the second night as well. If there is anybody who has a burning desire to see me while I am in town, drop me a line and we can figure out a time. Odds are I will be staying downtown right next to the Cheesecake Factory and I won't have a rental car, so you'll have to come to me.
It also looks like plans for Kris' and my wedding are starting to firm up. We're looking at the last week in July, but don't bother clearing your schedule; neither of us is interested in a big wedding (read: any kind of wedding in which people actually attend). We are happy to take cards and gifts (and cash!!!), but the extend of anybody sharing the day with us is probably going to be a friendly email from us mentioning that we got hitched. Then we are going to jet off to New York and spend a week or so seeing Broadway shows and wandering around the city. Yay!
Well, that's all I got for today. Time to go put Ben to bed. G'nite.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
From:
no subject
It's not just you, or being remote. Our workflow process in many ways sucks the sweat off of a pig's balls. Take this week for example, once we got past the release. BWillie got some coding done late Tuesday, which made it into the midnight build, and could have concievably been tested starting Wednesday morning—except that before it was testable, Kurt needed to get part of the wizard done to get campaigns' statuses able to be assigned. That didn't happen until noon today- which meant that, for all intents and purposes, once i got Serena to poke the 'submitted' status into all the campaigns in test, the only new filter items which could be tested were the drop date parameters and job numbers.
And then there was the discussion yesterday morning (Seattle time) about the three of you all needing to make modifications to the same page at the same time.
That's not an efficient use of resources. In fact, that's an asinine misuse of resources. When there are three developers working on a project that will encompass a dozen different elements, it should have been possible for each of you to work on, for example, different components of the wizard— which, in turn, would have produced something tangible for test.
Instead, we dorked around with this week's user stories, and ended up at demo time on Friday with untested code being shown off from a developer's localhost build because there wasn't anything checked in and complete enough to have been built and deployed otherwise.
Of my 40-hour work week, I spent approximately two hours actively working on testing the project's progress this week. That's simply unacceptable, and it's why i spend as much time bitching about my workflow as i do. Even last week- when things went more smoothly, there was realistically no testing which could practically be done before noon Wednesday, which has the unfortunate effect of backloading my week to the point where i spend Thursday and Friday scrambling around like a chicken with my head cut off, and things are falling through the cracks.
Eventually QA will be able to fill our open headcount. When that happens, one of the new people is going to rotate on to Campaign Management, and i'm rotating out of daily involvement in ongoing new development to handle Triage, and the talented Ms. Ross is going to continue to be the maintenance/release PM. That means that there's a space for a developer to work hand-in-hand with us on getting issues identified through triage fixed. We're unquestionably certain that we know who we want that developer to be. Any objections- if we can swing it- to becoming the triage team's dev? (And, gee, doesn't this look as if we're reinventing Maintenance?)
From:
no subject
I would be thrilled to be the Maintenance Triage team's dev.
From:
no subject
I would love to see you, but I won't get my sched until the week before.
I'll just be crossing my fingers until then.
--
Adding more to your burdens...
I'd really love to see some recent pictures of Ben when you have a chance to put them up. I miss getting to see them fresh from the developer.
From:
no subject
From:
oh no you don't
The. Hell.
You got away with sneaking the first one past me. I am not missing the one that counts.
From:
Re: oh no you don't
If you don't still have your Indiana Jones hat let me know and I'll pick up another one for you before I meet you at the airport.
From:
Re: oh no you don't
...
I would be honored to accept. Thank you.
I will begin living like a bum to scrimp and save for the airfare immediately.
Oh, no, replaced that before I even left, remember? Just don't have the macthing bullwhip yet.
From:
Re: oh no you don't
I remember very well picking up Hat 2.0, but that was going on two years ago. I just wasn't sure if it had survived the intervening time, and I know that that particular hat was the one you needed for survival in the Florida summer sun.