Geekamama


Leave a comment

Road trip or bust!

Who on earth would be crazy enough to plan a two-week road trip–14 consecutive days–with a just-turned-2 toddler?

Oh, right. That would be me.

In my defense, parts of the trip had been in the works well before there was a Kiddo to complicate the plans. But after years of postponing and rescheduling, I finally said, Enough. It’s happening. We’re going to make it work. And amazingly, it not only worked, but turned out to be one of the best vacations we’ve taken as a family.

Our itinerary took us first to Glacier National Park, in the northwest corner of Montana. We then headed south to my hometown, Bozeman, and while there, split our time between the annual Sweet Pea Festival and my 20-year high school reunion.  The following week, my parents, sisters, and I (plus husbands and kids, of course) visited Yellowstone National Park, a couple hours south of Bozeman.

So what inspired this grand tour? Nostalgia, initially. When I was a kid, there were two things my family did on a regular basis: visit Yellowstone at least once a year, and spend Sweet Pea weekend hanging out at the park where the festival was always held. In fall 2008, I was driving on a road that reminded me of Yellowstone, and got the idea that we should take another family trip to the park and revisit some of our favorite sights. And why not schedule it adjoining Sweet Pea, and check off two things at once?

The family was on board; we set our sights on summer 2009 so that we’d have time to schedule time off from work. And then my sister and I both got pregnant about three months apart. Making that trip with months-old babies wouldn’t work out well, we all agreed. In spring 2009, we postponed the trip to the following year.

But a few months later, before I’d gotten around to booking lodging in the park, my husband’s family stepped in with their own plans for an big family August 2010 trip. They’d already picked dates and made hotel reservations when I learned about it. Our little family could have made both trips happen, but it would have meant taking more than three weeks off work, and taking a cross-country flight right after completing a two-day drive back from Montana–and all that with a one-year-old. I was informed that our Yellowstone trip would have to be postponed yet another year.

I’ll confess that I didn’t concede this as gracefully as I could have. I’d been making these plans for a year and had postponed it once already. Now I had to wait not one but two more years? Even now I can still feel some of the ire that was bubbling back then. I reluctantly agreed, but defiantly hammered my stake into the ground: August 2011 was MINE.

Whatever, people said. After all, that was almost two years away. Who knows (and who cares) what we’d be doing then?

I knew. I cared. I started making plans. At first, it was just going to be Sweet Pea and Yellowstone, in some order. Then I remembered that my husband and I had talked about visiting Glacier Park, and that it could be doable even with a young kid. I decided we could fit a Glacier visit into whichever week we weren’t going to Yellowstone. Finally, after that was settled, my high school classmates decided to follow local tradition and schedule our reunion to coincide with Sweet Pea weekend.

It was a lot to cram into two weeks. It was especially a lot considering that by the time the vacation happened, we’d have a two-year-old who needed regular snacks and naps and attention. We were worried he’d protest being cooped up in the car for hours of driving, and that he wouldn’t sleep well in unfamiliar hotel rooms. We knew his little legs didn’t have the stamina to keep up with us on hikes and geyser tours, so we’d need to make accommodations.

However, I’m an organizer at heart, and I was already in the mindset that we were going to make this trip happen, come hell or high snowpack. We found some great tools and techniques that helped make things go more smoothly (more to come on these), we built in downtime for naps, and we kept an open mind toward adjusting the schedule on the fly if needed.

And in the end, it was all worth it. We saw amazing sights that we’d never seen before, revisited others that I’d grown up with, brushed elbows with mountain goats, and spent rare time with family and friends. Would I change anything? Oh sure, looking back there were a few tweaks that could have been made, but nothing major. Would I do it again? Unquestionably.


2 Comments

Road Trip, by the numbers

Days traveling: 14
Miles traveled: About 2,200
States visited: 4
National Parks visited: 2

Nights sleeping in hotel rooms: 8
Days traveling from one point to another: 6
Mountain passes crossed: 8 (Snoqualmie, Fourth of July, Lookout, Logan, Bozeman, Craig, Dunraven, Homestake)
Continental Divide crossings: 13 (including 2 on foot, as well as one crossing of the Northern Divide)
Highest point of elevation visited: 8,878 feet

