Category Archives: Rogue Cardigan


I’m about an inch up the pocket. Everything’s going well. Not enough progress to photograph, so I thought I’d answer some questions.

Ever establish a second layer by knitting into the front and back of each stitch?

Judy asks if I’ve ever done this. The idea is that on the foundation row, one knits into the front and back of each stitch, then goes back and separates the stitches onto two needles.

I haven’t. I stumbled across the two-strand method early on, and haven’t tried other methods. I’m a bit skeptical of this one though. I suspect that you’d get a line of stressed, slightly open stitches, almost eyelet-like at the base of the two layer part. I don’t have that problem when I knit two strands.

Is the discontinuity in the Little Dragon Skin pattern noticeable?

Yes, I’d have to say it is, but I’m looking for it. I considered ripping back and starting again with the original (and more elegant) Walker version, but I decided that to do so would be being too picky. Target Daughter is pleased, so I’ll keep going.

How do you know the pocket placement is correct because you’re doing it differently than the pattern says?

First off, my placement is within 10% of the original. I doubt the difference will make a major change in the look. Some minor change, yes, but not enough to kill the piece. That I’m able to plow ahead making changes like this is testament to the thoroughness of the explanations and clear logic of the pattern. I can read it and understand the principles underlying why something is being done. If I know why, I also can get a grip on roughly how far I can bend that why, before something breaks.

In this case the pocket is a self contained module. The original presents a stitch count at the pocket’s base, a pattern of decreases that yield a gracefully curved pocket edge, and a final stitch count after the pocket flap is completed. My pocket may have been started on a different number of stitches, but I will retain the slope and pattern of the original decreases, and end up eliminating the same number of stitches as the original. When the time comes to fuse in my left and right pocket, I’ll count in the number of stitches from the center front cardigan opening, mark the body stitch that corresponds to the endmost pocket flap stitch, and fuse accordingly.

Your texture pattern has decreases and increases on it. How are you working that in with the pocket shaping?

This pattern maintains its stitch count on each row. If I eliminate the opportunity for one of those increases to be made, I either have to eliminate its partner decrease, or fudge a substitute increase where it will be inconspicuous. Fudging the increase would mean changing the slope of the pocket shaping, so for the most part, I’m killing decreases in concert with the eliminated increases.

This pattern is pretty easy to eyeball. There are 10 stitches in a half-repeat. Each half of that includes one increase and one decrease. I started the pocket at one of the verticals. I "ate" five stitches by designating one as an edge stitch, and then working k1b, p1, k1b, p1 for my pocket edge ribbing. The insidemost purl is the column on which I am working all the pocket decreases. Since the pocket edge has consumed five stitches, the next five constitute a full increase/decrease segment of my pattern. I worked them until the pocket edge’s march to the garment’s center intruded on the decrease. After that I worked the remainder of that five-stitch quarter-repeat unit in plain stockinette.

Do you always screw around with a pattern instead of knitting it as written?

It depends on what you mean by "screw around." While it’s true I don’t often work from "boughten" patterns, I don’t avoid them on principle. If I see one I really like, I’ll do it. Some I do verbatim. My last several lace projects were like this. I’m still getting the feel of lace, and aside from several counterpane motifs and a couple of simple scarves, I haven’t plunged into designing my own yet.

I do tend to play with garment patterns more. Sometimes I do them as written. More often I play with yarn substitutions, which may or may not bring gauge adjustments, too. I’m also a bit on the tall side of large, so many patterns need some alteration before I’m satisfied with the fit. Other times I’ll like most but not all of a given design, and adjust some of the parts, even swapping in different textures, collar lines, or details.

I admit the multiple injustices I’m doing to Rogue are rather extreme, even for me. The design though is robust enough to survive my abuse.

Will you send me the pattern?


There are few ways more calculated to set me off on an anti-copyright infringement tirade than receiving this question. The pattern is a good one. The price is very reasonable, especially considering the vast amount of hand-holding it contains. It’s easy to find and buy. Heaven knows I’ve provided enough links to it, and it’s so widely talked about that even the most rudimentary searches turn it up.

The author deserves recompense for her time and effort. Copying patterns in this manner is piracy. Beyond just being immoral, it’s flat out illegal.

