When lockdown started, it was still cool enough to wear sweaters. I alternated between wearing my tartan pajama pants with a fitted v-neck sweater and wearing leggings with a tunic. A frequent entry in my work-from-home loungewear rotation was a store-bought oversized sweater in pine green with a statement cable down the front; double moss stitch on the sides, back, and three-quarter sleeves; and a deep cowl neck. If it has any faults, it’s that it’s a loosely knit cotton with wrist-baring sleeves, so it’s not suited to particularly chilly days. I wanted a sweater with a similarly relaxed fit, but in wool with full-length sleeves.
Initially I was drawn to the idea of a sweatshirt sweater, and I even downloaded, swatched for, and started knitting Alicia Plummer’s Ease. After several attempts to achieve gauge—super important on a top-down raglan in the round—I prevailed and went on to knit most of the body before trying it on and HATING the way it looked on me. I don’t think there’s anything wrong with the pattern, nor can I say with certainty that it’s a bad silhouette for my personal fit preferences. I suspect the Malabrigo Rios wasn’t the ideal yarn choice: the 100% wool worsted yarn is a little too thick and a little too structured for the relaxed but not frumpy look I was going for, and it managed to skim too closely in front while bagging out too much in the back. To the frog pond it went.
For my second attempt, I turned to CustomFit, specifically the Catboat design. This was my first time picking a drop-shoulder instead of a set-in sleeve, and I agonized about getting the body and sleeve widths correct. After comparing the measurements on my only two drop-shoulder sweaters, I settled on an average (rather than relaxed) fit, a sleeve cast on of 8 inches, and a bicep width of 13.25 inches.
The central cable panel was borrowed from the #02 Cable-Panel Turtleneck design in Knit Simple Magazine’s Winter 2012/13 issue. Thanks go to my sister for giving me the magazine as a gift several years ago; I’m glad I could finally put it to good use!
I opted to add a purl row between the ribbing and the stockinette on the body and sleeves. This same detail shows up on my inspiration sweater, and I like how it define the separate sections, particularly since the cables don’t flow neatly out of the ribbing.
Overall I’m very happy with the fit of the sleeves, but I do wish the body had turned out longer, and I can’t help but feel like the back is a wee bit baggier than it really needs to be. I still don’t feel like I’ve exactly nailed my preferred fit with CustomFit, but I do feel like I’m getting closer each time, and in this case the length issue comes down to how the swatch was blocked (aggressively) versus how the sweater was blocked (much more gently).
I’m also on the fence about the neck. To be clear, I like a deep, snuggly cowl, but I’m annoyed that the instructions result in one that doesn’t fold at least in half. Despite multiple attempts, my picked up edge at the neckline isn’t as tidy as I’d like, and I’d prefer if the cowl gracefully concealed these sins. I have enough yarn leftover that I could un-pick the whole thing and try again, but I’m not sure I have it in me.
That said, this sweater is wonderfully warm and cozy—so much so that by the time I finished it I only got to wear it twice before it was too toasty for comfort. These photos were taken early in the morning in June, and it was a mad dash to snap as many as we could before my face melted off. It’s no secret that I hate summer and love autumn, and I’m already counting down to cooler weather.
P.S. I thought I’d try dressing like a crayon for this shoot. The look didn’t turn out half as chic as I’d imagined. Oh well.
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.
Given this sweater was on the needles for two years and two months, is it any surprise the photos sat on my phone for nine more months after that?
I kicked off this project right at the end of 2015, and I showed my progress on it at the beginning of June 2016. I’d just started on the sleeves when we experienced the basement flood that derailed the remainder of our summer, and that cemented 2016 as a terrible year for us. (There were many terrible things that happened that year. It was a bad year for everyone. But that was our personal tragedy.)
Eventually—I don’t remember when—I pulled the sleeves out of their abandoned project bag and finished knitting them. I’d ignored the CustomFit instructions for binding off the shoulders in favor of using short rows, as usual following the handy guides provided by TECHKnitting and Knitty. Seaming the shoulders was a cinch using a three-needle bind off.
Attempting to set in the sleeves (in the flat) revealed that I’d made a mistake on one of the sleeves and the cap wasn’t tall enough. I wish I could say where I’d gone wrong, but apparently I didn’t see fit to leave myself any explanatory notes about this. I ended up ripping out the sleeve cap to the underarm bind off and re-knitting, meticulously counting decreases on the second try.
Setting in the sleeves so that the stripes matched across the upper chest and the sleeve caps was a struggle and a half. I looked at many, many pictures of hand-knit and ready-to-wear tops with stripes to determine what properly matched stripes should look like. (I later discovered the Seamwork article “How to Match Stripes Like a Pro” also gives a clue.)
I concluded that a match stripe is typically located at the widest point on the chest, which generally corresponds to the lowest point of the armhole. You can place the match stripe at a higher point on the chest and sleeve, especially if you’re cutting and sewing a garment, but the armhole bind off provides a convenient matching point to work from on hand-knits. Importantly, you may be able to match more than one stripe above it, depending on the height of your stripes, but the closer you get to the top of the sleeve cap, the less likely the stripes are to match.
This should have been obvious to me, since I had specifically worked out what color stripe to begin the sleeves with precisely so my stripes would align at the armhole. But when it came time to seam, I got it in my head that I should be able to match all of the stripes on the sleeve cap to those on the body. That was an evening of self-induced crazy-making, let me tell you.
Once I finally stopped trying to achieve an impossible perfection in stripe-matching, setting in the sleeves and then sewing up the side and sleeve seams proceeded as usual—mattress stitch all the way!
I mentioned in my progress post that I was using one of TECHKnitter’s eight tricks for weaving in as you go. I chose the overcast method because it can be used for same-color or different-color joins in both flat and circular knitting (so versatile!) and because it’s recommended for fine yarn (no added bulk!). Unfortunately, I haven’t mastered the proper tension required to make this work well, because the tails are distorting the stitches they’re trapped against. Some stitches are pulled taller and other are squashed shorter, making it looks like there’s jog in the stripes. It’s not visible at a distance, but I can see it when I’m looking at the sweater up close and it bugs me (probably more than it should). My solution will be to only knit stripes where the unused yarn can be carried up the edge of the work. Or knit fewer striped garments. (AHHAHAHA yeah, right. Like I can stop myself.)
Even weaving in as I knit, I had an unforgivable number of ends to deal with. To stave off utter despair, I made myself weave in about half of them before I let myself pick up and knit the neckline. It helped. Somewhat. I still had to weave them in, but breaking the work up over a couple of evenings before and after the final knitting sprint did keep my twitching eye in check.
Now that I’ve not only come to the ends of the ends, but also worn the finished sweater a couple of times, I feel like I’ve formed an honest opinion of it.
I’m glad I knit a CustomFit design more or less as written. My previous CustomFit sweater involved heavy modification due to less-than-optimal yarn selection. This sweater has given me an opportunity to evaluate my measurements and what CustomFit thinks of as a close fit, including the placement of bust darts, the circumference of sleeves, and so on. Overall, I’m happy with the silhouette, and I’m less inclined to tinker with the pattern generator to try to get an even slimmer fit (which could result in unflattering straining or wrinkling).
When I wore it out for the first time, I was lukewarm about my yarn choice. I love Cascade Heritage Silk (blogged evidence here, additional proof on Ravelry) because it’s an affordably priced wool–silk blend that offers next-to-skin softness and a rainbow of colors. But the drape of the silk means that it can feel like it’s bagging out when I bend or sit and sagging over the course of the day. But after multiple wears, I’ve realized this is mostly in my head. While it’s true it doesn’t have the recovery of 100% wool, it doesn’t actually grow with wear or get sloppy-looking. For a lightweight sweater worn on its own or over a camisole, it’s a solid choice and I’d recommend it.
The turning point this sweater is named for was the realization that this sweater pairs exclusively with jeans and gym shoes. It doesn’t look like any of the other sweaters in my drawer; it doesn’t go with anything else in my closet. It clashes with my complexion, especially now that I’m a redhead.
The candy-colored yarns that were irresistible on the shelf seem strangely muted when knitted up together. (I know that’s hard to believe, looking at those photos.) Their vibrancy waned with my enthusiasm, and didn’t return even after I finished the project.
I remember when I got those yarns, from the now-closed Yarn Tree Studio in Raleigh. I bought them first and foremost because they looked good together, like they belonged together. Not because I wanted to wear them. Which is so silly, in hindsight, because I’d always intended to wear them—as a sweater, as a shawl, as a something. I only saw them as “pretty yarns,” and didn’t for a moment consider them as “the stuff to make clothes.”
I could defend my decision by saying I bought the yarn six months before I did Wardrobe Architect for the first time, but I find I’m not actually interested in justifying this sweater to myself. Instead, I feel like I’ve finally learned something that all of the meditations and mood boards didn’t drive home for me: just because something looks good on the rack/on the yarn or fabric shelf/on someone else, and just because I like how it looks, doesn’t mean I need to own it or wear it.
If my goal right now is to have more things in my closet that work together to create cohesive outfits, then I need to think about my buying and making in terms of projects that support that goal. There’s nothing wrong with owning styles that aren’t “flattering” or are one-of-a-kind, unless my goal is to have more garments in flattering colors and remixable shapes—then I’m just going out of my way to dilute my closet and increase the chance I’ll have “nothing to wear.”
I don’t like making mistakes, and the idea of learning from my failure has never captivated me—I’d much rather save time and heartache by learning from the mistakes other people have already made, if that’s an option. Despite reading and observing other people’s style journeys, it took personal experience to learn this particular lesson about making what I want to wear. It was a long walk, but I got there in the end.
I’ve already seen the payoff: during a trip to the New York City Garment District this summer, I went with a plan to look for specific fabrics intended for specific garments, all of which should work together in a variety of combinations. As soon as I catch up on my backlog of finished projects from the last few months, I’ll share my autumn/winter sewing plan, which is already in full swing!
I’m not surprised if you don’t—it made its first and only appearance all the way back in January. January. That was six months ago, friends. Egads. (So much for this being a year of knitting productivity…)
I stalled out sometime in April after I completed the back and started the front. Fingering-weight stockinette doesn’t make for particularly speedy knitting, but it’s mindless enough that I can work on it while watching TV and riding in the car. No, what strangled my enthusiasm for the project was not the pace, but the prospect of weaving in all. those. ends.
I hate weaving in ends. Every time I sat down and knit another stripe, I created two more ends to loom on the horizon. Just look at them, promising hours of tedium—and no doubt frustration—as I try to figure out where to put all of them without any stray colors cropping up where they don’t belong.
But, fueled by my Me-Made-May pledge (which came about in part because of this very project), I finally made a concerted effort to drag this project toward the finish line. Over the course of four weeks, I knocked out the front and started in on the first sleeve. (Interestingly, it doesn’t bother me to be on Sleeve Island, and I’ve yet to experience Second Sleeve Syndrome on a project.)
To help combat the tyranny of ends, I used one of TECHKnitter’s strategies for weaving in as I go on the front and the sleeve. It slows down the process of turning a row and joining a new color, but I’d like to think it’s preferable to the interminable and uncertain job of dealing with all the ends at, well, the end. But I’m withholding full judgment until I can seam everything and put it on—I don’t want to actually recommend this approach until I know that it won’t come apart or create unsightly lumps or bumps on the face of the fabric.
Meanwhile, I’m itching to move on to other projects. With consecutive days of 80-degree temperatures and 90-degree days on the horizon, I won’t be sporting this sweater any time soon—except for blog photos, of course. 😉