Miles hiked in Glacier National Park: About 5.5
Geyser basins visited in Yellowstone National Park: 7
Waterfalls visited in both parks: 3, plus a handful seen from the car window

High school classmates revisited: About 70!
Facebook friends added: 10
Tater pigs eaten: 2
Miles walked early in the morning pushing a stroller: 3.1
Parades viewed: 1

High temperature on departure day: 71 F
Average high temp in Whitefish and Glacier Park on days 2-5: 86 F
Average high temp in Bozeman on days 6-9 and 13: 82 F
Average high temp at Old Faithful on days 10-13: 73 F
High temperature on return day: 70 F

Longest day of driving: Technically Day 14 (Missoula to Seattle) but Day 5 (Whitefish to Bozeman by way of Logan Pass) certainly felt like it.
Cows counted: Uncountable
Toddler meltdowns while driving: Only 2!

Suntan acquired: Yes (but not as much as the guys)
Freckles acquired: Many
Spectacular vistas viewed: Definitely
High school reunion survived: Yep!
Blog posts likely to come out of this trip: At least 3

Overall assessment: A++, would trip again


3 Comments

Geekspeak leaks

My cousin and I had a brief conversation on Twitter the other day (although really, what other kind of conversation can you have in 140 characters or less?) about engineering terms that are considered jargon even when they’re convenient for describing less-technical situations. One term in particular, actually, but I’ll come back to that; it’s an interesting case. The conversation got me thinking about other places where tech-y terms have seeped into my day-to-day vernacular.

Bug resolution jokes aren’t uncommon among people who find them or fix them for a living. When someone logs a software bug and the developer or designer chooses not to fix it, there are a couple possible reasons. Maybe they can’t reproduce the bug (“Not Repro”). Maybe it’s not a bug in their own software, but rather a deficiency in the underlying operating system (“External”). Maybe it really is a bug, but fixing it wouldn’t be cost-effective or would destabilize the rest of the product too much (“Won’t Fix”). Or maybe what the tester thinks is a bug is what the designer thinks is how it’s supposed to work (“By Design”).  While they’re primarily used in technical contexts, they transfer to real life without too much trouble. Someone describes a complex problem that is less likely to happen than a lightning strike on a sunny day, and we’ll respond “Yeah… Won’t Fix, buddy,” with a chuckle.

One that’s become pretty common outside the technical field is “bandwidth.”  In the context of electronic communications, one meaning is the amount of data that can be passed along a communications channel in a specific period of time. Your internet provider may advertise that they offer a high-bandwidth connection, for example. Among my co-workers, I’ve also heard it used referring to their personal ability to take on tasks: “Let’s give that one to Mikey, he’s got the bandwidth right now.”

The term my cousin and I were discussing was “Namespace collision.” It’s not an intuitive name to someone who doesn’t write software code on a regular basis, and yet it describes a situation that just about everybody’s been in at some point. In a nutshell, a namespace is a context in which a particular word or phrase has a specific meaning that might be different outside that context. A namespace collision, then, is when that term is used and it’s initially ambiguous which meaning you’re referring to. This sort of thing happens all the time in real life, as illustrated by a conversation my husband and I had the other day:

Husband: “…and Mike brought waffles and the toaster to HQ on Sunday morning.”
Me, thinking: <Mike? Mike J.? What toaster? Why would he have–OHHH, does he mean Mike H. instead of Mike J.? Mike H. has a toaster that we’ve talked about recently, well, not really HIS toaster, which is why we’ve talked about it…>

In programming, occasionally you’ll have two functions with the same name, say “getSpeed.” If the compiler can’t figure out whether you mean the one that goes with the radar detector software or the one from the auto aerodynamics software, it will give you an error. Every programming language provides a way to designate which one you mean. In conversation, we resort to qualifiers like initials, or possessives, or rambling descriptions like “My co-worker Steve, you know, the one who flies model planes? Who has an office two doors down from me? Yeah, the blond one, that one.”

Everyone’s been there, but we (by which I mean my cousin and I, not the more general we-the-people; another unclear reference) couldn’t think of a general non-technical term that rolled off the tongue as easily as “namespace collision” does for us. “Ambiguity” gets close, but is itself ambiguous: does it mean simply an unclear qualification, or does it refer to a situation where there is no clear answer?