Be warned. I am considering posting the names and addresses of everyone who makes this request from now on, so that their lack of moral integrity and basic ethics will be made known to the on-line community at large.

End tirade.


As you can see in today’s progress photo, I’ve finished fusing the hem. I’m quite pleased with the result. You can also see that my bottom edge is in fact scalloped, and that the scallops stand up nicely without cupping or curling, and that the hem facing accommodated their shape without any special adjustments.

I’m now up to Row #4 – the row on which one is supposed to begin the kangaroo style pocket. I have to admit that I’m going to depart from the pattern and cheat a little here. I know the pattern calls for working just the pocket front, then going back and picking up stitches at its base to provide the foundation for the back side of the pocket. After both are worked to the same depth, the pocket front and back are fused, and the knitter continues on to work the rest of the body.

A while back I did several Wonderful Wallaby sweaters for assorted nieces and nephews. It’s a raglan pullover that also has a kangaroo pocket in front. Those directions called for something similar – knitting a bunch, then picking up stitches and knitting a second layer (in that case for the pocket front) then fusing the two layers together. I found the picking up to be tedious at best, so I came up with an alternative lazy person’s method.

On the row where the second layer is introduced, I knit with two strands of yarn. Then I take two needles and stitch by stitch carefully slip one loop of each stitch to the needle I will use for my pocket front, and the other loop onto one from which I will end up transferring the stitches back to my original body needle (on small things, I just use the other end of the body circ for this, then shunt the stitches back to the correct "ready to knit" orientation). The yellow arrow indicates the circ that’s carrying just the pocket front stitches. The pink arrow shows the circ that’s carrying the full body.

In this case, because of the split cardigan front, I’ve had to start two more yarn balls – one for each half of the pocket. Again, in order to accommodate the zipper tape, I didn’t work the two stitch thing all the way to the cardigan opening edge. Instead I cast on four "free" stitches left and right for the inside the pocket piece, leaving the outside presentation side smooth and uninterrupted. I am now ready to do the sloped side pocket itself, on this confusingly presented second circ, now hanging off the front of my work.

As for where I introduced the pocket – I fudged. My chosen stitch pattern has strong verticals. I’ve moved the pocket opening over a few stitches so that it lines up with one of those verticals. Since it looks like ten stitches are decreased away during production of the pocket, and my verticals are present every ten stitches, I think I’ll be able to be similarly congruent when I finally work up to the fusing row.

One last note – like the Wallaby, the pocket edge appears to be in garter stitch. Frankly I am not a big fan of garter, and I don’t think it will complement the already busy surface patterning of my mutant Rogue. I’m thinking of doing four stitches left and right in twisted stitch ribbing instead. I’ll play with that idea a bit and see if it works. If not – it’s rip-back time again, and I’ll revert to the original garter pocket edging.


Here I am again, on Row #10. For me with my non-pattern-compliant stitch and row gauge, that’s the row on which the depth of the hem facing is the same as the depth of the public side. It’s time to unite the hem facing and the body into one unit, eliminating the need to do this bit of finishing seamwork later.

I’ve unzipped the chain of the provisional cast-on and put the newly freed stitches onto the smaller diameter circ I used to work the facing (the gray needle). The work is folded along the turning ridge, and I’m holding it with the hem facing showing. You can see the bit of ended off facing I mentioned yesterday. If you squint at the spot indicated by the arrow you can just make out the little "plateau" of the four terminated stitches. Instead of doing an orthodox bind off, I used a crochet hook to loop the stitches together, looping the last one around the base of the fifth stitch in from the end. While this is a legitimate bind off technique it is rarely used, as it makes an extremely tight, unstretchy edge. (Some buttonholes use this trick for extra firmness). Besides tightness the other reason for doing the bind-off this way was to eliminate the need for extra ends. I’ve got only one working strand here. If I were to do a normal bind-off on the four end stitches, I’d need to introduce a strand with which to do it.

In the photo above, my right hand needle holds four purled stitches of the body, and three stitches in which I’ve purled together a body and a hem facing stitch. (I’ve stretched the thing as much as possible for clarity).

