<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>work</title>
  <link rel="alternate" type="text/html" href="http://domesticat.net/taxonomy/term/167"/>
  <link rel="self" type="application/atom+xml" href="http://domesticat.net/taxonomy/term/167/atom/feed"/>
  <id>http://domesticat.net/taxonomy/term/167/atom/feed</id>
  <updated>2007-10-28T14:19:19+00:00</updated>
  <entry>
    <title>What is true of reservoirs</title>
    <link rel="alternate" type="text/html" href="http://domesticat.net/2008/06/what-true-reservoirs" />
    <id>http://domesticat.net/2008/06/what-true-reservoirs</id>
    <published>2008-06-15T06:31:43+00:00</published>
    <updated>2008-07-12T16:30:49+00:00</updated>
    <author>
      <name>domesticat</name>
    </author>
    <category term="camping" />
    <category term="seattle" />
    <category term="travel" />
    <category term="washington" />
    <category term="work" />
    <summary type="html"><![CDATA[<p>One a.m.<br />
"This is a good life," I whisper to myself.  I'm not certain I always believe it, but tonight I think I do.<br />
Stephen's DCTV shoot was today; I got up this morning and headed cross-town with Jeff for a taping of scenes for a live-action version of 'Code Monkey.'  I tired rapidly in the latter half of the shoot, and was grateful when Stephen rearranged the shoot order to get the backing band (read: Jeff, among others) finished up.<br />
Dinner was at 5:30 at Stephen and Misty's.  We didn't get home until a little after four, and I suspected I was making an imprudent choice when I lay down for a nap, but I did it anyway.<br />
I woke up nearly five hours later, and was grateful to learn that jeff had brought back some of Misty's soup for me.  I ate it on the couch while re-watching a favorite TV episode with Jeff.  We talked, absently, of our upcoming trip to Seattle.  Of food.  Of life in general.</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>One a.m.</p>
<p>"This is a good life," I whisper to myself.  I'm not certain I always believe it, but tonight I think I do.</p>
<p>Stephen's DCTV shoot was today; I got up this morning and headed cross-town with Jeff for a taping of scenes for a live-action version of 'Code Monkey.'  I tired rapidly in the latter half of the shoot, and was grateful when Stephen rearranged the shoot order to get the backing band (read: Jeff, among others) finished up.</p>
<p>Dinner was at 5:30 at Stephen and Misty's.  We didn't get home until a little after four, and I suspected I was making an imprudent choice when I lay down for a nap, but I did it anyway.</p>
<p>I woke up nearly five hours later, and was grateful to learn that jeff had brought back some of Misty's soup for me.  I ate it on the couch while re-watching a favorite TV episode with Jeff.  We talked, absently, of our upcoming trip to Seattle.  Of food.  Of life in general.</p>
<p>Jeff went to bed hours ago, and I settled in with a book.  Books are accessorized with felines in this household; Tenzing and Edmund both are attracted to the stillness and quietness they engender in 'their' humans.  As a result, I've been pinned here for a few hours, turning pages amidst kitty bathing sessions that subsided, eventually, into the amusing, soft sounds of kitty snoring.</p>
<p>I'll sleep again soon.  Probably within the hour.  While I'm awake, and have barrelled my way through a great deal of <cite>Kushiel's Mercy</cite> tonight, the tiredness is still there.  I feel it in the set of my shoulders and how my fingers seem to always rub my eyes a little harder than is absolutely necessary.</p>
<p>When we don't rest enough, mentally or physically, we can subsist on our reserves for a while.  What is true of reservoirs is true of people; draw down more deeply than you replenish, and eventually you run dry.</p>
<p>I think perhaps I have played my game a little too close.  Early this year I calculated what it would take for me to be able to do the two major trips we wanted to take this year.  My workplace only allowed us to carry 120 hours of vacation time at once.  I wrote out a spreadsheet and calculated exactly what I would need to make these trips work, and the answer was clear:  no vacation time between January and July.  None.  The reward would be two extraordinary trips in one year:  over a week each in Seattle and Hawaii. </p>
<p>I fly in about forty days; forty, the Old Testament way of saying "How long?  We don't know exactly how long, but it was a while."</p>
<p>It is a good life.  I am tired, and I am drawing hard on my reserves, but it is still a good life, and soon?  Soon, there will be water, mountains, city, and sky.  I will stare into the campfire I share with friends and it will have been worth it.  Every moment.</p>
<p>For now, though, life is what it is.</p>
    ]]></content>
  </entry>
  <entry>
    <title>Overheard</title>
    <link rel="alternate" type="text/html" href="http://domesticat.net/2008/01/overheard" />
    <id>http://domesticat.net/2008/01/overheard</id>
    <published>2008-01-28T14:01:11+00:00</published>
    <updated>2008-01-28T14:01:11+00:00</updated>
    <author>
      <name>domesticat</name>
    </author>
    <category term="cliches" />
    <category term="geekery" />
    <category term="quotes" />
    <category term="work" />
    <summary type="html"><![CDATA[<p><strong>Amy:</strong>  "You're such a cliché, Charles."<br />
<strong>Sherry:</strong>  "Yeah!  There you are, with your Admiral Ackbar profile photo, sucking down your Mountain Dew while eating your chili cheese Fritos."<br />
<strong>Amy:</strong>   "..and are those Converse you're wearing?"<br />
<strong>Charles:</strong>  "Yeah, but they aren't Chuck Taylors, so it's not totally bad."</p>
    ]]></summary>
    <content type="html"><![CDATA[<p><strong>Amy:</strong>  "You're such a cliché, Charles."<br />
<strong>Sherry:</strong>  "Yeah!  There you are, with your Admiral Ackbar profile photo, sucking down your Mountain Dew while eating your chili cheese Fritos."<br />
<strong>Amy:</strong>   "..and are those Converse you're wearing?"<br />
<strong>Charles:</strong>  "Yeah, but they aren't Chuck Taylors, so it's not totally bad."</p>
    ]]></content>
  </entry>
  <entry>
    <title>personal eye</title>
    <link rel="alternate" type="text/html" href="http://domesticat.net/2008/01/personal-eye" />
    <id>http://domesticat.net/2008/01/personal-eye</id>
    <published>2008-01-23T00:24:06+00:00</published>
    <updated>2008-01-23T00:24:06+00:00</updated>
    <author>
      <name>domesticat</name>
    </author>
    <category term="choices" />
    <category term="conflict" />
    <category term="death" />
    <category term="friends" />
    <category term="work" />
    <summary type="html"><![CDATA[<p>We joke about people being married to their jobs, but the numbers in my own life tell quite a tale.  A typical workday sees me awake for 17 hours.  I spend nine of those with co-workers.  Since Jeff and I keep slightly different work schedules, I only see him for about five hours per weekday.<br />
The jokes become less comfortable when you realize that you're spending more hours per day with your co-workers than you do with the person you married.  Co-workers don't have the same commitment to permanence that spouses do; they are people you spend time with, but not people you share everything with.  I marvel at how few people find this strange or unusual.</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>We joke about people being married to their jobs, but the numbers in my own life tell quite a tale.  A typical workday sees me awake for 17 hours.  I spend nine of those with co-workers.  Since Jeff and I keep slightly different work schedules, I only see him for about five hours per weekday.</p>
<p>The jokes become less comfortable when you realize that you're spending more hours per day with your co-workers than you do with the person you married.  Co-workers don't have the same commitment to permanence that spouses do; they are people you spend time with, but not people you share everything with.  I marvel at how few people find this strange or unusual.</p>
<p>A co-worker of mine died this past week after an extended illness.  I did not know her as well as many of my co-workers did, but I was greatly saddened by her death.  I enjoyed her company, though our social circles did not overlap.  She was well-liked, and with reason.  She was both pragmatic and knowledgeable, and -- important for someone in my line of work -- embraced computers and technology to a level that was not often seen in the books-and-paper world of libraries.</p>
<p>We had warning, of course; the quiet step of co-workers passing news down the hall told us that she had been worsening fast, but no endpoint or timeline was given us.  I assumed days, not hours, but I was wrong.  Another quiet step, another knock on the door, later that afternoon passed the news to our department.</p>
<p>I ached to see my co-workers cry, those people that I spent more time with on a daily basis than my spouse, but whom I didn't feel I had permission to hug.  Later that afternoon, I was approached by other co-workers who asked, "Would you mind designing the memorial flyers?"</p>
<p>I did not cry then, not to the level of my co-workers, but the tears came when I slotted her photo into the layout.  The combination of personal distress and professional graphic design was too dichotomous for my brain to handle well, and it unsettled me greatly when each step of the design approval process brought fresh tears from my co-workers.  Someone had to approach the project with a professional, not a personal, eye, and evidently that someone needed to be me.</p>
<p>If you like the people you work with, the line between professional and personal can blur all too quickly.</p>
<p>I got word late last week that the funeral would be Monday, and harbored plans to attend the services between taking the last remaining visiting friends to the airport.  As the weekend went on, I realized that my plans were plausible but perhaps not well thought out; by attending the funeral I would miss out on the last few hours of visiting with two people who had flown from South Carolina and Arizona to stay with us.</p>
<p>On Sunday night, I made up my mind to skip the funeral.  I should have attended, but I also should have spent time with my houseguest-friends; given no good option, I chose to side with the living.  I thought about her as we had lunch and bought coffee and gradually talked faster, trying to fit in months' worth of conversations in the half-hour left before airport time.</p>
<p>I thought about how the professional and personal worlds collide, whether we want them to or not.  I put Jake and Scott on planes and thought of Helen, and wished them all well.  </p>
<p>All three mattered, but choices had to be made.</p>
    ]]></content>
  </entry>
  <entry>
    <title>Name: devil.  Location: details.</title>
    <link rel="alternate" type="text/html" href="http://domesticat.net/2007/11/name-devil-location-details" />
    <id>http://domesticat.net/2007/11/name-devil-location-details</id>
    <published>2007-11-17T20:07:05+00:00</published>
    <updated>2007-11-17T20:07:25+00:00</updated>
    <author>
      <name>domesticat</name>
    </author>
    <category term="books" />
    <category term="cats" />
    <category term="creativity" />
    <category term="reading" />
    <category term="work" />
    <summary type="html"><![CDATA[<p>I lay on the bed this afternoon, drowsy with sunshine and tea and salacious novel, and trawled fingers through Edmund's orange fur.  As my hand crept over and around, to reach the white fur on his belly, the purring changed from lazy to nearly explosive, as if to say, <em>oh yes, pet me right there...</em></p>
    ]]></summary>
    <content type="html"><![CDATA[<p>I lay on the bed this afternoon, drowsy with sunshine and tea and salacious novel, and trawled fingers through Edmund's orange fur.  As my hand crept over and around, to reach the white fur on his belly, the purring changed from lazy to nearly explosive, as if to say, <em>oh yes, pet me right there...</em></p>
<p>He's missed me, the little brat.  Tenzing too.  I've been a null entity in my life for the past two weeks as I worked on bringing The Print Project&trade; to completion.  I came home Thursday night with a sense of jubilance that was tempered by a well-chilled bottle of Mirror Pond Pale Ale and a desperate need to sleep.  I slept nearly ten hours that night and nearly twelve last night.  I feel mostly human again.</p>
<p>Frantic creativity, for me, comes with a hefty price tag.  I do marvel at how I react to it, as I'm not sure if my reaction is typical.  It is not physically tiring work, but it's mentally draining.  I measure the length of my days by the lights in the room I work in; if I'm the person who first turns them on at the beginning of the day and also turns them out when I leave, I know it's been a long day.</p>
<p>(Misty, I have meant to ask you for ages if you react similarly to design work.)</p>
<p>I think my co-workers think I'm a little crazy.  'Touched' is the phrase I heard growing up, as in, <em>She's a little touched in the head, isn't she?</em>  I'm something of a favored and eccentric pet in the office, someone whose foibles are odd, yet amusing.  My creative output can be reasonably estimated by a graph containing hours of headphone time and total cups of tea per day.  </p>
<p>It also turns out that I'm slightly superstitious about projects.  I react strangely when told an unfinished project is good.  Perhaps I'm afraid of jinxing the final piece of the puzzle.  However, once the project is done, and I can see all the parts, I'm comfortable with being told it's good work.</p>
<p>But, regardless, it is done.  I had a slight whiff of disappointment when I handed a copy of the finished project to Jeff this afternoon, so he could see what had stolen his wife away for two weeks.  I stifled the sense of discouragement that said, "But it's only three pieces of paper.  How did this eat 116 hours of my life?"  But that's easily answered; see the title of this entry.  </p>
<p>116 hours goes away quickly when you add it all together:  Photography.  Initial design and layout.  Throwing out most of the initial design and layout when the mailing's layout had to be changed radically due to cost issues.  Reshoots.  Photo cleanup.  Copywriting (in this case turning raw statistics into readable, interesting chunks of information).  Layout.  More layout.  Proofing.  Discussing changes with printer and the commissioner of the project.  Readying for press, and sending it away.</p>
<p>116 hours, mostly over the course of two weeks, one of which was shortened due to a holiday.</p>
<p>No wonder the cats have missed me.  I woke up this morning to soft, querulous purring from Tenzing:  <em>snuggle time plz?</em>  Since words don't work well with cats, I rubbed his ears, giving the Universal Cat Signal Of Human Available For Petting.  The next thing I knew, he was busily twirling himself into the perfect position to collapse in the crook of my arm, chin draped over my elbow, paws flexing as he uttered a dramatic, exhausted wheeze (he is such the drama queen) and settled into a nap.  I could feel the soft vibrations against my arm as he purred himself to sleep.  I hadn't made time for him, and he'd missed me.</p>
<p>Today is a recharge day.  Tea, sunshine, kitties.  The best moment of all?  Realizing that I'd guessed wrong on some of the details (Huntsville?  Married?  House instead of apartment?) but that when examined from a distance, I've become exactly the adult I thought I would be.</p>
<p>This won't be the last time I need a recovery day like this one.  The nature of my job guarantees there will be others, and sooner rather than later, but it's comforting to realize that this time, I didn't just do a decent job, I did a jaw-dropping kick-ass one.  Each time I do so, I grow a little more confident that I can do it again.</p>
<p>But for now?  Edmund's belly needs rubbing, and I've got a little paperback that's whispering my name.</p>
    ]]></content>
  </entry>
  <entry>
    <title>zeroed down</title>
    <link rel="alternate" type="text/html" href="http://domesticat.net/2007/10/zeroed-down" />
    <id>http://domesticat.net/2007/10/zeroed-down</id>
    <published>2007-10-30T00:21:41+00:00</published>
    <updated>2007-10-30T00:23:00+00:00</updated>
    <author>
      <name>domesticat</name>
    </author>
    <category term="coding" />
    <category term="work" />
    <summary type="html"><![CDATA[<p>Today was the rarest of programming days.  My headphones were on by eight a.m., and while the code didn't flow, the ideas did; when I next looked up, it was after one p.m.  I zeroed down on the section of code I had my suspicions about, and started testing, line by line.  The book clubs problem eventually presented itself as a three-headed beast.</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>Today was the rarest of programming days.  My headphones were on by eight a.m., and while the code didn't flow, the ideas did; when I next looked up, it was after one p.m.  I zeroed down on the section of code I had my suspicions about, and started testing, line by line.  The book clubs problem eventually presented itself as a three-headed beast.</p>
<p>The first problem was the one I expected; having seen a similar array problem on another page, I knew what to look for, and it was easier to isolate this time.  Once I corrected the inconsistency, information began flowing.  Just not all of it that I needed.</p>
<p>The second problem I had also seen before, but I still don't have an answer for it.  There seems to be a problem -- likely, a collision -- between the Thyme calendar and drupal whenever the $_cur_cal variable has been brought into play.  When methods involving the $_cur_cal variable are brought into play in standalone pages, they work beautifully, but when used in a drupal page, the code dies silently every time.  I don't understand why, but in both instances, I have been able to create a workaround by building a smart little query to the database that brings me all the results I might need.</p>
<p>I might not know how to lock the trapdoor so I don't fall into it, but I have figured out how to walk around it.</p>
<p>The third problem is a .htaccess problem.  It should have been the simplest of the three, but my ineptness with regular expressions has caught me off guard again.  Every time I encounter a problem that can be solved by regular expressions, I learn a bit more about how they work, but I am a slow and fitful learner.  They are alchemy and pixie dust, and they don't always work the way I need them to work.  </p>
<p>The page in its current incarnation contains links like this:</p>
<p><code>/bookclubs/?y=2007&amp;m=10</code></p>
<p>Click on the link and the page continually reloads itself, and provides year and month information to build queries from (end result:  shows book club information from that year/month combination).  The problem is that I can't do this directly in drupal, and it requires some rather obfuscated workarounds.  The logical option would be to build a new URL like this:</p>
<p><code>/bookclubs/200710</code></p>
<p>The problem is that you can't do that through drupal alone.  Drupal's URL aliasing system doesn't let you use wildcards, and I refuse to add in a new alias for every month and year combination -- that's a very wrong-headed approach.  Since you can't say "if it starts with /bookclubs/ followed by a six-digit numeric string, do this..." you have to resort to a regular expression in the .htaccess file.  I have to take all of the requests that match that pattern and route them to a single page, something like</p>
<p><code>/bookclubs/showmonth</code></p>
<p>The end user never sees that address -- all they see is what they typed.  On that page, I then use $_SERVER['REQUEST_URI'] to pull out that six-digit number they typed, squish* it into the format I need, and show the books the book clubs read for that month/year combination.</p>
<p>Once that is solved, the book clubs problem-in-three-parts is solved.  I can build the end-user's pretty links, insert them into the menu system, and move on to the next architecture problem.  I've promised myself that I'll save the look-and-feel questions for last, and that I'll sit on my hands and refuse to tinker with the look until it's time.  Bones before skin.  Structure before surface.  Build it correctly from the start, and the rest is just window dressing.</p>
<p>The frustrating thing?  I may not be able to finish this tomorrow, or anytime this week.  If a certain vendor comes back with a usable quote on a print project, I have to drop everything and work feverishly on that project until it can go to press.  The web project, although it is the overarching issue, has to let the print project take precedence.</p>
<p>Assuming I get the .htaccess issue sussed* out, that puts me one major step closer to full beta.  (Fingers crossed that the potential solution Adam sent to me via SMS fixes the logjam.)  I've got just under two months to my totally arbitrary and self-imposed deadline.</p>
<p>We'll see.</p>
<p><em>* Technical terms.</em></p>
    ]]></content>
  </entry>
  <entry>
    <title>proving ground</title>
    <link rel="alternate" type="text/html" href="http://domesticat.net/2007/10/proving-ground" />
    <id>http://domesticat.net/2007/10/proving-ground</id>
    <published>2007-10-28T14:19:19+00:00</published>
    <updated>2007-10-28T14:19:19+00:00</updated>
    <author>
      <name>domesticat</name>
    </author>
    <category term="coding" />
    <category term="design" />
    <category term="work" />
    <summary type="html"><![CDATA[<p>The tally is now at fourteen months, and verging on fifteen.<br />
I'm amazed anyone still reads this site; it has to be obvious that my design time and energy has been diverted elsewhere for that period of time.  It used to bother me.  I still apologize for it, but I've stopped giving estimates on when I might finally reach the finish line and be 'back.'  I don't know.  I stopped knowing about six months ago.</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>The tally is now at fourteen months, and verging on fifteen.</p>
<p>I'm amazed anyone still reads this site; it has to be obvious that my design time and energy has been diverted elsewhere for that period of time.  It used to bother me.  I still apologize for it, but I've stopped giving estimates on when I might finally reach the finish line and be 'back.'  I don't know.  I stopped knowing about six months ago.</p>
<p>From my very first day at The Job, the understanding has been that I would 'fix' the website.  The depth and complexity of that task did not become clear to me until a few months in, when I realized that I was dealing with many small scripts scattered all over the site, undocumented, uncommented.</p>
<p>I did the only thing I knew how to do:  I buckled down.  My first priority was assessment.  What was wrong?  Why was it wrong?  I went from directory to directory, cataloguing, making notes, writing down questions for later.  Through that assessment, it became clear that my first priority needed to be a calendar conversion; the homebrew calendar we were using at that time had no comments, no documentation, and had major flaws and limitations.  </p>
<p>Fast-forward a couple of months.  I moved forward - finally getting a new calendar system purchased, adding in the old data, then adding new data in tandem with the old calendar, writing functions to do the extra display work the homebrew calendar did, then finally turning off the old calendar.  I breathed a little easier.  The day I was finally able to do repeating events without keying in every instance of the event was a joyous day.</p>
<p>Since then, progress has been glacial.  Most people can't even see it, and that's been the disheartening thing.  I've been re-coding the scripts one at a time into a language I'm more familiar with, and more importantly documenting and commenting them as I go.  I now understand about 90% of what the scripts on the website do.  But the end goal?  Transparency.  End users <em>shouldn't</em> have seen a change, and neither should my co-workers.</p>
<p>Stage three was a content management system.  I identified drupal as the way to go for this site about six months ago, and my coding work has been aimed toward making every page on the site insertable into drupal.  I'm most of the way there.  I have two major subsections of the site to go before everything's included, and we can consider moving the site live.</p>
<p>I've been solo on this project for fifteen months.  It's left me feeling isolated both at work and at home.  I am the only programmer at The Workplace, and it's been made clear to me that they love me, but I bewilder them.  I'm a sausage-maker.  What I do scares them, makes them sketch warding signs and think of alchemists -- but they want that end result.</p>
<p>I want to be done.  I remember real life.  I want to stop asking my co-workers for patience, to just show them what I've been working on, to find answers to these last two major problems...  This project is very much my proving ground.  If I do it to <em>my</em> satisfaction, there will be no doubts as to why I was hired.</p>
<p>I've held fast to something a co-worker found out for me.  We've been looking at a similar website overhaul/revision, and through family contacts, we were able to find out details on what it took to achieve their website overhaul.  It took ten full-time programmer-designers working on only that project for a year.</p>
<p>I am solo, am doing this in conjunction with print design, and have been at this for fourteen months.</p>
<p>So, Santa?  Here's what I want for Christmas.  I want the final two big questions solved.  I want to fix the book clubs problem, and I want to find the answer to the training center problem.  Give me those, and I can wrap up the rest.  Let me hand them a beta before I get on the plane on December 27th.</p>
<p>I want my life back, but right now I think it is more important to myself (and a lesser degree my co-workers) that I prove myself.  The people working with me in my department know it has taken endless cups of tea and headphone hours to get where I am now (both appearing in tandem are a sign of a major code problem) but I want so very much to show the rest of my co-workers that <em>this</em> is why I was hired, that <em>this</em> is what I'm capable of doing if I'm allowed time and space to do my job.</p>
<p>December 27th - is that so much to ask?</p>
    ]]></content>
  </entry>
</feed>