I think “no clear answer” is exactly what we’ve got here.

But in truth, sometimes it’s fun to have inside jokes making light of the challenges we get paid to deal with. I’m certain that engineers aren’t the only ones who make those kind of references. They’re just the ones that I’m likely to catch when they’re thrown.


1 Comment

Uncentered

I’ve been busy with my new job, and haven’t had much time to write here lately. And in the meantime, my little guy has been up to so much. Over the past several weeks, he has continually amazed me with the way in which he learns things, and how quickly he picks up little tricks. He speaks in sentences and phrases now, repeats back what we’ve told him, sings Twinkle Twinkle Little Star and counts past twenty with a look-what-I-can-do lilt in his voice.

He’s growing up so fast, and last weekend really brought it home. My husband and I were involved with an all-day puzzle event that we needed to be able to focus on, so we had to find an alternate plan for Kiddo. Our sitter that day was the son of a couple friends of ours; he’s taken care of Kiddo before at their house, with occasional oversight from his mom, and Kiddo has usually enjoyed his time there, once he gets past being upset with us for leaving him behind.

I was expecting the usual tears and clinging when I dropped him off, but this time was different. As I stood in the driveway chatting with my friend, her daughter came outside to talk to Kiddo, and then led him inside by the hand to find a toy. He didn’t even look back.

I was a little taken aback. When I realized what had just happened, and Kiddo didn’t immediately come running back out. I turned to my friend. “I feel bad about leaving without saying goodbye, but it might be easier on him if I just go,” I said uncertainly. She agreed, and I hopped back in my car.

Usually as I drive away from a drop-off, I feel a tiny bit of regret. How could I knowingly upset him, even knowing that he’d be fine again as soon as I was out of sight? Last weekend I felt a different kind of regret. As much as I’d looked forward to the day when I could walk away without the tears and drama, I suddenly missed it a little bit. It was no longer a big deal that Mom was leaving him behind, and my ego wasn’t sure how to handle that.

Objectively I know that this means we’ve done something right. We’ve helped him build his independence and confidence that it’s OK for Mom and Dad to leave him with someone else for a while. He knows we’ll come back and we still love him. Emotionally, though, it was a little bit of a hit to see him casually go off with someone else, as though he was saying “Oh, you’re leaving? Whatever, see you later.”

I’m proud of the big boy he’s becoming. Outwardly I’ll give him all the support he needs to grow into a confident, independent adult. And if I get a lump in my throat now and again missing the little baby whose universe revolved around me, well, I guess that’s just part of growing as a parent.


4 Comments

Words mean things, I think

Kiddo’s turned into quite the chatterbox recently. One article I read a while back about speech milestones said that right around 2, they’ll start talking a lot and you’ll be convinced they’re speaking another language. I laughed at the time. Now I see what they meant.

He tells us his observations of everything: Mom’s coat is green, his own coat is blue and yellow, Dad’s car goes vroom vroom. He can usually articulate his needs and wants: more meat please, water please, Dad read book, light on. He’s started offering his opinions too: cheese mmm, no Mom no sing!

All of these, of course, in his own dialect of toddler-ese. I’m reasonably adept at translating it, my husband nearly as much, and I have to assume his daycare teachers are too. I think he meets the developmental milestone guideline that says by this age, strangers can understand about half of what Kiddo says. But even I have trouble parsing some of the garbled words and phrases. Our smattering of sign language helped for a while but we haven’t really kept it up, other than the basics.

When he says something that we can understand, we usually repeat it back to him so that he can hear (and hopefully pick up) the correct pronounciation. In the car this morning Kiddo said “Gar doh o-peh” and I said yep, I’m going to open the garage door. As we started down the driveway he cheerfully exclaimed “Doin don hih!” and I confirmed that’s right, we’re going down the hill! I can’t always do this–sometimes I’m occupied with things like driving or cooking, other times I simply can’t make it out.

This morning I wondered whether I was overdoing it. Imagine how you’d feel if someone was correcting ninety percent of what you said. Some might find it helpful, but I know if it were me, I might start to feel like I couldn’t do any darn thing right, and might even lose the confidence to keep trying at all. In my attempts to build up the correct use of language, am I actually tearing him down? Am I modeling, or just invalidating?