Here I am making one of those purl togethers. The facing is closest to the camera again. If it looks awkward it’s because I’m holding the thing at arm’s length, and The Target Child (official house hand photographer) is standing on a box with the camera perched on my shoulder, giggling. This shot answers another inbox question – as you can see I did NOT work the facing using twisted stitches. I knew I wanted to do this fusing step, and I wanted to eliminate any possible source of biasing.


This weekend saw some Rogue advances and retreats.


First, I knit up to the point where I had the same width of finished motif-bearing front as I had stockinette hem facing. Because of the needle size change, this happened on row 10 of the side panel motif chart – a few rows before I was to begin the front pocket, very conveniently – a row without cable crossings on the side panel motif chart. I decided that I wanted to fuse the hem to the body, rather than wait and sew it down later.

This isn’t part of the original pattern. Jenna suggests sewing down the facing in as part of finishing. It would be difficult to write up doing fusing. The "how" is easy (see below). The "when" is harder. When to do it depends on row gauge, which can vary enough to make the answer too subjective for hard and fast directions, especially considering that not everyone would be doing it on the same row, and that exact directions would vary depending on the row used. I can see why she didn’t include it.

Here’s why. For me, fusing the facing posed two potential challenges. The first is common to everyone making either the cardigan mod or the original pullover. The side motif chart includes increases. There are more stitches on Row #10 than there were on Row #1. 21 as opposed to the original 15. If I were to knit one facing stitch with one body stitch, I’d run out of facing stitches, and the hem would be bias skewed.

The second challenge is unique to cardigan mod makers. I’m doing a zip front. If I just work the facing in straight across I won’t be able to encapsulate the lower part of the zipper tape inside the doubled-over hem facing. Not a vital concern to be sure, but one of those finishing/neatness details that are nifty to do (if you remember in time).

So I went about my fusing step. I popped open my provisional cast-on’s crochet chain, and slipped the stitches it released onto my smaller circ, one by one. I folded the piece along my turning row with the purl side on the inside, and began working my body and facing together. Doing this is a lot like working a three-needle bind-off, but without the final bind-off step. Working in my established pattern, I either knit or purled one stitch of the body together with one stitch of the facing, uniting them into one unit. When I got to the side panels I fudged a bit. Because I had more side panel stitches than facing stitches, starting two stitches before each panel, and ending about two after – and trying to be more or less even in my spacing between – I worked one stitch of the panel without a companion stitch from the facing. I did this as many times as I had "leftovers."I am pleased to report that my facing was nicely fused into the main piece, and even in my non-stretchy cotton the facing relaxed nicely, avoiding any puckering or undue flaring out.

Now about leaving room for the zipper tape. I didn’t just begin fusing at the stitch. I left the first and last three stitches of the facing on safety pins, working the corresponding stitches of the body by themselves. I’ll go back later and either end them off with a crochet hook (possibly tacking them down with a couple of sewing stitches), or I’ll sew them down to the zipper tape when I do my final finishing. In either case, I’ve left a slot along the zipper edge to accommodate tape placement.

In other issues, as predicted the Little Dragon Skin pattern did scallop at the bottom edge. The facing accommodated the scallops with no problems, and in fact – I think the non-straight edge looks quite interesting. I like the effect and the treatment because the facing is keeping the scallops from cupping and turning in on themselves. I think I’ll have to play with this hem facing technique on other projects using deeply embossed or deformed edge patterns.

All in all, the fusing step was a rousing success.


O.K. Having done all of this, I ripped back the entire thing and started again. I am now up to exactly the same point as I showed in Thursday’s post. I did this because of a size issue.

My gauge was spot on. The measurements were good. However, I forgot to include one vital thing in my ease calculations. Target Daughter is in the cocoon phase of early adolescence – the phase in which one wants to hide in overly large, baggy, anonymous garments. I seem to remember similar sentiments, and that the whole hiding thing ended up being a prelude to a later butterfly phase.

She "tried on" the piece on the pre-pocket row and was shocked that it wasn’t going to be as generously full a fit as her original concept. So being a good maternal-unit, I decided to subscribe to her comfort level, and start again.

This time it’s going to be harder, as the measurements of the garment she’s chosen as a size model combined with my smaller native gauge preclude use of the stitch counts of the largest size of the original Rogue pattern. I’m going to increase the width of the body panels a bit, but not tinker with altering the angles or numbers of the waistline decreases, nor mess with the armhole. The largest armhole should be adequate. If not, there’s always ripping back and trying again.

