FO: Garden Party Dress and Mashion Cardigan


AKA Outfit Along 2015


AKA Third Time’s the Charm


AKA Better Late than Never


If I had actually sewn the dress I said I was going to sew, I probably would have finished on time instead of more than a month late. Then again, “finishing” may have consisted of wadding the dress up in disgust and refusing to think of it ever again. In the balance, satisfaction was clearly more important than punctuality.

The problem with the original dress plan is that I bought McCall’s M6887 solely as a result of peer pressure, in direct defiance of my own stated preferences and without regard for my previously purchased fabric. Don’t get me wrong—I like the pattern, and I think I actually will make it at some point. But in order to not hate the feel of the waist seam/fit-and-flare silhouette, I’m going to have to make it out of a stretch woven at least, or possibly even adapt it for a stable knit like ponte. My fabric was neither of those things, and I didn’t even make it as far as I muslin before I had a reality check and realized that I already didn’t like the road I was headed down.

After reviewing my recent haul of patterns, I briefly considered making McCall’s M7084, a shirtdress, instead. But it also has a waist seam, and I didn’t have enough fabric to do the fuller skirt, which felt like a must on a breezy summer dress. Instead, I settled on McCall’s M7156, which has princess seams and no waist seam. I’d been imagining it in a rayon challis or possibly a lightweight jersey, but decided that it should work with my fabric. And if it turned out a bust, I wasn’t any worse off than I would have been by sticking with the original plan.

I decided to skip the muslin on the grounds that there are a total of 8 seams on the dress, all designed to be sewn at 5/8″, which allowed plenty of leeway if I needed to take it in or let it out anywhere. After a recent knit dress project, those seams looked enormous! *cue the faintly ominous music of foreshadowing*

As I was handling my fabric in preparation for cutting, I confronted the fact that, no matter what my husband said, it was too lightweight to sew on its own and liable to be see-through in strong sunlight. So I quickly went out and purchased a white cotton sateen to use as an underlining. It came on a ridiculously wide bolt, something like 109″. I feel like I’ve heard somewhere that because sateen is a satin weave, it’s warmer than a plain weave, but you just can’t beat how smooth and lustrous it is. Besides, when it’s 95°F with an equally high humidity index, nothing is really going to feel cool, you know?

It’s a good thing it felt so lovely, because I struggled mightily to prep it for cutting. When I went to square the cut edges to the selvage, I expected it to behave like a plain weave and attempted to snip into the edge and tear it straight across, but instead it tore on a diagonal. (I tried to find a scientific explanation for this, but nothing at all came up in my searches. Is it because it’s more similar to a twill than a plain weave? If anyone can tell me what happened, I’d love to hear about it.) Since I couldn’t use the torn edge to position the grainline of the pattern pieces, and because the fabric was so wide, I went through an elaborate ritual that involved positioning the first piece relative to the selvage and then each subsequent piece according to the grainline of the piece that directly preceded it. It took forever, but I think I must have done it right, because everything hangs really nicely in the finished dress.


I started with a size 10 at the bust and graded out to a 14 at the waist and hip. I also took advantage of the For Petite line at the hip to shorten skirt. I cut everything on a single layer for accuracy, and I stole the pocket pieces from McCall’s M7084 since I’d cut them out when I though I was going to be making that pattern. I hand-basted all of the underlining pieces to my fashion fabric by hand, and followed the advice of this Threads article to account for turn-of-cloth. It took a couple of evenings in front of the TV to get it all done, but it was well worth the effort because I avoided any slipping or bunching during the actual sewing.

Since I didn’t make a muslin first, I machine basted all of the seams to check the fit. But because of the wavy nature of my hand basting and a couple of places where I had to staystitch per the instructions, I didn’t baste all of my seams at 5/8″ as I intended to sew them because I didn’t want to a) sew over any other temporary stitching or b) take out my hand-basting stitches before the actual, final stitching was done. I know, I know. This is a decision that seems completely absurd when I type it out now, but that was my thought process. I had plenty of excess fabric throughout with the narrower seams, so I reasoned that sewing them at the correct width would bring everything perfectly into line.


