On My Fifth Blogiversary

I now have five years of blogging experience, and even with all that behind me, I find this post difficult to write. No, I’m not killing the blog, even though I haven’t written here in six months. You can still expect posts from me here, when I have something to say that doesn’t fit on Ravelry. I may not post very often, but I do plan to continue posting occasionally.

When I was deciding what to do with the blog, I found it helpful to think about why I’d started down this path in the first place. After all, what did I have to offer the knitting community? I don’t teach knitting, so I have no schedule to post. I haven’t published patterns, so I have nothing to offer for sale or giveaway. I don’t have a lot of time to compose beautiful photographs, so it’s not a work of art to look at. No, it’s just color commentary on my knitting projects, and sometimes on life in general.

So, why did I want to start a blog? Well, I’d found that blogs had helpful to me when I wanted to look up a particular project, or a new technique, or just be entertained by someone else’s knitting adventures. I felt like I could repay some of what I’d gotten out of the knitterverse by adding my own voice. And speaking of voice, the blog has been a unique place for it.

I have other places where my online persona resides. Facebook keeps the Wife and Mom self. Twitter has my pithy, Knitter self. Instagram keeps my photos from the knitter and non-knitter aspects of my self. Ravelry is great, in that sort of walled-garden knitterverse sense. The blog fills another aspect where the other forms of social media just don’t fit, so it does have value to me. Offline, my journal is probably my truest self, and I don’t have to self-edit the way I do for my public writing. Alas, self-editing my public writing is essential because I don’t want to get fired or piss off those I know in real life on the offhand chance my writing might be mildly amusing for the few readers I have out there.

When I started the blog, I hoped I would gain a small, but fairly stable readership. While I never expected The Blog to help me find that one additional skein of yarn I needed for a project, nor perhaps to point me to some good restaurants when I was on travel, I did hope that over the course of five years that I’d have readers who enjoyed my weekly or biweekly posts and interacted at least a little with me or with each other. And while I have tried, in the main, to write regularly, I never really acquired a regular, interactive readership of any size.

That lack of readership has resulted in a lack of motivation to use my scarce free time to write. I have a demanding full-time job and no lack of family and other obligations. When I have free time, I prioritize knitting over writing. When I do write, it tends to be to update my projects in Ravelry instead of here.

Ravelry is great, although its format is project-specific, rather than holistic. So, if I want to write about how my Green Tourmaline Shawl is coming along, it’s there on Rav. But if I want to post about travel-compatible knitting in general, it’ll have to be here.

You’ll see that I’ve not posted here since last October. What changed? In addition to the usual lack of time, I’ve had to work with my son on his schoolwork this year, and that’s taking time I ordinarily would have spent knitting and writing. Plus, I’ve decided to ramp up my exercise sessions, so I’m putting in more time Nordic walking and at the gym. These are good things, of course, but doing them leaves me precious little time to knit or write.

Given all that, why do I want to continue with the blog? I do see value in writing, when I have time.  I want to spend time writing for the blog in proportion to what I’m getting out of it. So, that may not be a whole lot right now, but it may improve in the future.

In the meantime, if things look quiet here and you’re wondering what I’m up to, check out my Ravelry page, Twitter, or Instagram. You can send me a message on Ravlery, as well.

Posted in Uncategorized | 1 Comment

That Question

The other evening, some colleagues and I were having dinner with some higher-ups who’d come from back East to our office for a visit. My boss, who must have been a game show host in a former life, was doing his usual bang-up job of keeping the conversation going.

“It’s really fascinating, the things our staff members like to do in their free time,” my boss noted. Let’s everyone say something about what they like to do. Julia?” he gestured to me from across the table. “You go first.”

I knew what he expected me to say. What’s more, I knew that if I didn’t discuss knitting as my passion, he’d only goad me into it. I replied, “I’m a knitter,” trying to sound as enthusiastic as I could about being forced to share this factoid with the visiting Alpha Male.

“You’re a what?” asked Alpha Male. His expression was incredulous, as if I’d slipped into some foreign language that he couldn’t understand.