Then I said to myself, Self, you’ve been spending too much time in online parenting forums. Stop being a dork.


3 Comments

Back to geekland

On the last workday of April, I left my previous job. On the last workday of May, I was offered a new one. I’ve accepted it, and will start work next Monday, once again testing software, but at a different company than before.  I’m looking forward to getting back into the work world. Our house is in a wooded neighborhood a dozen miles from the nearest town, and can feel very isolated at times. On the other hand, there are a couple of things I think I’ll miss from this past month and a half.

Above all, I’ll miss being able to stay on top of the clutter. Before, when I was working, our evening routine went something like this: come home, make dinner, give Kiddo a bath if he needed it, put him to bed, and then collapse in front of the TV. It was hard to do a lot of cleaning up right after Kiddo’s gone to bed because his bedroom is close to the kitchen and living room, so loud noises like vacuuming or clattering pots being put away would keep him from falling asleep. Even harder was putting down the remote to do the chores once we’d been sucked into TV watching for the night. While at home these past weeks I’ve done what I could to get the house to a cleaner “base level” in the hopes it would make daily tidying less of a burden, but I don’t know how long we’ll be able to maintain it.

I’ll also miss having time to cook interesting dinners. We pick Kiddo up from daycare around 6:15 p.m. and our drive home from there usually takes half an hour or more. This means anything beyond quick-prep dinners pushed dinnertime (and consequently, bedtime) even later. It didn’t help that we often didn’t decide on that night’s dinner until right before leaving work. Whoever wasn’t on pickup duty was in charge of arranging for dinner, whether that meant shopping or just hitting the local Panera. But that also meant a delay in getting home and getting it started.

I’m a little bummed that I didn’t get to all the projects I wanted to do. I’ve found that I’m something of a structured procrastinator, so I have gotten a fair amount of other work done, but the basement is still a mess, the recipes never got organized, the software project I’d meant to work on with a friend hasn’t gotten further than the design stage. Writing a non-prioritized weekly to-do list helped a lot; the weekly deadline let me push things back a day without feeling like I’d failed to get everything done, and I could rearrange things as needed–for example, I couldn’t sweep the deck very well in the pouring rain, so that had to wait for a good-weather day.

So, I’ve been thinking a bit about how to keep some of my at-home work to continue into the summer and beyond. Planning meals and shopping on the weekends might save us a little time in the evenings, and perhaps we could do some prep for the next night’s dinner after the boy has gone to bed. Chopping onions isn’t as noisy as washing dishes, after all. We might also be able to streamline our getting-out-of-the-house routine in the morning, in the hopes that leaving for work earlier means coming home earlier as well.

Could we do some of the noisy chores like vacuuming right after getting home from work? Maybe, if Kiddo were a little older. Right now he loves being underfoot while we’re cooking, which often means whoever’s not cooking is on distraction detail. In the past, I’ve asked my husband to take care of the vacuuming before he left for work (he generally went in later than we did) but that would cut into his worktime, meaning he had to either stay later at the office, or bring work home. Maybe it’s time to dust off and empty out that Roomba — or just get a quieter vacuum cleaner.

Having the weekly list in a visible place could also be helpful. I’ve found that when I have a visual reminder of what needs to be done, it’s a little easier to find the time to do small chores, and I can budget time for big ones. And it will help my husband as well, who has reminded me countless times that his psychic powers are very weak. This way we’ll be in sync about what needs to get done that week.

I don’t know about those projects, though. The obvious time to do them would be on weekends, but during the summer we rarely have a weekend free. Perhaps they’ll just have to wait until this fall, when we might have to find a new way to fill Sunday afternoons.


1 Comment

Making memories

Last Sunday, after spending most of the afternoon at Pike Place Market, we stopped at Marymoor Park on the way home. Pike Place Market is nifty for taller people, but not so exciting when you’re strapped into a stroller. Kiddo had been very patient though, and he deserved some fun time for himself.

The park was the emptiest I’ve ever seen it. The playground itself was deserted. Granted, it was a holiday weekend, it was close to dinner time, and there were ominous-looking rain clouds not far away. But none of that mattered to our boy. He was thrilled that he could play on all the slides and ride on the little rocking tractor to his heart’s content, without needing to take turns or watch out for bigger kids. He’d pause at the top of a slide and sign “More?” and we would tell him, of course you can slide some more! We let him lead, and just followed him from slide to rocker to bigger slide to swing, letting him choose what he wanted to do next.