Rather than test this theory in a semi-rational way by sewing them at that distance, I decided to double-down on my questionable decision-making and proceeded to disassemble the basted dress and serge the vertical edges of each piece first. (I should have done this—with the knife disabled, if I was worried about accidentally shaving off too much fabric—before I basted everything together, but since I’m new to serger ownership I forget this and no commercial pattern I’ve ever encountered actually tells you to do it.) And, because my brain works in ways mysterious even to me, I elected to serge the edges at different widths. I know, I know. This doesn’t make any sense. Sure, avoiding a bulky seam on the princess seams makes sense, but do not ask me why I sewed the center front/center back seams and the side seams at different distances. I do not know. Also don’t ask me why I thought it was safe at this point to cut into the corners between the pocket bags and the side seams to allow me to press the seams open—I was just blindly following Lauren’s tutorial for adding pockets and conveniently forgot that she didn’t need to check the fit of her dress midway through.

Once I had the edges tidied, I sewed the dress up properly. Shock of shocks, it was too tight pretty much all over. Who would have guessed that barely estimating the changes you planned to make and then making said changes inconsistently would result in an outcome other than the one intended? Not me, apparently.

I had a bit of a cry about it, and then I unpicked all of the seams and sewed them as narrowly as I dared. I believe it was ¼” for all of the seams except the princess seams, which had already been serged together, but I can’t be sure, because I’d trimmed off different amounts while serging.

Lucky for me, this solved all of the fitting problems. But because I cut close to the original stitch line to free the pocket bags for pressing the seams, and then moved the seam outward, I ended up with holes above and below the pockets on the outside of the dress. To fix this, I carefully sewed a line of stitching that blended between the old and new seams to close the holes. The only downside was that my excellently constructed pockets are a little lumpy at the top and bottom and no longer completely hidden; they now have a tendency to peek out a bit, as you can see in a couple of the shots at the top. Otherwise I daresay they would have been perfect.

Once the fit was resolved, the rest was, if not exactly smooth sewing, at least more pleasant sewing. Taking advantage of the various feet for my machine was, I think, a contributing factor. The invisible zip, while still a little uneven at the top, is easily my best to date. (Well, as long as you ignore the fact that I sewed the seam to the dress and, while unpicking it, poked a hole through the underlining and fashion fabric. I was able salvage it by embroidering a red flower over the hole. Justin suggested I put a tiny flower on all of my makes. It would be sweet, I’ll admit, but I don’t think I have the patience for that.)


Since I underlined the whole dress, I elected to skip the facings in the pattern and use bias facings instead. I used self fabric for the neckline edge and stash quilting cotton for the hem. It was a great excuse buy Clover bias tape makers. (I love gadgets). I used this tutorial from Colette for making continuous bias tape. It took a couple of tries to get everything just so, but it was totally worth it and I don’t see myself ever buying pre-packaged bias tape again unless I’m in an absolute crunch. I used my overcasting foot to attach the bias tape, since I don’t have an edgestitching foot (yet) and it gives me basically the same result; I turned and sewed them down by hand using blind stitches. The bias facing along the neckline ended up narrower than intended, but it hasn’t popped free during wear, so I get to pretend that it was a deliberate and delicate touch rather than another miscalculation.

I attached the straps before the bias facings, but forgot to also check their length before I sewed the facings down, and they ended up too long and with exposed ends showing through in one or two spots. I solved the problem by pinching out the excess right where the straps meet the dress and then sewing them to themselves and to the bias facings with more hand-sewn blind stitches. You can’t tell from the outside, and you can honestly barely tell from the inside, either.


As I mentioned earlier, I took advantage of the For Petite line to shorten the skirt portion, but it still came out quite long so hacked off about 4 inches from the bottom.