If anyone HAS done an up-sizing mod on Rogue and has met special concerns with which I am blissfully unaware, I’d greatly greatly appreciate a warning. Finally, this ripping back thing is good for followers of String. On this second go-around I hope to be able to provide photos of the fusing process.


I admit it. I’m wrong. Not that it happens all that infrequently. Yesterday I answered a question on the KnitList about the central double increase used in the side panel cables of Rogue. I didn’t have my knitting with me, nor was I at my base station, surrounded by my reference library. So of course, I messed up.

Because confusion persists, and I still think there might be a typo in the directions for this stitch as written, I present a walk-through.

The bottoms of the closed loops in the side panel cables are formed by central double increases. The Rogue pattern directions say:

"on RS, knit into the front and back of st, pick up the vertical strand running downwards between these to st just made, twist and knit into this picked-up strand: 3 knit sts made from one st"

I think the "knit into front and back" should be reversed. The all-knowing Barbara Walker in both her Charted Knitting Designs (aka Walker III) and Fourth Treasury of Knitting Stitches (aka Walker IV), says this (paraphrased from page xxiv of Walker III):

Knit one b, knit one in one stitch, then insert left hand needle point behind the vertical strand that runs downward from between the two stitches just made and k1b into this strand.

Like a dingbat I also reversed the front/back first step. Here’s how it should go:

First, knit into the back of the stitch (needle shown inserted into back of next stitch, ready to knit):

Then knit into the front of THE SAME stitch (needle shown inserted in the right place, ready to knit):

Here’s the result after doing the two knits described above:

If you look carefully, you can see the vertical bar both sets of directions describe. I’ve called it out with an arrow:

I take my left hand needle tip and grab that bar, then knit into the back of it as well. Bar shown on the left hand needle tip, ready to be knit as a twisted stitch:

The end result: three stitches where there was one before:

The beatings may commence at sundown. Thanks to Rosemary who took me to task on this one.

Edge Scallops

I also received an interesting observation from Melanie, who said she’d tinkered with Dragon Skin and noticed that it made a very pronounced scalloped edge. She wants to know if Little Dragon Skin does this too, and whether or not it will be a problem.

Little Dragon Skin also scallops. (It would make a very nice scarf stitch for this reason). I am hoping that the two-inch hem facing, knit on smaller needles will help tame the scallops. I can’t say for sure that it will. This may end up being one of those bugs that lives on as a design feature.

I’m almost up to the point where I will be unzipping the provisional cast on, putting those stitches on another needle and working them along with my main body stitches. In effect I’ll be fusing my hem facing to eliminate the need for sewing it down later. I should be able to tell at that point if I like the effect.

Should I have taken the time to work all this out in the swatch before casting on for the main piece? Sure. Absolutely. Most sane people would have thought to do so. But I find knitting to be more exciting when you live dangerously, and I don’t mind ripping back.


Just spent the morning answering questions over on wiseNeedle, so forgive me for cutting today’s post short. Feel free to ask (or answer) questions on knitting technique over there.

Dragon Skin Rogue

I’m surprised no one noticed the discontinuity in the Little Dragon Skin graph I posted yesterday. It’s not as elegant a pattern as its big brother because there’s a break in the lines formed by the decreases and increases when the chart replicates after Row #11. I haven’t decided if I like it yet. The swatch looked o.k., but I need to see it larger. I may end up ripping back the body if I’m less than pleased.

Here’s the obligatory Wiggly Worm Photo of a piece just aborning. Proof positive that I’ve actually cast on and am working on the thing:

You can see the white string of the provisional cast-on, the ten tons of markers keeping me on track (my new silver ones mark the center back, plus the beginning and end of the two cable detail side panels; the older beaded ones mark the dragon skin repeats). I am about to start one of the side panels, and my cardigan split is on the right, where the extra crocheted chain trails off.