When it was time to leave we borrowed a trick and pointed to the small berm surrounding the concert stage, about halfway between the playground and the parking lot.  “Look at that hill! Want to run up the hill?” I asked Kiddo, and of course he did.  Off he ran, glee bubbling out of him, with all the speed his little not-quite-two-year-old legs could produce.

As we followed, I asked my husband, “Do you remember anything from when you were two?”

“No,” he said.

“Neither do I,” I replied.

After some thought, he was able to remember a big event that happened shortly before his brother was born, which would have been a couple months before my husband’s second birthday. And I remember the house my family lived in, and meeting another child who turned out to be one of my longest friends. But neither of us could remember much beyond that of those early years. I’m certain that we had afternoons like this one, where there was so much joy in getting to do whatever he wanted, for a little while. We must have had those moments of awe, discovering the secrets of the world that would become everyday facts just a few years later. I’m sure we had many, many moments of delight in learning and repeating new words and phrases, or tasting fresh raspberries for the first time. But memories laid down at this age often don’t stick around into adulthood; it’s not until children develop the ability to put events in chronological order that long-term memories start forming, and most children don’t develop that ability until around age 3 or 4.

In a way, it makes sense. A toddler’s brain is still developing, soaking up all kinds of details and bits of trivia. Mom’s shoes go in the closet; Dad’s glasses go on his face. But the part of their brain that controls emotions (and emotional outbursts) is still very immature. Or to put it more simply: it’s hard being a toddler! Frustrations abound because you don’t understand why you can’t do something, because your limited language skills make it hard to explain what you want, or simply because you’re overwhelmed and stressed dealing with the influx of new data, and you don’t have the mental maturity to cope with it. Who would want to carry the memories of those chaotic times around for the rest of their life? Perhaps the delay in developing long-term memory is a blessing in disguise.

But as the memories of the difficult times fade, they take with them most of the memories of the joyful times too. I saw Kiddo beaming with delight that afternoon and got a lump in my throat thinking that he probably won’t remember these moments. Pictures and video capture the physical activities and the words that were spoken, but his feelings and emotions can only be reconstructed, not retained.

I didn’t take pictures on Sunday afternoon. I wanted to take in the full experience of the fun we were having, of him playing and us watching him play. The little boy grown big may not remember this one afternoon out of so many others–but his father and I will.


Leave a comment

Guest appearance!

I’m guest blogging today at Tales of an Unlikely Mother.  Darlena asked me to describe what it’s been like for me this past month, changing from working a nine-to-five* job to staying home all day.  I’ve gotta admit, it wasn’t entirely what I expected!

* OK, we all know it was rarely a nine-to-five job. Software engineers in the office at nine a.m.? Leaving the office at five? Unheard of! 😉


8 Comments

I’m bringing paperback

Kindles, Nooks, iPads, even smartphones… it feels like everywhere I look, someone’s got some kind of e-reader. Heck, even my mom got one for Christmas last year! Being the voracious reader that I am, you’d think I would be first in line for the latest device. But this is one geek trend I’m skipping, for now. I’ll take my reading the old-fashioned way.

I grew up devouring books. Most times when I got suspiciously quiet, it wasn’t because I was up to mischief, but rather because I’d gotten lost in a book. And I wouldn’t just read them once–if I liked a book (and I rarely met one I didn’t) I was happy to return to it many times. Even as an adult I get as much pleasure reading a book for the second or third time as I did the first time through. Some people watch their favorite movies over and over, spouting memorable quotes. Why should it be strange that I do this with my favorite books?

So, it seems like a no-brainer.  Electronic readers have all kinds of advantages over traditional books. They’re kinder to the environment than printed editions, they’re easier to carry when you want to take the whole library along, and I could read late into the night without turning on the bedside light. Anti-glare screens make it convenient to read outside, and advances in battery usage make it possible to go for weeks without needing a charge. But I’m still not sold. I’ve got a more important, less personal reason to pass for now: I want my son to love reading as much as I do.