I didn’t use the For Petite line to shorten the torso between the bust and waist because it seemed to align with my own measurements, but in hindsight I think it would have been a good idea to do that too. It would make a subtle but positive difference.


I think that’s everything for the construction and fit of the dress. There’s a lot less to say about the cardigan, although there are a few key things I’d like to share. First, I’m apparently such a tight knitter that I had to go up not one but two—TWO!—needle sizes to get gauge. I’m not sure I would have knit it quite that loosely if I’d had my way, but so far nothing has snagged so I can’t complain about it.


Second, and a thing I feel justified in complaining about, is the construction of the sleeve. Now, I’ll admit that this approach to a top-down set-in-sleeve is new to me, but it’s not the short rows that tripped me up (I’ve done them before on my Black Cherry Tart Cowl). No, it was picking up stitches that nearly drove me to madness. It’s not clearly spelled out in the pattern, but you should pick up a stitch in every other stitch, regardless of whether the edge is vertical, angled, or horizontal. That may not seem like a big deal, but one constant that every knitting resource agrees about is that you pick up stitches at a 1:1 ratio along horizontal edges. That’s what I tried doing on this cardigan, and it resulted in too many picked up stitches. I ripped this part out and re-did it several times, attempting to pick up fewer stitches everywhere else, before I realized what had to be done. I understand that designers shouldn’t be expected to hold the knitter’s hand every step of the way, but if you’re going to require the knitter to fly in the face of one of the few universally accepted pieces of wisdom, I’d appreciate it you’d say so up front.

That frustration aside, I’m not convinced about the fit/attractiveness of this set-in-sleeve construction method. Picking up every other stitch results in an almost hole-y pickup, especially around the underarm. The cap shaping seems okay, but I think the way the sleeve connects to the body at the underarm is causing the large wrinkle you see at the bust in every photo where I’ve bent my elbows away from my body.


Third, I found that the final cable cross happened in a weird place relative to the ribbing, so I adjusted by crossing later than specified to align with the pattern set by prior crosses. It’s possible this was my fault, since I had issues with the cables shifting too early (detailed here), but I thought it was worth mentioning.

I’m aware that it sounds like I’m being rather negative about the knitting, but I did truly enjoy it and I love the final result. It’s toasty warm even with the three-quarter sleeves, and it perfectly complements the dress. The buttons are easily my favorite part, though. I was going to use plain green plastic buttons, but at the last minute chose these wood-look ones instead and really love have they contrast the yarn but tie into the natural theme of natural fibers and flowers.

Oh, and in case you’re wondering, the name Mashion comes from the name of the pattern, Marion, and the fact that Justin and I embarked on a journey to watch all of M*A*S*H from the beginning around the time I started knitting, and much of it was accomplished during the first couple of seasons. Plus it’s green, which is ubiquitous on a show about Army life.

Overall, I’m so glad to have participated in the Outfit Along and so happy to have two handmade items that I know I’ll wear because I know I can wear them with each other if nothing else.

I’m also really happy to be following along with Gillian’s Better Pictures Project, which is aimed at taking better blog photos even if you don’t have a fancy camera or fancy training. This month’s prompt was to step away from the blank wall and take pictures out and about. This is something I love to do anyway, so it wasn’t out of my comfort zone to visit the Raleigh Rose Garden for these photos. And, in an effort to increase the number of usable photos that came out of the shoot, I had Justin take a ton. People, he took 187 photos. Is that not crazy? Here are several more that I liked:






And tied for absolute favorite:



Fixing a (Knitted) Cable

When last we left the Outfit Along, I was lamenting the fact that I made the cable on either side of the front opening travel too soon, which meant that it wasn’t in position to line up with the pattern on the bottom band. I could have modified the pattern on the bottom band—in fact I did try it, but I didn’t care for how it looked—but in my heart of hearts I knew it would bother me. So I set out to fix it.

