While I was visiting my family for Thanksgiving, I had the experience of witnessing a time-worn idiom come to life, when my mom approached me with hat in hand to ask for my knitting expertise. The very literal hat in question was a light grey, slouchy, slightly fuzzy beanie with alternating bands of plain and textured knitting, the crown of which had started to come undone. She had picked up the hat to wear when walking the dog, and she admitted that though it was nothing particularly special, she would nevertheless be sad to lose it to unraveling. She asked if I would be willing to take it home and try to repair it, which I readily agreed to do.
Fortunately for the hat (and my nerves), once I carefully unpicked the tangle of loops at the top of the hat, I discovered the situation was not as dire as I feared. The crown had not been cinched shut with the tail of the working yarn, but had instead been secured with a separate strand of yarn, and it was this strand only that had broken. None of the yarn used in the knitting itself was damaged—no snags or severed plies to fuss with—which meant it was a relatively simple task to latch up the few dropped stitches and then close the top of the hat with a strand of stash yarn in a similar weight and color.
Since I knew I’d see my parents again at Christmastime, I had the hat in my possession for a couple of weeks, during which time it occurred to me that I had the power to do more than simply keep a humble accessory from meeting an untimely demise: I could, in fact, template the cherished item and ensure that it lived on through an infinite number of iterations, should the owner so desire. Or, at the very least, I could create a copy, doubling my mom’s sartorial choices and prolonging the life of the original hat. Which, as far as I’m concerned, is a close second behind hat-based immortality.
To make my copy, I started by taking some flat measurements of the height from brim to crown, the height of the ribbing, and the height of a pattern repeat. The stockinette and reverse stockinette portions were easy to identify, but I had a slightly harder time with the other texture, which sort of resembles ribbing if the knits were squatter and more pronounced and there were no purls between them. After some searching and comparison, I came to the conclusion that it was probably fisherman’s rib. Whereas the original hat had been worked flat and then seamed, I think seamless hats are one of the ways handknitting distinguishes itself as superior to machine knitting, so I found instructions for knitting fisherman’s rib in the round and was off.
The yarn is Malabrigo Rios; the colorway is Natural. The recipe for this hat can be found on my Ravelry project page. Contrary to the care note I sent my mom (hi Mom!), it is, in fact, machine washable, so long as it’s placed in a garment bag on a cold, gentle cycle. It still has to be laid flat to dry, but being wool, it doesn’t need to be washed all that often. I enjoyed working with the yarn so much that I used it again for another hat and also a sweater—more on them soon.
I wish I’d had the common sense to take a photo of the original so I could show you both hats side-by-side and you could be impressed by what a good match they are, but I think we all know by now that that kind of forethought isn’t my specialty. Just picture the hat above in light grey and a little fuzzier. Pretty similar, eh?
On the opposite end of the spectrum from my Pumpkin Pie sweater is this monster, which did not so much inspire introspection into the nature of craft as it did provoke spates of cursing and self-condemnation.
The pattern in question is Casapinka’s Magical Thinking, the Local Yarn Shawl of 2019. As in 2018, I found it difficult to resist the lure of a “free” pattern in support of my beloved LYS Warm ‘n Fuzzy. I’ve put “free” in quotation marks because you receive a download code for the shawl only when you purchase suitable yarn for the project on Local Yarn Store Day (the last Saturday in April).
That’s where the trouble began.
Don’t get me wrong—I don’t begrudge my LYS one cent of the money I’ve paid for yarn, needles, notions, or knitting swag over the years. But I have no shortage of sock yarn shawls already, and within the framework of having no particular need for another sock yarn shawl, I definitely spent more money than I should have. Whereas my 2018 Local Yarn Shawl required two skeins of fingering weight, this year’s offering demanded three—three! As you might imagine, these hand-dyed beauties—a semi-solid, a tonal, and a speckle—came with a premium price tag. I do very much love the colors, though, both individually and together. That’s how they get you.
Everything would have been peachy if all I’d needed to do was assuage a bit of guilt for indulging in luxury yarn (a trivial inconvenience for the veteran knitter). At some point, no doubt around the time I had an armload of yarns I was auditioning for my next neck accessory, it dawned on me that I had, in fact, been suckered into yetanotherstripedproject. (If you’re wondering why three out of the four links lead to apparently solid-colored knits, it’s because I had to alternate skeins to manage dye lots/color transitions, which works the same as knitting contrasting color stripes).
“It’s fine,” I told myself. “It’s knit in the round. I can carry the unused yarn inside the work.”
This is…not really the case. There are a handful of places where you can carry the yarn, true, but it’s not possible to carry all three yarns all the way through from beginning to end. My sense of betrayal and disappointment (mostly with myself, to be clear) when I realized there were actually going to be a lot of ends to weave in did not contribute to an auspicious start to the knitting portion of this endeavor.
The pattern instructions were, quite frankly, not my favorite. For starters, there seems to be no consistent logic to when the first stitch of the round is slipped. It’s supposed to prevent a jog in the stripes, but slipping the first stitch isn’t indicated for every color change, nor is it omitted when the color stays the same. There’s probably some esoteric bit of stripe-knitting theory I’ve failed to grasp here, and that’s hardly the designer’s fault. Regardless, I struggled with the transition between the end of one round and the beginning of the next looking like a gappy, jagged mess the whole time I was knitting, even with the slipped stitches.
Then, there’s the explanation of the increase rounds. In theory economical but in presentation inelegant, the increase rounds caused more than a few minutes of puzzling on my end. “Do them as you do the first increase round” it says in bold, and “Note that increase rounds are defined in bold, above” it says, but then doesn’t specify whether it means the first increase round in each section (nope) or in the whole piece (yep, it’s this one). The stitch instructions for this foundational increase round are not themselves bolded for convenience, which is baffling when you consider they’re referenced throughout the remaining 6 pages of the pattern.
Eventually the entire thing became so big and unwieldy that not even novel changes in the texture held my interest; eventually “one more round” was not the breathless whisper of anticipation but the ragged mantra of someone who just wants the thing to end.
And, wonder of wonders, it finally did. The issues I had with the beginning of round transition disappeared with blocking, and, as is so often the case, the memory of my agitation during the making-up has dulled with time. I may not have loved a single minute of the process, but I’m pretty fond of the finished product—fond enough that I wore this exact outfit for my birthday party, back on a bitterly cold night in November. (I was supposed to wear a dress I’d made myself, but that’s a story for another day…)
Much of TECHknitter’s writing deals with the mechanics of knitting, like why a stockinette edge curls (and why adding a border doesn’t really fix the problem), and how to use that knowledge to your advantage. But sprinkled throughout are bits of knitting philosophy, such as when to choose an excellent but fiddly solution and when to settle for a pretty good one. Very occasionally—only a handful of times in a decade—TECHknitter treats the reader to a pure philosophical refection on the craft.
The one that’s stuck with me, that continues to thread itself through more and more of my thinking, is the work-to-glory ratio. Originally posited by TECHknitter’s friend Carol, the work-to-glory ratio is the relationship between the amount of effort that goes into a project and the degree to which the result is impressive or satisfying. A project that appears difficult but was in fact easy to knit has a good work-to-glory ratio, whereas a project that was tedious or hard and turns out indistinguishable from something machine-made has a bad work-to-glory ratio.
As TECHknitter is quick to point out, there are of course plenty of projects that are both challenging and gratifying: some projects are rewarding precisely because of the time and effort that went into their making. A practical project in a workhorse yarn with a familiar pattern might turn out precisely as useful as the knitter intended. For TECHknitter, the work-to-glory ratio is more an observable phenomenon than a guiding principle.
The orange sweater above, a CustomFit version of Amy Herzog’s Foyle’s Pullover, has proven to have a pretty good work-to-glory ratio. The allover lace on the front is an easy-to-read and memorize six-row repeat where the wrong-side rows are all purled, and it’s a great design to practice decreasing in pattern (though no specific instructions are given for this, and the source I was going to recommend is no longer available online). Meanwhile, the back and sleeves are simple stockinette, yet these large swaths of plain stitching somehow recede into the background so as not to draw attention to the fact that two-thirds of the sweater are mindless TV knitting.
While to my eye there’s nothing really outstanding about this pullover, everyone who’s seen me wear it has been impressed by its handmade origins and convinced that it must have been quite a bit of work to produce. Oh no, I think, it wasn’t nearly as fraught re-knitting every piece of this sweater to get a mediocre fit, or as mind-meltingly tedious as dealing with the kajillion ends on this one to make it wearable. Both of those projects took far more time and mental energy, but you’d never know it by looking at them.
(In case anyone thinks I’m underwhelmed by the results here, let me assure you that I’m very happy with the outcome and feel it’s my best CustomFit sweater yet.)
The work-to-glory ratio as a framework for thinking about things that take work—even if they’re not thought of as work, as a task or a job—has slowly crept into other areas of my life. Increasingly I’ve been thinking about it in the context of friendships, and I’ve been struck by how even a healthy friendship can at times have a pretty poor work-to-glory ratio.
The daily work of being friends, of nurturing a relationship, can involve so many small acts to affirm, question, encourage, and comfort. Making time to call, remembering milestones, knowing a person’s favorite treat or pet peeves—these are all part of the skill of being a friend, a skill that must be learned and can be cultivated.
But it’s also work that can go unrewarded. A deliberate effort to ask about something a friend is working on might lead to a dead-end in conversation; a genuine desire to check up on their wellbeing might go completely unanswered or unacknowledged. Frequent small touches become shallow interactions, which can start to feel like more of a rote exercise than the practice of making a genuine human connection.
In my lowest moments, I wonder if the work isn’t worth the paltry sum of glory.
And yet TECHknitter offers another way of thinking about this too: work as product plus process. The idea that the value of a thing lies in the thing itself, and also in all of the moments that went into making the thing added up. A handknit sock is no longer just a sock: it’s an act of care, patiently created to be something functional and comfortable and beautiful that someone can use and enjoy every day. The knitter knows it, and so does the wearer, and that knowing is as much as part of the joy as the sock itself.
The time, place, and emotional space the knitter was in while they knit are also part of that sock, whether the wearer knows it or not. They become folded into the process part of the equation, bringing further dimensions to that sock’s intangible value.
But beyond even these things are the very act of making itself: the friction of yarn sliding over the tensioning finger, the clicking of needles in motion, the rhythm of forming stitches and turning the work. Watching the balance of yarn change, the unraveled cake collapsing as the yarn is raveled back into a slowly lengthening sock. Choosing to see and hear and feel the process of yarn becoming a sock when it would be far faster and simpler to buy socks at the store.
How much better to think of friendships as product plus process! To imagine each moment of connection, no matter how seemingly trivial, as another stitch in the knitting—by itself practically inconsequential, but in aggregate absolutely essential. To treat the intention behind each small act of kindness as equal to the outcome of the act in importance. The goodness of a friendship is thus measured not only in how meaningful are the conversations or how memorable the events, but also in how much love and concern motivated every effort to have those moments, even when those efforts appear to fail.
The work of friendship and the rewards of friendship are not two sides of an equation to be weighed against each other: a friendship is the sum of the work and the rewards, the product and the process added up and divided between friends.
Although these photos look more or less seasonable—heavy coat, thick scarf, let’s just ignore those exposed ankles—they were taken on the last cold day of spring in 2019. In fact, by the time we were finished shooting, I was starting to get a little steamy under all that wool.
If you think roughly nine months between cast off and debut is a long time, you’ll be positively boggled to know that this pattern, Gateway by Glenna C., is the oldest surviving entry in my Ravelry favorites. Ravelry very helpfully notes that I added it on March 24, 2012, meaning it had been marinating in the back of my brain for almost 7 years by the time I finally committed yarn and needles to it.
It would be rather convenient if I could chalk up that long wait to the difficulty of the pattern or the cost of the yarn, but the lace is easy to read and Quince & Co.’s 100% wool Lark is quite economically priced.
This was my first time knitting with a Quince & Co. yarn, which is another head-scratcher, since it was the first small-scale (at the time, anyway) yarn company I learned about as I was starting to branch out beyond craft store offerings and widely available commercial brands like Cascade and Berroco. While Lark isn’t as snuggly as a superwash merino, it’s smooth and plump and not at all unpleasant to knit with. (I’ve got nearly 1,000 yards of it under my fingers to prove it.)
The color, Gingerbread, continues my simmering love affair with dark orange and orange-y brown yarns (Andraste, Oxidation, More of a Bourbon Girl, and an as-yet-unblogged sweater). What can I say—I’m enchanted by the idea of having knits in the same color family as my hair. I’m a simple creature like that. (In every other way, however…)
On the subject of seasonally appropriate and thematically related things, I made gingerbread from scratch yesterday and it is amazing.
Firstly, it’s proper gingerbread, not ginger cookie of the sort used to make gingerbread folk or gingerbread houses—though to be very clear, I also love soft gingerbread cookies and crisp gingersnaps. A lot.
Secondly, it’s dark and molasses-y and not overly sweet, with the added benefit of filling the house with the sweet and spicy smell of gingery delight for the hour-long bake time. I’ve already had it as both dessert and breakfast, and there’s at least half a pan left to enjoy before the festive season is over. I highly recommend it.
On that note, I’m off to soak up a little more holiday cheer before I have return to my usual routine. Merry Christmas all!
A quick entry on an exceedingly quick project. How quick? More than a weekend but less than a month. I know that I started it after I finished my Stone’s Throw cardigan, but before I started my next project at the beginning of February.
Normally I print out patterns to take notes on, but this is such a simple design that I downloaded the pattern to my phone and referenced it only a handful of times to make sure I got the proportions of ribbing and body correct and decreased the crown in a pleasing manner.
The pattern is Rocky Ridge Hat by Knox Mountain Knit Co., and it’s available as a free Ravelry download. The yarn is Swans Island Washable Wool Collection DK, the leftovers from my cardigan. You can view my Ravelry notes here, but there’s precious little to say about it. I knit the adult medium size as written, including the length.
Can you believe this is my eleventh hat, but the first one with a pom pom? I know, me neither! When it comes to hats, I’m a fan of the whole genre, and I have no qualms about poms. In fact, I’m rather fond of them, and encourage them for others. But somehow none of my many beanies ended up with a dapper topper. Really, it was long overdue, and I’m glad the shortcoming was rectified.
This is also the first hat I’ve made that could be described as even remotely slouchy. Between you and me, I think it could have been slouchier, but the extra ease would have come at the expense of the pom pom, and that was a sacrifice I just wasn’t willing to make.
I foresee many more slouchy and/or be-pommed hats in my future. Until then, enjoy this ridiculous picture of my pom pom hype.