![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Work was work. It went okay, there were some aggravating moments but I also got some stuff done - and I told a project manager something wasn't possible from a technical standpoint, stated the available alternatives, gave my preferred one and why, and he actually took the advice - and more than that, appreciated it, and said so.
That was nice.
Stopped on the way home to sign tax stuff. I will probably file without help again next year but I did want someone to sort the papers out for me once. Having done it, (a) I would not go back to this guy as he is not big on explanations and is a bit abrupt, and (b) I still can read his papers and realize that I should have done it myself. That's okay; it's done and now I know, plus, if he hadn't pestered me to find one paper I didn't have, I'd never have known how much of a difference that not-much made....
Got home and was going to dig up the back yard, which I totally didn't feel like doing. Scott was planning to clean the kitchen and living room, which he totally didn't feel like doing, so he proposed we switch. I was glad to take him up on it but I do think the poor man got the short end of the deal. That back yard is a pain in the you-know-what right now.
Today was not a recreation day, I guess. And I don't even mean that recreation didn't happen. After we finished that, I came upstairs to roleplay...and found myself staring at night-time descs and totally uninspired. In retrospect, I could have done about 14-bazillion things, but I just gave up and logged off. Pathetic. On the other hand, I then got more stuff done around the house, wrote up my character for the Tuesday night game (which may be starting next week), and read more in the book I picked up at the library.
It's a book on risk reduction strategies in software management. I haven't read enough yet to see if it will be as applicable/useful as I'm hoping, but as it's a collection of papers, including several on a model I really want to learn about, I have a good chance.
It's also a lovely, wonderful, absolutely amazing counter for insomnia. Ooof. Okay, more accurately, the introduction and outline is. It's a lengthy section that gives general information, terminology, structure of the rest, and a sample case that is referenced later on. And it is written in true textbook style, dryer than the Sahara desert in most places.
I'm hoping that the individual articles will be a bit less dead than that - goodness knows many other books on the subject manage not to be that way - but if not, I will still get the info from it. :P If it doesn't improve in delivery, however, I will definitely be reading this only for myself, and not arranging to get a copy for the office (as I do for well-written books that I think will help us in some fashion - our VP quite agrees with this approach). I just can't see putting in a book where no one will get past the introductory section, unless I can tell them it gets better, or better still, tell them to read this section and that section and that, and then, if they're interested, they can read the rest.
Some time when they're having a bout of stress-induced insomnia, and need a cure.
That was nice.
Stopped on the way home to sign tax stuff. I will probably file without help again next year but I did want someone to sort the papers out for me once. Having done it, (a) I would not go back to this guy as he is not big on explanations and is a bit abrupt, and (b) I still can read his papers and realize that I should have done it myself. That's okay; it's done and now I know, plus, if he hadn't pestered me to find one paper I didn't have, I'd never have known how much of a difference that not-much made....
Got home and was going to dig up the back yard, which I totally didn't feel like doing. Scott was planning to clean the kitchen and living room, which he totally didn't feel like doing, so he proposed we switch. I was glad to take him up on it but I do think the poor man got the short end of the deal. That back yard is a pain in the you-know-what right now.
Today was not a recreation day, I guess. And I don't even mean that recreation didn't happen. After we finished that, I came upstairs to roleplay...and found myself staring at night-time descs and totally uninspired. In retrospect, I could have done about 14-bazillion things, but I just gave up and logged off. Pathetic. On the other hand, I then got more stuff done around the house, wrote up my character for the Tuesday night game (which may be starting next week), and read more in the book I picked up at the library.
It's a book on risk reduction strategies in software management. I haven't read enough yet to see if it will be as applicable/useful as I'm hoping, but as it's a collection of papers, including several on a model I really want to learn about, I have a good chance.
It's also a lovely, wonderful, absolutely amazing counter for insomnia. Ooof. Okay, more accurately, the introduction and outline is. It's a lengthy section that gives general information, terminology, structure of the rest, and a sample case that is referenced later on. And it is written in true textbook style, dryer than the Sahara desert in most places.
I'm hoping that the individual articles will be a bit less dead than that - goodness knows many other books on the subject manage not to be that way - but if not, I will still get the info from it. :P If it doesn't improve in delivery, however, I will definitely be reading this only for myself, and not arranging to get a copy for the office (as I do for well-written books that I think will help us in some fashion - our VP quite agrees with this approach). I just can't see putting in a book where no one will get past the introductory section, unless I can tell them it gets better, or better still, tell them to read this section and that section and that, and then, if they're interested, they can read the rest.
Some time when they're having a bout of stress-induced insomnia, and need a cure.