Since my cable was not crossed in the wrong direction, instructions for duplicating stitching over it or (egads!) cutting into the knitting to reverse the crossing were not going to solve my problem. Instead, I learned that you treat it like any other mistake: isolate the offending stitches, drop them off the needles, and then gently tug free the strand of running yarn on each row until you get down to problem row. Correct the mistake(s), then use your knitting needles to re-knit (or a crochet hook to latch up) the stitches until you’re back on the working row.

I had very much hoped to photograph my steps, but the lighting just wasn’t cooperating. Instead, may I recommend Yarn Harlot’s and Twist Collective’s handy photo tutorials? I referenced both and would definitely recommend them if you find yourself in the same boat as me.

To their excellent advice, I would add the following four suggestions:

  1. Thread a DPN through the target row of the isolated stitches. Don’t worry if you don’t catch all of them, or you pick up the wrong arm of a stitch. Once you’ve unraveled most of the rows and are close to the row with the mistake, you can use one of your knitting needles to slip stitches off and on the DPN until all of them are accounted for and oriented correctly. Keeping them on a holder stops additional rows from unraveling, which is more common for tight knitters like me, and which is the #1 cause of knitting-induced panic around here. No need to make the fix more complicated or stressful than it needs to be, right?
  2. Count each loose strand of running yarn as you unravel it to make sure you know what row you’re on. Cables can be difficult to read, especially if they haven’t been blocked yet and are all scrunched up under their own tension. I had a pretty good idea about where I went wrong in the cable chart, but I made sure to count each row I unraveled to be sure I landed on the correct row for my fix. It also allowed me to confirm that the fix was happening on the side of the knitting that I intended (in this case, the public side) and that when I went to reknit I knew exactly where to pick up the pattern in the chart. The last thing I wanted was to go through all of this trouble only to be off by one row the whole way through and have to do it all over again.
  3. Use a smaller needle to hold the stitches to be worked; use the needle size needed to get gauge to work them. Even though the section of sweater I was dealing with was 9 stitches wide and worked on US 10 needles, it was tight and difficult to maneuver. I was concerned that in every row, the first few reknit stitches would be correctly sized and tensioned, but the last few would end up too tight and too small as I struggled to catch the dwindling span of the running yarn for the row. To mitigate this issue, I put the stitches to be worked on a US 8 DPN, and I did the actual knitting with a US 10 DPN. This did mean that each time I successfully reknit a row, I had to transfer the new stitches from the US 10 to a US 8 to work the next row, but the extra time was worth it because the reknit stitches are a pretty close match to the surrounding stitches that were left untouched. If you use interchangeable circulars, you could put a different sized tip on each end of a longish cord and eliminate the transfer step.
  4. Use a cable needle or DPN to rearrange the stitches for the cable cross, and then knit the entire row. If you try to knit part of the row, move stitches to a cable needle for the cable cross, knit half the cable, transfer the stitches back and knit them (or knit directly from the cable needle), and knit the remainder of the row, you’re in for a struggle. The cross is liable to be tight to the point of straining, the stitches will be scrunched up and difficult to work, and there’s a good chance you’ll end up stabbing yourself. Again, it takes a little extra time to rearrange things, but the payoff in appearance (and painlessness) is worth it.

The process was time-consuming, but the result was deeply satisfying: the cables are now correct, and it’s nearly impossible to tell that they were ever wrong; any remaining vagaries in tension/stitch size can be resolved during blocking. Best of all, by being patient and following the four steps above, I was able to avoid any weeping, gnashing of teeth, or questionable language. (I also wasn’t tempted to turn to booze and/or ice cream, which most certainly would not have improved the outcome.)

Have you ever had to fix a mistake in a cable? How did it go? Do you have any tips to add?

Wardrobe Architect Week 13: Downloadable Planning Worksheet