I’m using Almedahls Texas. It’s a 100% cotton in faded denim type colors (50g, 105m, color #30). I’m already fearing running out of the stuff as The little bit you see – about two inches of hem facing plus four rows of the main body) is more than half of the first ball. That’s in spite of having 18 balls – about 2060 yards, which should be a ton. In theory…

I can say that this is NOT my favorite cotton yarn. It’s multi-ply, with the multiple plies only loosely wound together. It splits like crazy, and is about as inelastic as cotton comes. It’s nice and light for a cotton though, and shouldn’t have the leaden drape of many worsted weight cottons. Very soft, too. Between the softness and blue color, I can see why Target Daughter picked it from my stash.


Having finally gotten my act together what with swatching, recalculating, and general pointless noodling, I’m embarking on the highly modified Rogue. As ten thousand others have noted, it’s a very completely written out pattern for a pocket front hoodie, by Girl from Auntie’s Jenna. I really like the organic way she has used closed form cables to highlight the piece, and how those shaped cables narrow and widen. Killer!

In spite of the beauty of the native version, I am trying to satisfy specifications issued by a child in The Picky Years, so modifications are necessary:

  • Gauge. Target child has picked out a yarn that knits at 5 spi instead of the pattern’s 4.5. Math will be needed.
  • Fiber. Nice springy wool works best and is easiest to use for cables, but the chosen yarn is 100% cotton. I’ve done complex cabling in cotton before. I’ll cope.
  • Zip front. I won’t be the first to modify this and make a cardigan. The pattern’s own home page provides hints on cardigan-ization. I’ll be leaning on them.
  • Texture for body. Kiddo is in love with the Dragon Skin all-over pattern (Walker II, p. 136). While I prefer the contrast between the smooth body and dense cables of the original, she’s set on my using the design. Unfortunately, the design as presented by Walker needs 26 stitches to manifest nicely. A bit wider than is convenient for this pattern.

So to start. How to start?

First I bought the pattern. (Always a good thing, as “sharing copies” is a pernicious, evil, illegal but all too often seen antisocial behavior).

Knowing that the Dragon Skin pattern in the original was too wide. I began to play with it, and eventually trimmed it down somewhat. Here’s the result:

The original is definitely nicer, with wider vertical elements, but the slimmed down version is quite usable and recognizable as the other’s little brother. I’m still dithering whether or not to do the single stitch knit column between the make-ones as a normal or twisted knit stitch.

I swatched my yarn and established an unambiguous gauge for the stuff in my dragon skin patterns. I got a firm 5 stitches per inch total. Not the 4.5 spi the pattern specifies.

What to do?

First I looked at the size appropriate for Target Daughter in the original. Then I looked at the stitch counts of the next two larger sizes. I did the math to see if at 5 stitches per inch, they came anywhere near the circumference of the optimal original size. Serendipity! One did. I am using that size as the basis for all my stitch count estimations. I’ll use that size’s stitch count directions for anything relating to width, but will use the original size’s directions for length. Yes, I’m sure there will be fudging along the way, especially to eke out vertical repeats so that the cables up the side finish nicely, but I don’t think that those tweaks will be too difficult.

Can you take any pattern and do this? Yes and no. It’s relatively easy to translate between Worsted and DK (5 and 5.5spi) and Aran and Worsted (4.5 and 5spi), but harder to make this translation for larger gauge differences. Plus patterns that rely on row gauge like colorwork, or raglan shaping present additional challenges. It’s also easier to do this if you are not at either end of the range of sizes presented. If you already take the largest size in a pattern written for Aran weight yarn, and you wish to use Worsted, there aren’t any sizes left with higher stitch counts for you to play with. (If you were going the other way – you were faced with a Worsted weight 5 spi pattern that was just a tad too small – you might be able to eke out an additional size or two by using Aran weight yarn at 4.5 spi instead.)

I’ve got my basic stitch count now, adjusted for my finer gauge. The next mod is the cardigan one. The advice worked out by others suggests adding an extra stitch to the front and back so that the total stitch count can be divided by two, creating the center front break. I’m going to add three to the front, but two to the back. My width is just a bit skimpy, and I have a feeling that I’d like an extra selvedge stitch in the center front when zipper sewing and I-cord trim time comes. I’m adding one fewer stitches to the back because my new texture design has a center stitch, and I want it run down the center of the back.

The next step is to cast on. I’ll be working my Rogue back and forth rather than in the round (a loss there, I’d much prefer to work it in the round, but steeking would kill the elegance of the cables at the neckline). I note that the thing is written with a hem instead of ribbing. I like that for this cotton. Working it on smaller needles as directed should tame edge flare. Since I prefer a smooth finish inside when using a hem facing, I am using a provisional cast on – the same crocheted onto the needle one I used for Crazy Raglan. Using needles three sizes smaller than my body needles, I cast on the specified number of stitches for my chosen (larger) size, plus five more (three front, two back), and began knitting the facing.

On my first row of the facing, I decided to spot the left and right side areas in which the cable detail will happen. I did the count, figuring out which stitch will be the center sidemost stitch left and right, then counted out the required number for the first row of the cable detail chart, centered on those two stitches. I put markers in my work and left them there. While I’m not up to the post-facing bit yet, I can use the facing rows to re-count and confirm my marker placement. By the time I’m up to the first row of the main body, I should be 100% confident that those markers are in the correct places.

Next headache? Centering the Dragon Skin texture pattern repeat. On the back, I’ll identify the centermost stitch. That will be stitch #11 on my chart above. I’ll count back from that point, and begin my pattern panel on the appropriate stitch. On the fronts, I’ll also plan out from the center, working one plain stitch, then walking backwards from Stitch #21 to figure out where I have to begin my left front; and doing one plain knit then walking forward from Stitch #1 to place the pattern on the right front. One thing to take into consideration – to maintain a stable stitch count there must be an equal number of increases and decreases per row. Because the width of the back and front panels will require that I truncate the repeats, I’ll have to make sure to maintain that stitch count by fudging if that truncation cuts into an increase/decrease pair. I’m hoping that by happy coincidence, I’ll be able to work the pocket openings into the verticals naturally created in the Dragon Skin texture pattern. THAT would be nifty!

Now all that remains is to plug away at the knitting part. Like with all pattern manipulations, there’s no guarantee that my doing this will work out. I’m willing to wing it. By the time I get half-way up the body I’ll have a good idea whether or not finishing IS a good idea. If not – I’ll rip back and design something from scratch. (If you’ve read this far and noticed that I’ve screwed up my logic, please feel free to leave a comment and let me know.)

One final note – for those of you who are wondering how I can slap a copyright notice on a texture design from Walker – I am not copyrighting the pattern. She owns her prose write-up of the thing. I am asserting ownership of only my graphed representation. Have fun. Use it and other patterns shared here for your own knitting; but please do not repost or republish them without my permission.


I’m still noodling on the hoodie project. Target child is waffling about her requirements. I’d rather wait until she settles into firm conviction before casting on. Some questions came in after Friday’s post:

Why start with Rogue instead of designing your own from scratch?

First, I really admire this particular pattern, its proportions and the way the cables are so cleverly used. Since it fits so closely with the original set of requirements and/or mods to it would not be difficult, why not start out with it? Cardigan-ization isn’t tough, nor would be knitting a smaller size to compensate for gauge differences. As for the rest – the texture pattern and saddle shoulders with a cable down the center of the arms, as Target Child looks over the photos of other people’s finished Rogues, she’s becoming less attached to those concepts.

You know you can use knitting design software to help.

Yup. I know that. I’ve got Sweater Wizard and the older Cochenille product. Hated the latter. I didn’t mind the non-standard format of the directions, better suited for knitting machines than for hand knitters, but I was totally turned off by the lack of technical insight provided by customer support. The thing wasn’t cheap, and I could never get it to run properly. Only one or two of the supplied templates produced any sort of output, and even they were unable to produce more than one or two of the available sizes. “Support” claimed that it was a problem unique to my set-up and there was nothing they or I could do about it aside from waiting for the next upgrade and seeing if that worked any better. Since we’ve got an average of six or seven working computers in this house at any one time (all with different processor/opsys/video card combos), and I tried the software on all of them and turned up exactly the same bugs, I rather doubted that one unique set-up was the problem.

Rather than throwing good money after bad, I decided not to spend close to $100 to upgrade Cochenille (with no guarantee that the new version would work any better. I switched over to Sweater Wizard. It’s got far fewer design templates and isn’t a full-size sloper drafting program, but what it has actually works, and is quite easy to use both during the design and knit-from phases. Which is refreshing compared to my previous experience. My only criticisms of the product have to do with personal preference and fit. I find the standard fit a bit tight for my taste, so I always add extra ease (which is verysimple to do).

My real desire though is to be able to produce the full-featured graphs of actual garment pieces, showing color or texture pattern placement like the ones in Rowan magazines. So far no knitting pattern design tools come close to that degree of integrated pattern shaping/motif placement. Yes, there are export features that allow customization of garment shapes for colorwork placement, but no total pattern maker that lets you tinker with all parameters in one interactive console. (If you gotta dream, dream big. [grin])

Meanwhile, Back at the Ranch

Although progress is slowly burbling along on the hoodie, there wasn’t enough to keep my fingers happy over the weekend. So I started a pair of quickie socks. Standard Figure-8 toe toe-ups with short-row heels. I’m using Lana Grossa Melienweit Fantasy, on US #00s, at the (for me) relatively large gauge of 9spi (68 stitches around). Ankle pattern is an impromptu feather and fan variant:

Here’s the graph for the ultra-simple six-row feather and fan variant used on the ankle. It’s 17 stitches wide and six rows long. I’m working my socks on five needles (four in the sock, one to knit with). Because each needle has 17 stitches on it, this graph is worked once per needle:

More info on knitting socks of this type, including basic how-tos for both the Figure-8 toe and short-rowed heel can be found in any of the sock patterns on wiseNeedle.


Monitor Dearth Watch = 47 days and counting. Samsung’s latest excuse is that they mailed out the thing twice, but each time to a different wrong address, in spite of the fact that my address is correct in their records. Unpleasantness ensued until they conceded that error on their part doesn’t amount to $300. worth of liability for each monitor on my part. Since someone at those other addresses signed for the monitors, I can expect that they will now have the joy of paying for them. Which leaves me still without a monitor.

Now, those of you considering purchasing a Samsung product right now are probably taking this sample of exemplary service efficiency into account as a data point in that decision. And you’d be correct to do so…

Hoodie. Possibly Rogue-derived.

Can’t put it off any longer. I promised the older daughter that I’d knit her a sweater of her own design. I’ve gotten back this set of thoughts to play with:

  1. Yarn choice: Almedahls Texas, a 100% cotton loosely twisted multiply worsted weight yarn in faded jeans/chambray blues. Slightly marled. It’s a yarn sale acquisition from last winter that has been stash-aging a while. Very soft, splits like crazy. Knits up nicely on US #6 needles at spot on classic worsted gauge of 5spi/7rpi.
  2. Required shape: Oversize zip-front hoodie, saddle shoulders and slightly belled sleeves.
  3. Desired decorative elements: Cables! Especially up the center front and around the hood’s edge. Also if possible – the Dragon Skin texture pattern from Walker #2 (p. 136).

Now I’ve thought about starting with Rogue (a truly excellent bit of design work that I envy). There are some problems though:

  1. The gauge of my yarn is wrong for it, but I can cope with that.
  2. Also it’s not a cardigan. I can also cope with that, too. Others have split the front and made it into a zip-up, so I wouldn’t be the first.
  3. The cotton I’m doomed to use is also rather inelastic for this sort of thing, but I’ve done complex cabled pieces out of the most intransigent of yarns, so I don’t think that this one will be too difficult.
  4. The thing really isn’t set up for saddle shoulders. (I think this
    point isn’t a life or death requirement, and Target Kid will be happy
    without cables up the arm to the shoulder so long as she’s got the
    cabled cuff detail).
  5. Much of the beauty of the piece comes not only from its excellent shaping, and clever incorporation of cable increases into accents, but also from the contrast of the very plain body with the deeply embossed cabled trim. Using an all-over texture pattern like dragon skin would cut into that contrast.

Problem:? How do I either talk Target Child out of the dragon skin texture pattern, modify dragon skin’s stitch count/repeat to make it easier to use in a project of this scale; or talk myself into adapting Rogue to use it?? More explorations and/or negotiations are necessary. I’ll probably order the pattern early next week, after I’ve finished swatching out the Texas and playing with Walker’s repeat widths.

Here’s my initial swatching play of the texture pattern as she wrote it. (Dragon Skin is on the bottom of the thing. )