Friday, December 28, 2007
Happy Holidays
I just wanted to post a little something to say that I hope everyone had a great holiday (whichever one you celebrate). Best wishes for the coming year!
Tuesday, December 18, 2007
Two Cents
I recently finished a book that I think was called The Julie & Julia Project. (If I am incorrect about the title, anyone who knows is free to correct me.) It's about a woman who decides to cook her way through Julia Child's Mastering the Art of French Cooking. She starts at one end of the book and goes to the other, cooking every recipe in it. No skips, no substitutions. And in a year, her goal was to finish the book.
My initial response as I started reading it was the same as my mother's when I told her what I was reading: "She'll be a pig!" I mean, really. French cuisine is to die for, but it's incredibly rich (that would be why it's so good). Cream, butter, eggs, cholesterol -- if it's fattening, chances are it's in French food. If I were to cook my way through one of Julia Child's cookbooks (not that I would, because I have neither the patience nor the time to try many of the recipes, but assuming I did), by the end of the project, I would have gained about twenty-five pounds.
But then I got to thinking. If eating so much French food makes you fat, how come there aren't a whole lot of des cochons running around France? I've been in France enough times to know that not everyone is fat, or even overweight. In fact, (now, granted, I don't know the exact statistic here), I would be willing to bet that there are proportionately less overweight people in France than there are over here on our side of the pond.
So what is it about the French? How come they're capable of eating (and cooking) all these decadent, sinfully good foods and still stay healthy? How is it they are able to refrain from turning into des cochons and we aren't?
Any thoughts?
My initial response as I started reading it was the same as my mother's when I told her what I was reading: "She'll be a pig!" I mean, really. French cuisine is to die for, but it's incredibly rich (that would be why it's so good). Cream, butter, eggs, cholesterol -- if it's fattening, chances are it's in French food. If I were to cook my way through one of Julia Child's cookbooks (not that I would, because I have neither the patience nor the time to try many of the recipes, but assuming I did), by the end of the project, I would have gained about twenty-five pounds.
But then I got to thinking. If eating so much French food makes you fat, how come there aren't a whole lot of des cochons running around France? I've been in France enough times to know that not everyone is fat, or even overweight. In fact, (now, granted, I don't know the exact statistic here), I would be willing to bet that there are proportionately less overweight people in France than there are over here on our side of the pond.
So what is it about the French? How come they're capable of eating (and cooking) all these decadent, sinfully good foods and still stay healthy? How is it they are able to refrain from turning into des cochons and we aren't?
Any thoughts?
Monday, November 19, 2007
Snaps
Yeah, I know it's been a while since I last posted, but I've been working on my pictures blog lately, so there you go. You're probably all checking that one vigilantly anyway.
Anyway, I would like to say that after putting three pictures from my trip up here, only two people have responded to guess what any of them are, and one of them didn't guess -- she just said she knew where they were. So :P to her -- she's spoiling all the fun. But, Kathy e-mailed me and guessed that the one photograph was of the chapel next to Holyrood Palace in Edinburgh. And she's right. It is a picture of Holyrood Abbey. King James V (among numerous other Scottish royalty) is buried there.
The other two photographs, by the way, were of Loch Ness (the foggy one) and Loch Lomond (the sunny one). I would highly advise going to all three locales.
Snaps for Kathy!
Anyway, I would like to say that after putting three pictures from my trip up here, only two people have responded to guess what any of them are, and one of them didn't guess -- she just said she knew where they were. So :P to her -- she's spoiling all the fun. But, Kathy e-mailed me and guessed that the one photograph was of the chapel next to Holyrood Palace in Edinburgh. And she's right. It is a picture of Holyrood Abbey. King James V (among numerous other Scottish royalty) is buried there.
The other two photographs, by the way, were of Loch Ness (the foggy one) and Loch Lomond (the sunny one). I would highly advise going to all three locales.
Snaps for Kathy!
Tuesday, October 23, 2007
Isn't Fall Wonderful
It's doing that weird natural phenomenon called raining right now, so I'm taking advantage of the event. The other day, a couple of us went down to Harrisonburg to the Green Valley Book Fair, and we saw some really glorious sights as we drove down through the Shenandoah Valley, with the fall foliage in its glory. At one point after passing a particularly glorious tree, I made the comment that one of the most beautiful things nature can give us is a maple tree in the fall.
Did you ever stop to notice these spectacular trees? Every year, they "bloom" into gorgeous colors, almost as if they're on fire. Whether they turn yellow or red, they're simply breathtaking to behold.


*sigh*
Did you ever stop to notice these spectacular trees? Every year, they "bloom" into gorgeous colors, almost as if they're on fire. Whether they turn yellow or red, they're simply breathtaking to behold.


*sigh*
Thursday, October 18, 2007
And I'm Back
I just got home from a week's vacation in Scotland. It was truly a blast. (If you ever have the opportunity to travel to Britain, go. And preferably in the fall. It's definitely worth it.)
The thing that really amazed me was how incredibly rural the whole place was. Sure, Scotland has cities, and can be very built up in places; but for the most part, the land was so very undeveloped. Not empty or primitive in any way, but just incredibly bucolic and pastoral. There were places where you could go for miles and miles on end and not come across a town. Once you get away from the cities and out onto the moors, it's just amazing to see how much land there is. It was such a change from here in northern VA where it is all so built up and suburban. It was so great to get away from it all and just enjoy nature in its splendor.
Anyway, I took an amazing amount of pictures, and since the number is so great that I can't possibly e-mail them to you all, I am setting up a blog specifically for this trip so all of you can see them.
In the meantime, here is a preview of what will be on it. In fact, I'm going to make a game out of this :). Here is one of my photos:

And here is another:

And here is a third:

See if you can guess correctly what the photos are (they are from three different locations). I'll publicly recognize every person who can come up with the right answers. Have fun :)
The thing that really amazed me was how incredibly rural the whole place was. Sure, Scotland has cities, and can be very built up in places; but for the most part, the land was so very undeveloped. Not empty or primitive in any way, but just incredibly bucolic and pastoral. There were places where you could go for miles and miles on end and not come across a town. Once you get away from the cities and out onto the moors, it's just amazing to see how much land there is. It was such a change from here in northern VA where it is all so built up and suburban. It was so great to get away from it all and just enjoy nature in its splendor.
Anyway, I took an amazing amount of pictures, and since the number is so great that I can't possibly e-mail them to you all, I am setting up a blog specifically for this trip so all of you can see them.
In the meantime, here is a preview of what will be on it. In fact, I'm going to make a game out of this :). Here is one of my photos:
And here is another:
And here is a third:
See if you can guess correctly what the photos are (they are from three different locations). I'll publicly recognize every person who can come up with the right answers. Have fun :)
Tuesday, October 02, 2007
Take the Time
You ever notice that whenever you ask someone how they are, they always say they're fine? And whenever anyone asks you how you are, you always say you're fine, even when you're not? One time someone asked me how I was doing, and, even though I had a horrific head cold, and I had had a really long day, and I just wanted to curl up in my bed and ignore the world for a day, I told this person I was doing just fine, thanks.
I was thinking about this earlier today, and the thought occurred to me that, even though we're taught at a relatively young age to be honest with others, we're all guilty of this lie at some point or another. We all say to someone that we're doing great, even when life has just handed us a huge batch of lemons. I think this comes from the fact that asking someong how he or she is has come to be second nature to us. It's kind of like saying Hi to someone. We ask this person how they are because it's been ingrained into us. Everyone else does it, so we do it too.
The other day, after a horribly rotten day at work, I went to choir practice, and two people came up to me and asked me how I was. Instead of the standard "Fine, thanks," I told them straight out that I had had a really bad day. Both of them immediately asked if there was anything they could do, and offered their support. I walked away thinking how wonderful it was to have friends who actually cared about how my day went.
My point (and I do have one, even though it sometimes takes a while to get around to it), is that I think we (and when I say "we," I mean society as a whole) need to get back to standard etiquette and not do things just out of instinct and habit. We need to take the time to listen to each other. If we ask people how they are, shouldn't we be genuinely interested in their answers? If you don't really care about what they have to say, then why in the world would you ask the question? No wonder we always say "Fine, thanks" whenever anyone asks us how we are.
So, let's all take the time to listen to others. If you aren't interested in how a person is feeling, or how his or her day went, don't ask. And if you do ask, take the time to listen to what he or she has to say. And if someone asks you the same question, be honest. Don't say you're feeling fine if you aren't. You don't have to go into all the details (I didn't with my friends at church), but if you aren't feeling well, say so. If you had a long day at work, mention that. A little bit of honesty and thoughtfulness can go a long way.
I was thinking about this earlier today, and the thought occurred to me that, even though we're taught at a relatively young age to be honest with others, we're all guilty of this lie at some point or another. We all say to someone that we're doing great, even when life has just handed us a huge batch of lemons. I think this comes from the fact that asking someong how he or she is has come to be second nature to us. It's kind of like saying Hi to someone. We ask this person how they are because it's been ingrained into us. Everyone else does it, so we do it too.
The other day, after a horribly rotten day at work, I went to choir practice, and two people came up to me and asked me how I was. Instead of the standard "Fine, thanks," I told them straight out that I had had a really bad day. Both of them immediately asked if there was anything they could do, and offered their support. I walked away thinking how wonderful it was to have friends who actually cared about how my day went.
My point (and I do have one, even though it sometimes takes a while to get around to it), is that I think we (and when I say "we," I mean society as a whole) need to get back to standard etiquette and not do things just out of instinct and habit. We need to take the time to listen to each other. If we ask people how they are, shouldn't we be genuinely interested in their answers? If you don't really care about what they have to say, then why in the world would you ask the question? No wonder we always say "Fine, thanks" whenever anyone asks us how we are.
So, let's all take the time to listen to others. If you aren't interested in how a person is feeling, or how his or her day went, don't ask. And if you do ask, take the time to listen to what he or she has to say. And if someone asks you the same question, be honest. Don't say you're feeling fine if you aren't. You don't have to go into all the details (I didn't with my friends at church), but if you aren't feeling well, say so. If you had a long day at work, mention that. A little bit of honesty and thoughtfulness can go a long way.
Tuesday, September 25, 2007
Pronouns and Apostrophes
Those of you who know me well know that I cannot stand grammar faux pas. Particularly those that break standard rules that SHOULD HAVE BEEN DRILLED INTO YOU IN GRADE SCHOOL!!!!! (If they weren't, there is something seriously lacking in your education.) This past week, I have come across three instances of the same mistake, and since they were all done by people who really should have known better (two of them were professional writers), it is time for a lecture.
Possessive pronouns DO NOT (do I need to repeat myself? DO NOT) have apostrophes. This is to differentiate them all from the contractions that these pronouns sometimes form with the verb "is." Possessive pronouns denote ownership of something and are sometimes used as adjectives that tell the reader who owns a particular item. No contraction. No apostrophe.
The big confusion on this is the word "Its." There are two words with these three letters in this order: "Its" and "It's." They are TWO DIFFERENT WORDS and have TWO DIFFERENT MEANINGS. Therefore, they are NOT interchangeable.
"Its" is a possessive pronoun, and is used to denote ownership: "That book has lost ITS cover." Here the word is being used to describe which cover has been lost.
"It's" is a contraction for "it is." It is a subject and verb together, as in: "It looks like IT'S going to rain today."
There's even a simple test to see which one you need: every time you are about to write down the word, say the sentence in your mind replacing the word with "it is" and see if it still makes sense. Let's continue with the above examples:
"That book has lost IT IS cover."
"It looks like IT IS going to rain today."
If the sentence makes sense, you need the apostrophe (IT'S). If it doesn't, you leave it out (ITS).
Does everyone see the difference?
Possessive pronouns DO NOT (do I need to repeat myself? DO NOT) have apostrophes. This is to differentiate them all from the contractions that these pronouns sometimes form with the verb "is." Possessive pronouns denote ownership of something and are sometimes used as adjectives that tell the reader who owns a particular item. No contraction. No apostrophe.
The big confusion on this is the word "Its." There are two words with these three letters in this order: "Its" and "It's." They are TWO DIFFERENT WORDS and have TWO DIFFERENT MEANINGS. Therefore, they are NOT interchangeable.
"Its" is a possessive pronoun, and is used to denote ownership: "That book has lost ITS cover." Here the word is being used to describe which cover has been lost.
"It's" is a contraction for "it is." It is a subject and verb together, as in: "It looks like IT'S going to rain today."
There's even a simple test to see which one you need: every time you are about to write down the word, say the sentence in your mind replacing the word with "it is" and see if it still makes sense. Let's continue with the above examples:
"That book has lost IT IS cover."
"It looks like IT IS going to rain today."
If the sentence makes sense, you need the apostrophe (IT'S). If it doesn't, you leave it out (ITS).
Does everyone see the difference?
Thursday, September 13, 2007
Traffic Report
I live about ten miles from where I work, which gives me a little commute each day. When there isn't much traffic on the roads, it takes about 25 minutes to get to work. When there IS traffic (everyday it seems, now that school has started), it takes about 35-45 minutes to get to work each day. (Going home takes longer.) Luckily, I am able to carpool half the time, so that, at least, cuts down on my gas consumption.
Tuesday, L and I gave ourselves about 45 minutes to get to work. Plenty of time. About 2/3 of the way there, because we were making good time, we stopped for coffee. We were out in and out of the Starbucks in 5 minutes. We were about ten minutes from the library, and we had fifteen minutes until it opened. Still plenty of time. Until we ran into a huge bottleneck half a mile down the road, in which we sat for about ten minutes crawling along at a snail's pace, thus causing us to be a couple minutes late for work.
So, yesterday (that would be Wednesday), we decided to give ourselves a little more time and left for work 55 minutes before we needed to be there. A great idea. We made it about ten minutes down the road before we ran into another traffic jam. At first we figured that it was just a little road work, which has happened before, and that in a half a mile it would all open back up again.
But it didn't. Instead of opening back up, it got even tighter. It turns out there was a huge accident. We were detoured from a six-lane highway to a two-lane back road. For about forty minutes, we went absolutely nowhere. L was driving (she has a hybrid, thankfully), and when we looked at her energy consumption (one of the many cool things about a Prius is that you can do this), we realized that the car had not used any energy for about five minutes while we sat, completely still, on the road. Our fifteen minute grace period we had given ourselves disappeared, so that for the second time, we were late for work. This time, by about fifteen minutes. And to exacerbate the whole situation, we had two programs happening yesterday morning, made more complicated by the fact that three of us (another coworker comes from the same direction and got stuck in the same jam) were all late.
Life would be so much easier if we didn't have to go anywhere.
On the other hand, when you are spending 40 minutes sitting in a traffic jam, and someone else happens to be driving (please don't do this when YOU are driving), you can get about two inches of knitting done on when working with 115 stitches on size 7 needles.
Tuesday, L and I gave ourselves about 45 minutes to get to work. Plenty of time. About 2/3 of the way there, because we were making good time, we stopped for coffee. We were out in and out of the Starbucks in 5 minutes. We were about ten minutes from the library, and we had fifteen minutes until it opened. Still plenty of time. Until we ran into a huge bottleneck half a mile down the road, in which we sat for about ten minutes crawling along at a snail's pace, thus causing us to be a couple minutes late for work.
So, yesterday (that would be Wednesday), we decided to give ourselves a little more time and left for work 55 minutes before we needed to be there. A great idea. We made it about ten minutes down the road before we ran into another traffic jam. At first we figured that it was just a little road work, which has happened before, and that in a half a mile it would all open back up again.
But it didn't. Instead of opening back up, it got even tighter. It turns out there was a huge accident. We were detoured from a six-lane highway to a two-lane back road. For about forty minutes, we went absolutely nowhere. L was driving (she has a hybrid, thankfully), and when we looked at her energy consumption (one of the many cool things about a Prius is that you can do this), we realized that the car had not used any energy for about five minutes while we sat, completely still, on the road. Our fifteen minute grace period we had given ourselves disappeared, so that for the second time, we were late for work. This time, by about fifteen minutes. And to exacerbate the whole situation, we had two programs happening yesterday morning, made more complicated by the fact that three of us (another coworker comes from the same direction and got stuck in the same jam) were all late.
Life would be so much easier if we didn't have to go anywhere.
On the other hand, when you are spending 40 minutes sitting in a traffic jam, and someone else happens to be driving (please don't do this when YOU are driving), you can get about two inches of knitting done on when working with 115 stitches on size 7 needles.
Tuesday, September 11, 2007
Tedium and Pointlessness
I've just recently finished knitting a sleevless dress shell out of this beautiful blue acryllic yarn. The finished product is absolutely beautiful. It's sparkly, it fits well, and it's in a color that looks good on me. I worked the whole thing in the round until I got to the armholes, so with the exception of the shoulders, there are no seams. My favorite kind of project.
I wore it for the first time the day after I finished it. It looked well, but I noticed that it didn't hang completely straight in the back around the armholes. The way the pattern had indicated to make a selvage here was causing the edging to roll in on itself slightly.
No problem, I thought to myself. This will all be fixed when I block it. This is where I began to realize that I didn't particularly enjoy the project as I had originally. It's acryllic, which means that it has to be wet-blocked, and it's hand-wash only. Still, I tell myself that it's no big deal. I wash the thing and lay it out carefully, pinning it with the exact dimensions I want it.
And there it lay all weekend, drying into place like it was supposed to. Finally on Monday evening, I unpinned it and looked at it. It looked great. It was the right size. I was even able to fix a little pucker in the stitches that had occurred when I picked up the stitches for the neck. I was pleased.
And then, I put it on. At first, I didn't realize anything was amiss. Until I was at work. And I realized that despite the fact that I had followed the pattern exactly the whole way, the bloomin selvage was STILL rolling in at the armholes, meaning that it STILL was not hanging straight in the back. Moreover, in my attempt to block the armholes correctly, I had inadvertently increased the sizes slightly, causing the back to hang even less straight than it had originally.
I am ticked. I am annoyed. I am ready to curse the knitting gods. I just wasted an entire weekend doing a step on this particular piece that I didn't even have to do, because it was done in all one piece, and it turned out to be a huge colossal waste of time.
I hate blocking.
I wore it for the first time the day after I finished it. It looked well, but I noticed that it didn't hang completely straight in the back around the armholes. The way the pattern had indicated to make a selvage here was causing the edging to roll in on itself slightly.
No problem, I thought to myself. This will all be fixed when I block it. This is where I began to realize that I didn't particularly enjoy the project as I had originally. It's acryllic, which means that it has to be wet-blocked, and it's hand-wash only. Still, I tell myself that it's no big deal. I wash the thing and lay it out carefully, pinning it with the exact dimensions I want it.
And there it lay all weekend, drying into place like it was supposed to. Finally on Monday evening, I unpinned it and looked at it. It looked great. It was the right size. I was even able to fix a little pucker in the stitches that had occurred when I picked up the stitches for the neck. I was pleased.
And then, I put it on. At first, I didn't realize anything was amiss. Until I was at work. And I realized that despite the fact that I had followed the pattern exactly the whole way, the bloomin selvage was STILL rolling in at the armholes, meaning that it STILL was not hanging straight in the back. Moreover, in my attempt to block the armholes correctly, I had inadvertently increased the sizes slightly, causing the back to hang even less straight than it had originally.
I am ticked. I am annoyed. I am ready to curse the knitting gods. I just wasted an entire weekend doing a step on this particular piece that I didn't even have to do, because it was done in all one piece, and it turned out to be a huge colossal waste of time.
I hate blocking.
Monday, September 10, 2007
Here's Your Sign
I'm amazed at the ineptitude of some people. Truly, utterly amazed. And I don't know why I should be, really. I mean, I've spent most of my adult life working as a public service employee. You would think I would be used to meeting incompetent people.
But this really takes the cake. The other night, I was watching tv, and during commercials, there were these ads for those REALLY, INCREDIBLE MADE-FOR-TV items that everyone ABSOLUTELY HAS TO HAVE in order to make their lives better. Like a portable electric can opener, or knives that can go through dry wall, or gloves that can peel potatoes.
Now, I realize it can be difficult (not to mention time-consuming) to peel potatoes well. But Saturday night, I saw an ad for a photo slicer. Basically, all it was was a small paper cutter with tinted plastic that allowed the user to see exactly where the cut was going to go. I realize this can be useful (assuming it actually works), but the people they showed using this tool were using it because they couldn't make the same cut with scissors.
How hard, exactly, can it be to cut a straight line with scissors? In the ad, the people were struggling to cut photographs so they could go into a frame. It's not like they had arthritis, and it's not like they were cutting plain ordinary paper without a design. They appeared to be pefectly capable people. Cutting a photograph. With straight lines. And if worse came to worse, they could always flip the photo over and use a ruler to draw a straight line on the back.
*sigh* As Jeff Foxworthy (or whoever the guy is) would say, "Here's your sign."
But this really takes the cake. The other night, I was watching tv, and during commercials, there were these ads for those REALLY, INCREDIBLE MADE-FOR-TV items that everyone ABSOLUTELY HAS TO HAVE in order to make their lives better. Like a portable electric can opener, or knives that can go through dry wall, or gloves that can peel potatoes.
Now, I realize it can be difficult (not to mention time-consuming) to peel potatoes well. But Saturday night, I saw an ad for a photo slicer. Basically, all it was was a small paper cutter with tinted plastic that allowed the user to see exactly where the cut was going to go. I realize this can be useful (assuming it actually works), but the people they showed using this tool were using it because they couldn't make the same cut with scissors.
How hard, exactly, can it be to cut a straight line with scissors? In the ad, the people were struggling to cut photographs so they could go into a frame. It's not like they had arthritis, and it's not like they were cutting plain ordinary paper without a design. They appeared to be pefectly capable people. Cutting a photograph. With straight lines. And if worse came to worse, they could always flip the photo over and use a ruler to draw a straight line on the back.
*sigh* As Jeff Foxworthy (or whoever the guy is) would say, "Here's your sign."
Saturday, September 08, 2007
Semantics, Schmemantics
Last night, I was sitting in a coffee shop, enjoying my caramel latte, and I happened to strike up a conversation with a woman sitting nearby, and we had a nice chat. I had brought with me a baby sweater I was in the process of making, and a journal in which I like to write my latest plot ideas, and had been working on both throughout the course of the evening. Halfway through my conversation with this woman, she, apparently noticing the sweater, asked me, "So, did your mother teach you how to crochet?"
The short answer to this question is, of course, yes. My mother did teach me how to crochet. I was five years old, and she thought it would be neat if I made a scarf for my sister.
However, since the project I was working on was knit, not crochet, I thought I might pause here in a moment of reflection and explain to all you non-woolly people out there the difference between the two. Be warned. It's about to get technical.
Crochet is made with a hook.
If you are right-handed, you hold the hook in your right hand and the yarn in your left (don't ask me how you hold it if you're left-handed -- I don't know). You are only ever holding this one hook at a time. Ever. The basic crochet stich (some people call it a single crochet, others call it a double.) is based on something called chaining, and is made directly on top of the row of stitches, and creates a large, boxy-looking stitch. Think of building a wall with Legoes. You're placing one brick directly on top of another. When all you do, row after row, is this stitch, you produce thick, slightly wavy rows in the fabric. There is no casting-on in crochet. You simply chain the number of stitches you want, turn around, and work into the chain. When you're done, simply stop at the end of the row. There are two ways it is less complicated than knitting (I'm not going to say easier, because if I do, someone will call me on it). 1) Unless you are either making funky bobbles or working Tunisian style (neither of which I'm going to get into right now), there is only ever one stitch on your hook, making it marvelously easy to frog (ripping back in case of mistake). 2) Because there is usually only ever one stitch on the hook, there is no need ever to cast off. When you get to the end of a row and wish to finish, you can just stop.
Knit is made with needles
. For back and forth knitting (I'm not going to get into working in a round), they come in pairs, and you're always holding two at a time -- your working needle and your holding needle. Most people hold their working needle in their right hand and the holder needle in their left. All the stitches in a row are on the needles, and the produced fabric hangs straight down from the needles as you work. The knit stitch is made from the side of the previous row. With Legoes, this time think of creating a staircase. Instead of placing the brick directly on top of the one below so that all six bumps are interlocking, place it so that only half the bumps are interlocking, and it looks more like shallow steps. The created stitch is short and vertical, and when you knit every row, you create horizontal ridges going across your fabric. When you're finished with a project, it's necessary to cast-off all your stitches (this can be a bit of a pain at times, and I'm not going to get into it here). The resulting fabric produces a slightly neater look than crochet, but frogging isn't nearly as easy, and can be downright irritatingly tedious at times.
I have probably now created more questions in your minds now regarding these two crafts, but at least now, I have given vent to my frustrations about this. Feel free to come to my Woolgathering class every other Wednesday afternoon if you wish to have a more hands-on lesson in the two techniques.
The short answer to this question is, of course, yes. My mother did teach me how to crochet. I was five years old, and she thought it would be neat if I made a scarf for my sister.
However, since the project I was working on was knit, not crochet, I thought I might pause here in a moment of reflection and explain to all you non-woolly people out there the difference between the two. Be warned. It's about to get technical.
Crochet is made with a hook.
If you are right-handed, you hold the hook in your right hand and the yarn in your left (don't ask me how you hold it if you're left-handed -- I don't know). You are only ever holding this one hook at a time. Ever. The basic crochet stich (some people call it a single crochet, others call it a double.) is based on something called chaining, and is made directly on top of the row of stitches, and creates a large, boxy-looking stitch. Think of building a wall with Legoes. You're placing one brick directly on top of another. When all you do, row after row, is this stitch, you produce thick, slightly wavy rows in the fabric. There is no casting-on in crochet. You simply chain the number of stitches you want, turn around, and work into the chain. When you're done, simply stop at the end of the row. There are two ways it is less complicated than knitting (I'm not going to say easier, because if I do, someone will call me on it). 1) Unless you are either making funky bobbles or working Tunisian style (neither of which I'm going to get into right now), there is only ever one stitch on your hook, making it marvelously easy to frog (ripping back in case of mistake). 2) Because there is usually only ever one stitch on the hook, there is no need ever to cast off. When you get to the end of a row and wish to finish, you can just stop.Knit is made with needles
. For back and forth knitting (I'm not going to get into working in a round), they come in pairs, and you're always holding two at a time -- your working needle and your holding needle. Most people hold their working needle in their right hand and the holder needle in their left. All the stitches in a row are on the needles, and the produced fabric hangs straight down from the needles as you work. The knit stitch is made from the side of the previous row. With Legoes, this time think of creating a staircase. Instead of placing the brick directly on top of the one below so that all six bumps are interlocking, place it so that only half the bumps are interlocking, and it looks more like shallow steps. The created stitch is short and vertical, and when you knit every row, you create horizontal ridges going across your fabric. When you're finished with a project, it's necessary to cast-off all your stitches (this can be a bit of a pain at times, and I'm not going to get into it here). The resulting fabric produces a slightly neater look than crochet, but frogging isn't nearly as easy, and can be downright irritatingly tedious at times.I have probably now created more questions in your minds now regarding these two crafts, but at least now, I have given vent to my frustrations about this. Feel free to come to my Woolgathering class every other Wednesday afternoon if you wish to have a more hands-on lesson in the two techniques.
Monday, August 27, 2007
And now for something different
First off, an announcement: I am just about finished with the dratted pair of socks! I'm just about to begin the ribbing on the second sock! The heel has turned, the sock is fitting, everything is going beautifully. Wahoo!
And now for a review of the latest book I've read.
Over the weekend, I read the book First Light by Rebecca Stead. The book alternates between the view points of its two main characters -- Thea and Peter. Peter is the son of two scientists who have taken him to Greenland with them on an expedition to study Global Warming. Lately, Peter has begun to suffer from severe headaches, similar to the ones his mother has, and he has begun to see things that others do not. Thea is the last female in the First Line of ancestors who originally settled Gracehope, a community located underground in the middle of Greenland's ice cap. Lately the community has begun to outgrow the space where it is living. Thea is anxious about the possibility of exploring the surface above them to look for more space, and when she and her friend Mattias find a way up, they run into Peter, who is out exploring the area around his parents' camp. After Thea and Mattias return underground, Thea learns a disturbing secret about her mother that her family has kept from her throughout her life, but just as she discovers it, Peter arrives with his mother, who apparently is Thea's aunt who had been banished from Gracehope years before by Rowen, Thea's grandmother, who has refused to allow anyone to go to the surface out of fear of the persecution that drove community underground in the first place. After a climactic showdown between Rowen and Thea, the novel ends relatively happily. But the readers are left with the question of what the long-term effects of Global Warming are going to be on Gracehope, and how much time there is before the cap melts and the community falls into the ocean.
It was a captivating read. I finished the book around 12:30 at night because I simply couldn't wait until the next morning to find out what was going to happen next. There were enough twists and turns in the plotline to keep me interested, although the intelligence and technological adeptness of the Gracehope citizenry stretched my mind at times.
Anyone who has read and enjoyed Jeanne DuPrau's City of Ember, or Lois Lowry's Gathering Blue would enjoy this novel.
And now for a review of the latest book I've read.
Over the weekend, I read the book First Light by Rebecca Stead. The book alternates between the view points of its two main characters -- Thea and Peter. Peter is the son of two scientists who have taken him to Greenland with them on an expedition to study Global Warming. Lately, Peter has begun to suffer from severe headaches, similar to the ones his mother has, and he has begun to see things that others do not. Thea is the last female in the First Line of ancestors who originally settled Gracehope, a community located underground in the middle of Greenland's ice cap. Lately the community has begun to outgrow the space where it is living. Thea is anxious about the possibility of exploring the surface above them to look for more space, and when she and her friend Mattias find a way up, they run into Peter, who is out exploring the area around his parents' camp. After Thea and Mattias return underground, Thea learns a disturbing secret about her mother that her family has kept from her throughout her life, but just as she discovers it, Peter arrives with his mother, who apparently is Thea's aunt who had been banished from Gracehope years before by Rowen, Thea's grandmother, who has refused to allow anyone to go to the surface out of fear of the persecution that drove community underground in the first place. After a climactic showdown between Rowen and Thea, the novel ends relatively happily. But the readers are left with the question of what the long-term effects of Global Warming are going to be on Gracehope, and how much time there is before the cap melts and the community falls into the ocean.
It was a captivating read. I finished the book around 12:30 at night because I simply couldn't wait until the next morning to find out what was going to happen next. There were enough twists and turns in the plotline to keep me interested, although the intelligence and technological adeptness of the Gracehope citizenry stretched my mind at times.
Anyone who has read and enjoyed Jeanne DuPrau's City of Ember, or Lois Lowry's Gathering Blue would enjoy this novel.
Monday, August 20, 2007
Gauge (or Weird Inexplicable Math Phenomena)
A coworker of mine has asked me to teach her how to knit socks. I am thrilled with this request. I couldn't be happier. So, (because I can't possibly part with stuff from my own stash) I have bought her two skeins of microspun acryllic and a set of size 1 needles (for you people who are used to the Metric system, I think it's somewhere around 2 mm). But this means, of course, that I need to be making a set of socks at the same time. So, when I bought the microspun, I also bought two skeins of a cotton blend yarn that I could make in to socks for myself.
So I cast on the cotton and began my ribbing. All is going well. And after the inch and a half of ribbing, I begin my pattern. Then, after about three inches, I take a good look at what I've accomplished. And I realize that for some reason, even though I got gauge with this pattern (7.5 stitches/inch), this sock is not going to fit.
I decide to adjust my stitch count and needle size. I also decide to do something I've never done before -- knit the sock toe-up -- in an effort to get a better fit. I rip out my previous attempt (a thousand curses -- that pattern was beautiful), shrink the stitches from 60 to 56, go down a needle size, and begin a different pattern.
After about two inches, I realize that the bloomin' thing is still too big. I don't understand this. The gauge gods must be having a huge laugh at my expense. My ankle is 8 inches around. I'm knitting (now) at a gauge of 7 stitches to an inch. 56 stitches should be the perfect number. But it isn't.
So I rip it back (again), cursing the gauge gods as I go. At least at this point, I don't have to rip it back the whole way, just to where I started increasing for the toe, and try again at 48 stitches.
This time, it works. (Hallelujah!) I continue with my pattern up the foot to the heel. But here, another problem arises. I misjudge how much I need to knit before starting the heel (even though I'm basing everything on another sock) and start the heel way too early. As a result, I have to rip the stupid heel back twice before finally getting one that will fit me.
I am over the heel now and have begun working my way up the leg. And the sock is still fitting. *phew* Now that I have gotten the hang of this thing, I think perhaps I will knit all my socks starting with the toe ;)
But never for someone else. Never ever for someone other than me.
So I cast on the cotton and began my ribbing. All is going well. And after the inch and a half of ribbing, I begin my pattern. Then, after about three inches, I take a good look at what I've accomplished. And I realize that for some reason, even though I got gauge with this pattern (7.5 stitches/inch), this sock is not going to fit.
I decide to adjust my stitch count and needle size. I also decide to do something I've never done before -- knit the sock toe-up -- in an effort to get a better fit. I rip out my previous attempt (a thousand curses -- that pattern was beautiful), shrink the stitches from 60 to 56, go down a needle size, and begin a different pattern.
After about two inches, I realize that the bloomin' thing is still too big. I don't understand this. The gauge gods must be having a huge laugh at my expense. My ankle is 8 inches around. I'm knitting (now) at a gauge of 7 stitches to an inch. 56 stitches should be the perfect number. But it isn't.
So I rip it back (again), cursing the gauge gods as I go. At least at this point, I don't have to rip it back the whole way, just to where I started increasing for the toe, and try again at 48 stitches.
This time, it works. (Hallelujah!) I continue with my pattern up the foot to the heel. But here, another problem arises. I misjudge how much I need to knit before starting the heel (even though I'm basing everything on another sock) and start the heel way too early. As a result, I have to rip the stupid heel back twice before finally getting one that will fit me.
I am over the heel now and have begun working my way up the leg. And the sock is still fitting. *phew* Now that I have gotten the hang of this thing, I think perhaps I will knit all my socks starting with the toe ;)
But never for someone else. Never ever for someone other than me.
Tuesday, August 07, 2007
Socktopia
The other week, I read in a blog that I have linked to on my site (see Yarn Harlot for more information) about someone who is capable of recruiting knitters like flies to honey. She has discovered a knitting project where you are only given a little bit of the pattern at a time, and was encouraging others to join the project as well. When I read the blog, I laughed out loud at S's (she would be the yarn harlot, not the person who had originally discovered the pattern) weak will to resist this person. The idea of becoming completely vulnerable to a pattern project like this seemed hysterical to me.
The wool gods, it seems, have a sense of humor. This morning, I came across the blog Socktopia. It is a project where the blogger (and all her fans) knit a socks for a month that are all based on a certain theme. Last month, the theme was Harry Potter, and the blogger provided three socks based off of the different novels (one was based off Nagini -- I'm not entire sure of the reasoning behind this). This month, the theme is Mystery sock. Every Monday, a new part of the pattern is given out, so that by the end of the month, the knitter would have finished the socks.
Socks. Socks are my absolute favorite thing in the world to knit. They go fast (I can usually do a pair in a week), they're portable (a sock on the needles fits into my purse quite nicely), they're small (which means you can knit them any time of the year and won't get hot), they're versatile (you can do pretty much anything you want in the design), they're cheap (even with high-quality wool, the cost of the yarn is relatively miniscule because they don't use much yarn), they're always needed (if made correctly, a sock is the only hand-knit item that is made to wear out), and they're conversation starters (people tend to be fascinated by the fact that I can knit them). I never need an excuse to knit socks. Never mind the fact that knitting on tiny needles aggravates my carpal tunnel, or that anyone can buy perfectly good socks at Wal-Mart for mere pennies. From the first hand-knit socks that I slid onto my feet, I was hooked. There is no way I will ever be able to stay away from this blog.
The blog's website is http://socktopia.net. Anyone can join anytime. It was originally designed to go through the end of the year, but it's been extended through next year as well. And if you knit fast, you can go back and work on the old monthly projects also.
The wool gods, it seems, have a sense of humor. This morning, I came across the blog Socktopia. It is a project where the blogger (and all her fans) knit a socks for a month that are all based on a certain theme. Last month, the theme was Harry Potter, and the blogger provided three socks based off of the different novels (one was based off Nagini -- I'm not entire sure of the reasoning behind this). This month, the theme is Mystery sock. Every Monday, a new part of the pattern is given out, so that by the end of the month, the knitter would have finished the socks.
Socks. Socks are my absolute favorite thing in the world to knit. They go fast (I can usually do a pair in a week), they're portable (a sock on the needles fits into my purse quite nicely), they're small (which means you can knit them any time of the year and won't get hot), they're versatile (you can do pretty much anything you want in the design), they're cheap (even with high-quality wool, the cost of the yarn is relatively miniscule because they don't use much yarn), they're always needed (if made correctly, a sock is the only hand-knit item that is made to wear out), and they're conversation starters (people tend to be fascinated by the fact that I can knit them). I never need an excuse to knit socks. Never mind the fact that knitting on tiny needles aggravates my carpal tunnel, or that anyone can buy perfectly good socks at Wal-Mart for mere pennies. From the first hand-knit socks that I slid onto my feet, I was hooked. There is no way I will ever be able to stay away from this blog.
The blog's website is http://socktopia.net. Anyone can join anytime. It was originally designed to go through the end of the year, but it's been extended through next year as well. And if you knit fast, you can go back and work on the old monthly projects also.
Thursday, July 19, 2007
The Last Book -- Spoiler Alert!
On Saturday afternoon, I stepped out of my apartment door and picked up the copy of Harry Potter and the Deathly Hallows that I had preordered from Amazon and immediately started reading. It took me about 8 hours, and I finished a little bit after midnight. I know that I am going to have to reread it at some point, because I was so all fired up to get to the ending that I know that I skimmed over a lot of points. But all in all, I thought it was a really good read.
I would, however, like to respond to a few things that have been mentioned in someone else's blog regarding this book.
First of all, yes, I will admit that the epilogue is a little too cheesy. But guess what folks? That's how JKR intended it to be! She wrote that chapter way back in the early days when she was first writing Philosopher's Stone. And while she may have changed a few details along the way, it's the way she wanted the entire story to end. I agree that it's a little pat (and yes, I wanted to know a little bit more about a few of the characters), but I'm not going to gripe about it. It's the way she wanted it written.
Secondly, this person mentions (and I quote) "Where's Alan Rickman's big death scene? Does JKR want to deny him his Oscar?"
Ummm. Excuse me? His death scene? First of all, his character does get a death scene, and (in my own humble opninion) it's pretty cool too. Secondly, since when is it the responsibility of an author to determine how much screen time an actor receives? JKR wrote the book for which the movie will be based, not the other way around. It is not her job to change the way she originally intended the story to end just because we happen to like one of the actors that plays one of the major characters. Moreover, she has always maintained that HP came to her pretty much fully formed while she was riding the train one day, and that was way back in the early nineties. Over fifteen years ago! Back then, AR was the Sheriff of Nottingham, and JKR had no idea that HP was going to a successful story, let alone become the basis for seven major blockbusters. And the fact that she had written the epilogue at the very beginning leads me to believe that the way that she deals with this particular character in the book is the way she had always intended it. Besides, even if she did take the different actors and actresses into account when she finished the book, I personally liked the way she dealt with this character, because I think that it's the only way she could have dealt with him that we readers (let alone Harry) would have found believable. And if AR is half the actor I know him to be, he's going to pull off that scene REALLY, REALLY well.
(Let's just hope that the director is going to think so also.)
I would, however, like to respond to a few things that have been mentioned in someone else's blog regarding this book.
First of all, yes, I will admit that the epilogue is a little too cheesy. But guess what folks? That's how JKR intended it to be! She wrote that chapter way back in the early days when she was first writing Philosopher's Stone. And while she may have changed a few details along the way, it's the way she wanted the entire story to end. I agree that it's a little pat (and yes, I wanted to know a little bit more about a few of the characters), but I'm not going to gripe about it. It's the way she wanted it written.
Secondly, this person mentions (and I quote) "Where's Alan Rickman's big death scene? Does JKR want to deny him his Oscar?"
Ummm. Excuse me? His death scene? First of all, his character does get a death scene, and (in my own humble opninion) it's pretty cool too. Secondly, since when is it the responsibility of an author to determine how much screen time an actor receives? JKR wrote the book for which the movie will be based, not the other way around. It is not her job to change the way she originally intended the story to end just because we happen to like one of the actors that plays one of the major characters. Moreover, she has always maintained that HP came to her pretty much fully formed while she was riding the train one day, and that was way back in the early nineties. Over fifteen years ago! Back then, AR was the Sheriff of Nottingham, and JKR had no idea that HP was going to a successful story, let alone become the basis for seven major blockbusters. And the fact that she had written the epilogue at the very beginning leads me to believe that the way that she deals with this particular character in the book is the way she had always intended it. Besides, even if she did take the different actors and actresses into account when she finished the book, I personally liked the way she dealt with this character, because I think that it's the only way she could have dealt with him that we readers (let alone Harry) would have found believable. And if AR is half the actor I know him to be, he's going to pull off that scene REALLY, REALLY well.
(Let's just hope that the director is going to think so also.)
Wednesday, July 18, 2007
And Now, a Lesson in Math
So today, having slept in and dilly-dallied to the point where I didn't have time to pack my lunch, I had to go out to grab a bite to eat. So, at around 12:30, I trecked out into the heat to go to the nearby Subway two doors down. I ordered a sandwich combo and paid for my meal. As I started to walk away, I realized the woman hadn't given me my cup, so I asked for one.
Her: "Oh, that's for the combo."
Me: "Yes, that's what I ordered."
Her: "Oh. I guess I'm going to have to ring you up again."
(Now, personally, if this were me behind the counter, I would have just forked over a cup. I mean, it was my mistake, so I would be willing to pay for it, but I won't complain. I allow the woman behind the counter to ring me up again.)
Her: "Now, I charged you $5.53 for your sandwich and cookies, and the combo is...let's see....$6.60
Now, when she tells me this, I reach into my purse for my $1.07 to pay the difference.
Her (continued, pulling out an old receipt to do the math): Let me think here... I'll have to subtract it from this... (??) So, so that's....that's...that's...$1.10.
Now, I will admit, that I am not the world's greatest mathematician. I failed my high school trig exam (although I will contend to this day that it was because the teacher tested us on things he said wouldn't be on the test, and then accused us of not studying), and it takes me half a morning just to balance my checkbook, but this is pretty fundamental, even for the numerically challenged, like me. And while I will also admit that it was obvious that this woman behind the counter had a primary language other than English, I've never known numbers to change just because you don't speak the language your patron is speaking as fluently as she/he does. I mean, that's one of the beauties of math. Numbers don't change. 6 minus 5 is one. It has always been one, and it will always be one. 60 minus 53 is seven. It has always been seven, and it will always be seven. Therefor, 6.60 minus 5.53 is 1.07. It's really not that hard. It has always been that way, and it will always continue to be that way. And while I'm not one to begrudge anyone three cents, it's still three cents that I'd rather not part with (and besides, if she had been the one short, she would have demanded that I fork over the three pennies)
Me (slapping the extra $1.07 down on the counter): Actually, it's $1.07.
Her (a bewildered look on her face): It is? (a pause) I guess maybe it is....
Sigh. Some people. Incidentally, if you're interested in some additional math humor, please check out the link below.
http://www.yarnharlot.ca/blog/archives/2007/06/27/the_way_things_are.html
Her: "Oh, that's for the combo."
Me: "Yes, that's what I ordered."
Her: "Oh. I guess I'm going to have to ring you up again."
(Now, personally, if this were me behind the counter, I would have just forked over a cup. I mean, it was my mistake, so I would be willing to pay for it, but I won't complain. I allow the woman behind the counter to ring me up again.)
Her: "Now, I charged you $5.53 for your sandwich and cookies, and the combo is...let's see....$6.60
Now, when she tells me this, I reach into my purse for my $1.07 to pay the difference.
Her (continued, pulling out an old receipt to do the math): Let me think here... I'll have to subtract it from this... (??) So, so that's....that's...that's...$1.10.
Now, I will admit, that I am not the world's greatest mathematician. I failed my high school trig exam (although I will contend to this day that it was because the teacher tested us on things he said wouldn't be on the test, and then accused us of not studying), and it takes me half a morning just to balance my checkbook, but this is pretty fundamental, even for the numerically challenged, like me. And while I will also admit that it was obvious that this woman behind the counter had a primary language other than English, I've never known numbers to change just because you don't speak the language your patron is speaking as fluently as she/he does. I mean, that's one of the beauties of math. Numbers don't change. 6 minus 5 is one. It has always been one, and it will always be one. 60 minus 53 is seven. It has always been seven, and it will always be seven. Therefor, 6.60 minus 5.53 is 1.07. It's really not that hard. It has always been that way, and it will always continue to be that way. And while I'm not one to begrudge anyone three cents, it's still three cents that I'd rather not part with (and besides, if she had been the one short, she would have demanded that I fork over the three pennies)
Me (slapping the extra $1.07 down on the counter): Actually, it's $1.07.
Her (a bewildered look on her face): It is? (a pause) I guess maybe it is....
Sigh. Some people. Incidentally, if you're interested in some additional math humor, please check out the link below.
http://www.yarnharlot.ca/blog/archives/2007/06/27/the_way_things_are.html
Friday, July 13, 2007
New Books, Old Series
I am one of the few people on this planet who has not yet read any of the LOTR books. And I haven't seen any of the movies either, because, well, I tell myself that once I've read the books, I'll see the movies, but I don't want to see the movies before I've read the books. But at this point, I'm not sure when either one of them is going to happen.
People look at me strangely when I tell them this, but in all honesty, I really did try. When I was a senior in college (that was the year Return of the King was released in theatres), I sat down to read Fellowship of the Ring.
I read a couple chapters, and put it down. I just couldn't get into it. A few months later, I picked it up again and managed a few more chapters before setting it aside again. People tell me that I put it down just when it gets interesting, but I just haven't had any interest to pick it back up.
But at least I don't pretend that I know all there is to know about the trilogy. I dated this guy in college who contended that he was a big Harry Potter fan. And at first glance, I guess he was. He was familiar with many of the characters, believed that any book that got kids to read was fantastic, and found the charges against the books of witchcraft to be ridiculously ubsurd. He even gave me a book talking about religious symbolism in the books. That aside, at the time that we broke up, I don't know that he had once read a single one of the books. Everything he knew about the series, he knew from the movies.
Now, granted, at the time we were dating, The Order of the Phoenix was just about to come out, so the movies weren't that far behind the books. And I'm sure that, in the four plus years that have passed since we have gone our separate ways, he has probably read a few of the books. But still, really.
This is all prelude to my discovery this past weekend that there actually are human beings on this earth who have yet to read a few of the HP books. One of my coworkers has just begun reading the series with the intention of getting it read by the time the seventh book comes out. Hmmm.
BTW, does anyone have any cool ideas about what to do for a Harry Potter party for 8-12 year olds?
People look at me strangely when I tell them this, but in all honesty, I really did try. When I was a senior in college (that was the year Return of the King was released in theatres), I sat down to read Fellowship of the Ring.
I read a couple chapters, and put it down. I just couldn't get into it. A few months later, I picked it up again and managed a few more chapters before setting it aside again. People tell me that I put it down just when it gets interesting, but I just haven't had any interest to pick it back up.
But at least I don't pretend that I know all there is to know about the trilogy. I dated this guy in college who contended that he was a big Harry Potter fan. And at first glance, I guess he was. He was familiar with many of the characters, believed that any book that got kids to read was fantastic, and found the charges against the books of witchcraft to be ridiculously ubsurd. He even gave me a book talking about religious symbolism in the books. That aside, at the time that we broke up, I don't know that he had once read a single one of the books. Everything he knew about the series, he knew from the movies.
Now, granted, at the time we were dating, The Order of the Phoenix was just about to come out, so the movies weren't that far behind the books. And I'm sure that, in the four plus years that have passed since we have gone our separate ways, he has probably read a few of the books. But still, really.
This is all prelude to my discovery this past weekend that there actually are human beings on this earth who have yet to read a few of the HP books. One of my coworkers has just begun reading the series with the intention of getting it read by the time the seventh book comes out. Hmmm.
BTW, does anyone have any cool ideas about what to do for a Harry Potter party for 8-12 year olds?
Tuesday, July 10, 2007
Enablers
When I was in high school, we were studying the concept of alcohol addiction in health class, and the teacher discussed the idea of an "enabler." An enabler, according to him, was someone who defended and/or protected the alcoholic, like making excuses for him/her, and in the process sometimes encouraged the person to drink more.
I have come to the conclusion that alcoholism is not the only addiction that has enablers. Two days ago, I was at church, and a friend of mine came up to me and said, "If the guy at the yarn shop calls me today, would you like to go this afternoon?"
Dangerous words to a compulsive knitter. I mean, really, my stash is already taking over the living room, and I have so many projects on the needles that I'll be knitting for the rest of my life. I don't need an excuse to go to a yarn shop, and when I do, I always end up spending far more than I ever have the money for. And yet, when she called me later that day, of course I went. I mean, really. It's a yarn shop.
So we went, and I spent far too much money, mainly because, in the process of looking for something I can knit for my father, S picked up this variegated blue wool, held it up to my face and said, "Since you're not looking for yourself, I won't tell you how good you look with it." She then preceded to pull me over to a nearby mirror and show me. It was the perfect color. I was hooked. I, who had planned on getting some soft alpaca for my dad's sweater, and two skeins of soy yarn to make into socks, listened to S, who said, "Your father can wait. Get this for yourself," forgot completely about the alpaca and picked up the blue wool. It is now on two needles at home, and is going to be made into a ribbed sweater.
S is my enabler. She feeds my addiction for all things woolly, and I, of course, am helpless to defend myself against her. And she will remain my friend for life.
Oh, and I got the two skeins of soy for the socks, too.
I have come to the conclusion that alcoholism is not the only addiction that has enablers. Two days ago, I was at church, and a friend of mine came up to me and said, "If the guy at the yarn shop calls me today, would you like to go this afternoon?"
Dangerous words to a compulsive knitter. I mean, really, my stash is already taking over the living room, and I have so many projects on the needles that I'll be knitting for the rest of my life. I don't need an excuse to go to a yarn shop, and when I do, I always end up spending far more than I ever have the money for. And yet, when she called me later that day, of course I went. I mean, really. It's a yarn shop.
So we went, and I spent far too much money, mainly because, in the process of looking for something I can knit for my father, S picked up this variegated blue wool, held it up to my face and said, "Since you're not looking for yourself, I won't tell you how good you look with it." She then preceded to pull me over to a nearby mirror and show me. It was the perfect color. I was hooked. I, who had planned on getting some soft alpaca for my dad's sweater, and two skeins of soy yarn to make into socks, listened to S, who said, "Your father can wait. Get this for yourself," forgot completely about the alpaca and picked up the blue wool. It is now on two needles at home, and is going to be made into a ribbed sweater.
S is my enabler. She feeds my addiction for all things woolly, and I, of course, am helpless to defend myself against her. And she will remain my friend for life.
Oh, and I got the two skeins of soy for the socks, too.
My Things
There's been some questions, and it's been a while since the 23 Things started, so I thought I should probably explain to people who haven't been following what exactly I'm talking about. At work, there's been the initiative to introduce new technologies to all of us. It's called Learning 2.0, and it has 23 steps ("Things") for people to do. The premise is that we would do each step, and then blog about it to show that we actually did it (creating a blog was actually one of the steps). I completed all 23 of them back in April, but I've decided that since I did a lot of them just to say I did them, I'm going to go back and do some of them over again. This way, I can get more experience with them, and know what it is that some of my patrons are talking about when they come up and start throwing weird technology words at me :) And plus, it's fun!
If you are interested in learning more about these various and sundry steps, you can check out the link below (hopefully it works. copying and pasting might be necessary)
http://www.learningatlcpl.blogspot.com
If you are interested in learning more about these various and sundry steps, you can check out the link below (hopefully it works. copying and pasting might be necessary)
http://www.learningatlcpl.blogspot.com
Tuesday, July 03, 2007
A New Pattern
I bring in my knitting to work so I can work on it during my lunch break. The past two weeks, I finished two pairs of socks. Of course, I didn't use up all of my yarn, so I'm going to have to start another pair pretty soon. I just can't think of anything else that I can use with this particular yarn when I only have two skeins. But in the meantime, I've started with a sweater that will be a Christmas present to someone this year. (I'm only doing this because the needles required are larger and are not as horrendous for my carpal tunnel. The socks will return soon.)
Some of my coworkers think that the fact that I can string loops of yarn through other loops of yarn is just down right the coolest thing since sliced bread (although they would never think to ask me to teach them how to do it). The problem is that a few others also know how to knit (and are just as fiber-obsessed as I am, if not more so). One of them has given me a dilemma. She has this pattern for what she calls a "Probability Scarf." You take six different types of yarn, preferably in six different colors, and assign each one a number. Then, knit every row with a different color, rolling a die to find out which one you want to use. She says that this a great way to use up leftover yarn.
This is a problem for me. I had already thought that that was what socks were for. Now I have another way to use up my leftovers. Oh dear. Oh, the combinations I could come up with when doing a project like this...
Some of my coworkers think that the fact that I can string loops of yarn through other loops of yarn is just down right the coolest thing since sliced bread (although they would never think to ask me to teach them how to do it). The problem is that a few others also know how to knit (and are just as fiber-obsessed as I am, if not more so). One of them has given me a dilemma. She has this pattern for what she calls a "Probability Scarf." You take six different types of yarn, preferably in six different colors, and assign each one a number. Then, knit every row with a different color, rolling a die to find out which one you want to use. She says that this a great way to use up leftover yarn.
This is a problem for me. I had already thought that that was what socks were for. Now I have another way to use up my leftovers. Oh dear. Oh, the combinations I could come up with when doing a project like this...
Subscribe to:
Posts (Atom)