Since this week’s “assignment” was originally just a giveaway with a bonus (free!) one-page downloadable worksheet to plan sewing projects, I decided to print one off and use it to jot down my intentions for my OAL 2015 dress. I’ve gathered most of the things I need already (although I realized I’ll probably need to pick up some lightweight sew-in interfacing, since I’m not sure what I have lurking in my stash at the moment), but it gave me a chance to look over the pattern and anticipate the next steps, like what size I intend to cut and how I want to deal with seams and such. Plus, I got a chance to bust out some long-neglected color pencils and do a little drawing.


Cute, yeah? Figuring out what size I want to sew was the hardest part, because the back of the pattern envelope lists the finished measurements for the bust and hip only, and it’s the waist that usually trips me up. I had to carefully unfold the tissue so that I could find the marking for the finished waist size. With any luck, the largest size in the envelope should be big enough. But I’m planning to muslin at least the bodice before I cut into my fashion fabric, just to be sure. I have Friday off from work, so I’m going to try to do the bulk of the sewing then. Wish me luck!

Outfit Along 2015

As my Wardrobe Architect exercises have undoubtedly made abundantly clear, I haven’t been so good about buying or making clothes that work together over the last few years…or ever. Like a lot of people, I find a thing I need or a thing I like (preferably something that ticks both boxes) and go for it, without really considering if I can wear it more than one way. Sometimes that’s okay, but mostly it makes me one of those people that has plenty of clothing and yet has “nothing to wear.”

So when Lauren Taylor of Lladybird announced that she and Andi Satterlund of Untangling Knots would be teaming up again to host the 2015 Outfit Along, I was all over it like dog hair on a date night dress. What’s an outfit along? It’s a friendly challenge where you commit to sewing a garment and knitting a garment that are designed to be worn together. Lauren and Andi have picked a dress pattern and a cropped cardigan pattern, respectively, and throughout June and July they’ll be providing construction tips on their blogs. Participants can post their completed garments in the OAL 2015 Finished Outfits thread in the Untangling Knots group on Ravelry; garments completed by the July 31 deadline are eligible for nifty prizes and the adulation of their peers (but mostly prizes :-)).

The official sewing pattern is McCall’s M6887, which I picked up in a recent pattern haul. I’m planning to sew View A, which has an adorable back cut-out. 2015-06-20_1_Dress-Supplies

The fabric, which I believe is a cotton lawn, is something I picked up several months ago from JoAnn intending to make the Simplicity 1419, the Lisette Round Trip Dress. Sadly, that style is just not for me, as several yards of wadded up muslin will attest. Luckily, it’s enough fabric for the OAL pattern, and it’s a good match for my spring/summer capsule palette. I’d like to think I already had a burgeoning sense of my style preferences, but the reality is that it’s more of a happy accident, as I really just wanted something bright and cheery while we were still in the midst of freezing temps.

The official knitting pattern is Vianne, a cropped cardigan with a mesh back panel. It didn’t really speak to me, and I can’t help but think the mesh would look a little strange with the back cut-out. So I decided to substitute Marion, one of Andi’s other patterns.


Not too shabby, eh? I started knitting the first week of June, and I’m already to the point where I can start knitting the bottom band. It’s amazing how quickly something flies off the needles when said needles are US 10s. (The pattern calls for US 8s, which is already at the upper end of the range usually given for worsted weight. I went up a needle size preemptively when I swatched, but it wasn’t enough, so I went up again to get gauge.)

Unfortunately, I discovered an error in the final cable repeat on both sides: I made the cable travel too soon, so it isn’t positioned correctly to flow neatly into the bottom band. I was going to just leave the cable and slightly modify the band pattern instead, but after sleeping on it I realized that it’s going to bug me even if no one else can see it. I’m going to attempt to correct the problem without ripping out all of the rows (about 12), but if I completely flub, that will be my only option. Wish me luck!

P.S. The background of those photos is a sneak-peak at another project, a finished one, that I’ll share tomorrow.