Kiddo is still too young to tell an iPod from a smartphone, and the only difference to him between those two and our laptops is their size. In this little boy’s eyes, all of them serve the same purpose: to prevent Mom and Dad from paying Kiddo his rightful share of attention. If I pull out my phone to take a quick peek at my email, he’ll grab my arm and say “No, mom!”  He’s even reacted that way occasionally to other electronics like our digital camera. So, as handy as an e-reader might be for me, he’s not going to see it as a book. He’s going to see it as one more distraction.

Children copy the behaviors modeled by their parents. I remember playing in the backyard as a child while my own mother sat nearby with a book in hand. To show Kiddo how enjoyable reading can be, we have to demonstrate it with items he recognizes as books, not gadgets. Frankly, it’s not that much of a burden for me. I like reading traditional-format paperbacks.  They’re a good fit for my small hands. I like the feel and sound of fanning a new book’s pages; I love flipping to a random place in an old read and thinking, “Oh yeah, I remember this part!” and diving in.

And there are other benefits to analog versions. It’s easy to purchase a new one without needing any special software installed. I don’t worry about breaking them if I drop them, and I can keep reading on the airplane during takeoff and landing, while other electronic devices have to be turned off and stowed. Sure, they both get ruined if they fall in the bathtub, but the replacement cost of a mass-market paperback is considerably lower.

I have no doubt that a couple of years down the road, I’ll be ready for the latest Kindle or its kin. But for now, I’ll take my dead-tree versions, with the hope that I’m planting a seed for the future.


4 Comments

Little man with a plan

We’ve noticed a change in Kiddo the past week or two.  He’s gotten more assertive about letting us know what he wants to do–and especially what he wants us to do.

For as long as he’s been able to say “No” (and boy, that feels like forever) Kiddo has had no qualms about telling us that he doesn’t want us to do something, whether it’s checking email on our cell phones or attempting to get him dressed. But he generally didn’t take the initiative to tell us what he actually did want to do. Recently, though, he’s figured out that he can show us through actions what he’s got in mind.

In the morning, when either I or my husband is trying to sleep in, Kiddo will come up and grab an arm, trying to pull us out of bed. If I’m at the kitchen table and he throws his new orange ball over the baby gate and down the stairs, he’ll lead me by the hand to where the problem is. He doesn’t wait for us to serve him anymore at mealtimes, if he can help it. If there’s food he wants and it’s within reach, he’ll simply help himself.

This is exciting to me because it tells me that he’s learned he can influence other people’s actions.  He’s long past the stage where he figured out that Mom and Dad are separate people who sometimes have different opinions than he does (for example, whether he should go to bed or not). He has frequently demonstrated that he knows he’s allowed to express his opinion. But suddenly it seems like he’s realized that he doesn’t have to wait for other people to make a decision–that he himself can decide what we should do next.

Obviously, as parents we’re going to overrule him at times, but right now I’m getting such a kick out of seeing how he asserts himself. He’s so confident in his belief that of course Mom or Dad will do what he wants, if he can just show them what it is he wants to do.

My favorite example of this so far happened a few days ago. We’ve got a regular group that gets together weekly to watch the latest episode of Survivor. We’d all taken our shoes off when we arrived at the hosts’ house, and piled them just inside the front door before heading to the viewing area at the back of the house. About 15 minutes before the end of the show, Kiddo plopped down in my lap and handed me his shoes.  I put them on him–after all, sometimes he just likes having shoes on.  He disappeared, then reappeared a few minutes later carrying my husband’s shoes.  Next he ferried mine over as well.  “Mom shoes!” he announced. When he dragged our coats down the hall to us, we finally realized what he’d been trying to tell us: it was time to go home.  Never mind that we were literally about to find out who was getting voted off! When a not-quite-two-year-old has his mind made up, there’s no such thing as a rational appeal.

On our way to the car, we realized something else as well. Every weekday morning, as we get ready to head off to work and daycare, putting on coats and shoes is the first step to heading out the door. That night, when Kiddo decided it was time to go, he didn’t whine or throw a tantrum. He simply repeated the routine he knew from home and expected it would have the same result. From his point of view, his actions were totally logical. They may not be rational quite yet, but in their own way, toddlers actually can make sense.