“I knit,” I replied, being careful to enunciate, without over-doing it. This conversation was going exactly where I expected it to, sadly. I was about to remark about my other hobbies — things that might actually spark Alpha Male’s interest — when my boss chimed in.

“Tell him what you’re doing this weekend!” my boss implored. Now, given Alpha Male’s reaction to the knitting thing, this was definitely not where I would have directed the conversation, if it had been left up to me. My boss knew that I was going to the regional alpaca show this weekend, and that I was super-excited about it. We know these things about each other in my office. My office is like a family — dysfunctional at times, but by and large, we celebrate each other’s interests outside of work.

I looked at Alpha Male. “I’m going to an alpaca show,” I stated matter-of-factly. I was careful to not sound apologetic about it. I decided some time ago that if others had some sort of issue with my knitting as a hobby, that problem was with them, not me. I’m neither apologetic nor defensive about it, but I tend to not go on and on about it unless I’ve found a kindred spirit.

“A what?” Alpha Male responded. This time, I could detect a slight patronizing expression on his face, which he quickly adjusted. I might as well have been speaking ancient Greek. This conversation was at a dead end. Others at the table who had been involved in side chatter, were beginning to take note.

“It’s a show put on by local alpaca ranchers featuring alpacas, and that has fibers and yarns and demonstrations and such,” I replied. Then, I changed the subject. “My family is really involved in Scouts,” I offered, hoping that this would give us something else to talk about, or that someone else might chime in with a hobby Alpha Male could relate to. “I’ve got one son who’s an Eagle Scout and another pretty close,” I continued optmistically.

At that, Alpha Male looked relieved, like I’d slipped back into English. “Oh, I understand that’s something that requires a lot of parental commitment,” he said. I agreed, and the conversation moved to other people and other hobbies.

With the attention diverted from me, I sat back, took a sip of beer, and thought about how I wished this conversation had gone, and how I directed other, similar inquiries in a somewhat different direction.

I’m asked That Question on a fairly regular basis: “So, what do you like to do in your spare time?” In my mind, though, I tend to see past the question to what the questioner really wants to know: “What sorts of things do we have in common?” I’m always searching for that common ground, too. I find that I wind up having two kinds of conversations: maker-centric and non maker-centric, depending on the interests of the other person.

Just how I answer That Question depends on the inquirer. If I think the questioner is a maker, or perhaps loves one, I’ll put knitting front and center: “Oh, my biggest passion is knitting, and I do lots of other things, too, like Scouts, gardening, and food preservation.” Typically, one of those things will trigger a good conversation with a maker or someone who values us. We find that commonality.

Before we went to dinner the other night, I’d studied up on Alpha Male, and was pretty darn sure that he wasn’t a maker. We are roughly the same age and are on (ahem) rather different career tracks. Alpha Male was at the top of his classes in undergraduate and law schools. For my part, I had respectable, if unremarkable, grades. Alpha Male has had a high-powered, consuming career. I chose a path that was interesting and fulfilling to me, but which allows ample time for me to pursue my outside interests. I get the feeling that when Alpha Male isn’t doing something high-powered and legalish, he’s exercising himself half to death. He’s a little intense.

So, chatting about knitting with Alpha Male wasn’t high on my list of get-to-know-you conversation topics. Instead, had I been posed That Question and not been goaded into discussing knitting, I’d probably have said something like, “My family loves the outdoors here, so we’ve been very involved with Scouts. I also like to Nordic walk, go to the gym, read, garden, and knit.” When I phrase my hobbies like that, it’s often a good segueway into a discussion about Scouts, hiking, or the last books we’ve read. Someone might pick up on the knitting angle, but if not, that’s fine, too. It’s about finding that commonality.

As for Alpha Male and me, we never did find that commonality. I suppose that’s going to happen, sometimes. Perhaps we’ll have another opportunity at some later date to discover that connection.

Posted in Uncategorized | Leave a comment

A Hard Lesson About Row Counter Apps

Last night, I had a knitting crisis. We finished with dinner early, leaving me with a good hour-plus to work on Mom’s sweater.

I haven’t touched her sweater in over a week. My knitting has been mostly relegated to stockinette and garter stitch projects only, because much of my so-called spare time is now taken up by Nordic walking, strength training at the gym, and working with Eric on his chemistry homework. So, having an hour or so on a day when I wasn’t totally wiped out and had retained sufficient mental energy to follow a chart meant that I could make at least a little progress on the top-down cabled cardigan for Mom. I settled into my knitting chair, pulled out the chart and sweater, plugged in my iPhone, and pulled up the row counter app.

And then — nothing! The app refused to load or to do anything. I’d just updated to iOS 9, so I went to check to see if there was an update to the app that would make it play well with the new OS. Nope. I went to check the app store, and was disconcerted to find the app had been pulled from the store.

There I was, dead in the water. My hour-plus of knitting time was fast dwindling, as I was searching for some sort of fix, or at least an explanation. So, not only could I not access the app, I had no way to see the underlying data — my current row counts for the various parts of this project. I looked at my chart. I use highlighter tape to keep track of my rows, as well as the app, because the highlighter tape makes it easy to see where I am in a chart. I’d just finished the yoke, so I no longer had to keep track of sleeve and body increases, which was a good thing. If this snafu had happened during the yoke portion, I’d have a heck of a time reconstituting where I was.

At this point in the project, I’m working the fronts and back, and have a goodly number of rows to go before I have to start the gentle waist shaping. I can figure out pretty easily how many rows I have left to go before shaping. Before I did, though, I decided to check out Ravelry to see if others were having the same problem with this app.

On Ravelry, I discovered a thread on the app’s user group forum that indicated that, yes indeed, others are having the same problem, and that the developer was diligently working on a solution and plans to post an update to the software in the near future. Fine, as far as that goes. I have every expectation that in a week or so, we’ll get our update, and we can all use our spiffy app again. But will I?

I put aside Mom’s sweater, as I didn’t have the patience to reconstitute where I was in the pattern. Ay, that’s the problem, isn’t it? I never seem to have enough time to work on my projects, particularly those that require more thought that stockinette or garter stitch, so I need for things to go well when I do have the time and wherewithal to do so. I pulled out my garter-stitch shawl to knit and give this a think-through.

The reason I started using a row counter app in the first place was that I began a complicated Orenburg lace scarf some months ago. For that, I have to keep track of body repeats, border repeats, and pattern repeats within the body. I could have used my usual analog system of multiple row counters, coilless safety pins, and markings on the pattern. Instead, I bought an electronic counter which could keep track of three things at once. It made me nervous, though, because I found it too easy to erase the row counts on the counter. I sought a different solution, and tried out the app.

Eureka! I thought. The app was very customizable, stable, and it proved difficult to accidentally screw up my counts. So, when I started Mom’s sweater, it was a no-brainer to use the app for that, too.

Mom’s sweater calls for a top-down raglan construction, with five different cable charts in different parts of the pattern. An analog solution would require, at times, three row counters plus a system of coilless safety pins and pattern markings. It’s an ideal candidate for a row counter app. At least, when the row counter app is functional.

I realized that using a row counter app is a lot like entrusting your row counters to your kid or your second cousin or your next-door neighbor. The app’s functioning is controlled by at least three outside parties: the app developer, the owner of the phone’s operating software, and the app store. If those don’t play well, I have a situation not unlike leaving my row counters with the lady next door: She might be the nicest, most conscientious person in the world, but if I knock at her door to retrieve the counters and she doesn’t answer, I’m stuck. Why on Earth would I put myself in that situation?

So, tonight, I’m going to figure out where I am in the pattern. I’m pretty sure I don’t have enough row counters or safety pins in my stash room to accommodate this project, so I’ll run over to my LYS this weekend to buy more.

As for the Orenburg scarf-in-progress, I’m probably better off just waiting for the app update so that I can retrieve the data from my phone. Once I know where I am in that pattern, I’ll change over to an analog solution there, too.

The app was handy and slick and seductively easy. But this experience has taught me a hard lesson — my personal control over the row counter app is an illusion. If a developer takes it off an app store or the app no longer plays well with the latest OS, the result is just as if I’d given my row counters to my next-door neighbor for safekeeping. And what knitter in her right mind does that?


Posted in Uncategorized | 1 Comment