Frogs Everywhere

I think I've done more frogging than knitting the past couple of weeks. 

I can't say much because at least I'm now working on yarn crafting projects again.  Between the month of sewing I had to do this summer and some other miscellaneous stuff going on, I didn't really get back in the yarn crafting gear until the fall hit.

Sure, I did finish a pair of socks for my husband (finally, and without losing one this time!):

But the rest of the time since went like this:

• Finish up the custom baby dress and write up the pattern (which, being a on the fly pattern, mostly involves trying to figure out how the heck you wrote down what you wrote when making the darn thing). 
• Finally start an adult sweater to replace the one I been wearing so long I've had to darn both sleeves at the elbow (anyone remember when the work sweater was completed? It's been awhile; I can't say I'm surprised).
• Realize that I could get a sweater done for NYS Sheep and Wool if I pick up the one I was designing and knitting two years ago and un-screw up the neckline idea. 
• Get past the neckline, do another trim, then decide on another neckline trim to better match the other trim, redo the neckline.
• Finally get to the sleeves, so I do the math for the sleeves, try to work the sleeves, realize sleeve doesn't fit, rip sleeve out, adjust and restart sleeve. Now sleeve is too big on cap but tight elsewhere, rip sleeve out, get peeved at sweater when as I'm not going to finish it in time for Sheep and Wool and have no clue how to actually mathematically calculate an afterthought sleeve.  I then banned sweater to the time-out corner for a couple of days. 
• Decide that due to all the other crap that I should start a nice seed stitch cowl out of some soft yarn bought two years ago. Then I realized that the yarn is too thin to work for a good seed stitch cowl, so I surf patterns, don't like any of the patterns, get idea, try idea, rip idea out, try another idea, rip idea out, chart third idea, start idea, rip idea out, adjust chart, start idea, rip idea out, repeat two more times. I finally get an idea I'm mostly happy with off ground, but at this point I've created a time-consuming pattern for what was supposed to be an easy cowl. I resisted the urge to go find more yarn in the stash to do that seed stitch cowl.  Work on not-easy cowl on the subway for some reason.
• Go back to sweater, figure out a way to recalculate the stupid sleeves, start sleeve again, get half way done, realize it's still screwed up, rip it out.  I then realize I was using the stitch gauge instead of the row gauge to calculate everything for the sleeve, not that my method didn't work. Recalculate using correct gauge and start sleeve again.
• Decide to also work on getting baby dress pattern tech edited, tech editor finds first row has one stitch off of cast on, realize the one stitch off is because all the other calculations are screwed up and spend all night trying to figure out how the heck I managed to knit the thing in the first place.
• Then decided that I should write this blog post instead of working on sleeve or anything else I decided to design or start at the same time.

I mean, it's probably a good thing that I've gotten my design groove back.  I'm looking forward to getting something out there given the time it's been since I've had actual time and inspiration to devote to this.  But why do I have to make it so hard on myself when I could just simply work on something already written or easy without struggling through all the frogs?  Then again, I write software as a day job.  It all involves sitting there and beating your head against the wall wondering why on earth you're doing this when what you did isn't working for the 5th time...until you figure it out, get something done, and feel accomplished and confident.  Then you're more than willing dive right back into another wall because it won't be as crazy this time...right?

And if I have to frog that cowl or the sleeves one more time, the yarn is shot and I won't know what to do with myself.  Probably ban it back to the timeout corner.

Follow Instructions? Never!

So it turns out that I fail at following knitting instructions.  Despite the fact that I wrote said knitting instructions.  Why, yes, I may have had to just rip out a whole weekend's worth of work because I forgot to increase in one location.

Since this is a pattern I am eventually planning to write up and most likely sell, I won't show you much, but here's a teaser (after I ripped out most of it):

What makes this even more...well, I guess what makes it make more sense is that this is the second reproduction of this pattern. Story goes like this:

1. My sister is having (now has) another kid.  It's going to be another girl. Yay, make all the things with the yarn I got on the NYC Yarn Crawl because I got suspicious and so bought baby-appropriate yarn.
2. Start a blanket with yarn I had from last baby making spree, pick all the patterns out for all the yarn I can think of.
3. Promptly get nothing done because get assigned insane work project in the middle of capstone project for grad school.
4. Hit winter break, go on vacation to Iceland (was awesome), get one sweater done for baby over vacation.
5. Realize that all the yarn I bought is wool and baby is due in spring.
6. Find out WEBS is having a sale.
7. Find out nice colored cotton yarn is on sale as well.
8. I can do matching dresses in two different colors of this yarn for both my nieces, right?
9. Realize I don't like any of the patterns again for the style of dress I like to give kids.
10. Make up the pattern by coming up with the start, getting half way through the top, deciding I don't like my plan, futzing around until it works out, quickly scrap write it down with calculations, and continue knitting body of dress.
11. Start grad school again. Tons of schoolwork this semester again. Get to work all the hours again because nor'easters. Knitting? What's that?
12. Realize baby is due in a week.
13. Quickly finish up dress, writing rest down on paper.
14. Baby born, yay! Realize I am not going to see baby until I'm out of school, damnit.
15. Finish grad school. Get to work two nights right after. Somehow finish baby blanket same time.
16. Get to see sister and nieces. Give the sad pile of stuff I actually got done to sister. I tell her 'I'm going to make this dress for the other niece', and she goes 'the dress you made her before still fits. It actually fits both of them.' I think 'going to do it anyway; need to test pattern'.
17. Clean up notes made before, print them out, and start second dress.
18. Don't actually read notes carefully because I think 'ah, I see what I did here' and forget to do one increase, which screws up the whole pattern.

And here we are. Back to almost the beginning because I missed one last increase needed for the pattern to work.

Oh well. At least I have time to knit again.

So this was just the last year's worth of crap going on that lead me to end up abandoning the blog for...two years, yikes!.  Grad school is completely done, work is ok at the moment, and everything else is not where I thought I would be when life went crazy, but it's now stable, so I should be getting back into the swing of things now. There's a lot of catching up to do so I may not get there right away, but I'll try to start blogging my mishaps and future projects again.  There should be a number of those shortly.

The Good Kind of Remake

In the wirlwind of projects, both craft-related and not, that I've have to complete or are completing for others, I did manage to re-visit an old project of mine.  I got better yarn and knit a new version of my Reversible Eyelet Hat.

To be fair, I guess it wasn't 100% for me, though this version is better than my old one (which I still have and used). The person in my knit group who's responsible for the KALs (which work a bit differently in our group than the more traditional method) decided to focus on hats again, and out of the long list of hat patterns for it decided to list both of my hat patterns.

When she told me this, my first thought is 'dang, I wonder if the first one is good enough for that?'  The Reversible Eyelet Hat was my first knitting pattern, and it was designed on the fly in one size.  As well, I had already seen from those who did it on Ravelry that it ran big.  I also found that after the first year, my original one has stretched out as well and was big for me as well, and I prefer looser hats. So I decided to take my own pattern and re-knit it using nicer yarn, a different gauge, and less stitches.

The good news is that I found that the pattern is 99% correct.  The CO amount with the needle size it gives you will make a big hat if you have around a standard-sized women's head, but the instructions themselves are perfectly fine.  The only correction I would make is that unless you need a large hat (think around 28"), you're better off COing around 92 or 88 stitches, even 84 depending on things like the yarn and needles you're using.  I did 92 stitches using smaller needles for the re-make, but I also decided to use a wool/silk blend that had it's own stretching tendencies (this was probably not the best decision with a hat pattern that also has a tendency to stretch out, but it worked).  The good thing about that pattern is that it is super adjustable, and any multiple of 4 will work with the instructions as written (so I guess I wasn't as much of a dumbass with my first pattern as I thought).  Also, dropping down doesn't affect it as much as you would think, given the lacy and ribbed nature of the hat.  The pattern itself has a tendency to stretch, so you need to counteract that a bit.

So I didn't bother rewriting the pattern (though I will change the CO amount).  But be assured that it is doubled checked now.  Now if only I could take better pictures.

For What it's Worth

While, given it's a week into February, that my hopes for getting a new pattern out around New Year's are dashed, I am working on one.  Here's a hint:

One of the reasons I have no pattern still is simply because I keep changing my mind.  I keep changing my mind partly because I keep trying things out and they don't work.  Or I don't like them.  Or it's too small, too big, wrong yarn, etc, etc. It isn't helping that I only did one swatch, and it was small.

This is what happens when you think you can knock out a 'simple' item of your own design without doing much pre-planning, out of scrap yarn.  I should have known it doesn't work that way. Now, it doesn't help that I haven't had much time for knitting recently, let alone calculating things officially in a spreadsheet.  Spreadsheets require hours in front of the computer working on them.  I can knit on the subway,  the bus, and wherever I may be at the moment. Might have contributed to my throw-it-to-the-wind half-ass planning, that did.

Anyway, it seems to be working now.  Hopefully.  Though I can't promise when it'll be written up and out, or if I'll be more than one size,  I can promise that I'll release it for free.

I actually thought about that for a bit, even though this pattern is pretty simple and in the end I decided that it'd only be worth between $0.50 and a dollar, which means it doesn't pay to get it tech edited.  And I won't sell a pattern that hasn't been tech edited, because that's not respectful of my users.  If it's free, well, I try to make sure there's no errors, but that's the trade off for getting a free pattern.

However, it does have a different aspect to it, which is why I paused at first.  Even something as simple as this takes a good amount of planning and some time investment.  This is something I have very little of at the moment.  And since my last pattern was put for sale, there's the aspect of going legit on top of it.  Where's the line between free and not?  Should I give my efforts away like that, after I've said they're worth something?

But then I realize, who am I kidding, I ain't a professional in this nor do I want to be.  So, free pattern. At some point.

I did also get this done:

Pattern is Flame Hat by Irina Dmitrieva.  I did the beret version.

Yay, shiny cable hat.  It's a little big, but it stays on my head, covers my ears, and is warm enough. Now what to do with the other skein of that yarn...

Plans, Classes, and Decisions

In the black hole of my disappearing act, of which only part of it had to do with knitting, I've been trying to design a tank.

It is not the same tank I started with in the last post, no.  That was the tank I did my usual 'throw planning to the wind, swatch once, and start' act on, and it failed miserably.  I was so certain I would start from the bottom, but I kept ending up with too many stitches.  Several tweaks later, I decided to start at the band.  I calculated how many repeats I would need based on a similarly designed swatch, and went at it.  It started looking a bit big, but no matter, the cables will close it up.  It kept looking a bit big until I ended the chart, held it up to me, and...oops, did about seven too many repeats. 

I checked my gauge, found it wanting, so I looked at my half-assed calculations, which were changing with every whim I hit.  It was all wrong.  I ripped out the last ball I joined, looked at it, and...decided that this was the wrong yarn to use.  Too bulky, too big, didn't work.

Oye.

So I started hunting down more suitable yarn.  I actually went and bought a skein of one 'okay it may work' yarn and wound it up.  Then I decided to work on other things that didn't require as much thought (and need to get done as well):

Also, I'm still not done with the baby sweater and my Mom finished the blanket already.  That never happens!

Well, ok, maybe a little.  I had to rip out a few things in that sweater too. 

Anyway, while I was putzing about on where I would get the yarn for this tank I want to make, I also kept thinking about what to do with the yarn I had originally bought.  It was just sitting there because I didn't bother putting them up, of course.

Then I got a better idea.  Another tank, but one that would work with this yarn.  Simple, easy...

 ...and, it turns out, a pain in the butt to calculate everything. Of course it is.

I know this because I swore I would do this properly this time.  I would not quickly calculate how many to cast on for my size and go.  I would swatch properly, calculate everything out, then adapt to my size and go.  It helps that I got a 'up to 75% off your first class' coupon from Craftsy (because I signed up and only took free courses, then forgot about it) and I used it for this class.  Because, hey, ten bucks for instructions on the crap I keep doing wrong; it's a good deal, right?

Well, I haven't finished the class, but while it was worth the 10 bucks for the sparks I needed to figure out how to organize this stuff into a set of competent calculations, there are parts I've either 1) got so bored because it was below my skill level (computer skills, actually, not knitting.  She explains in minute detail how to use a spreadsheet.  I get why, but some of us have, you know, even programmed macros before) or 2) didn't get the reasoning behind it.  I'm at a part that is supposed to help me, but her setup wasn't working out for my tank.  I don't know why, because there's some magic numbers in her calculations and even when someone asked her in the comments to explain it, she didn't.  But thanks to the comments, I remembered I bought this book:

It was a random, get free shipping on Amazon buy.  I half-forgot about it, thinking a lot of it wasn't so relevant.  However, a comment in the class pointed me in the right direction, and I found that it contains a much simpler way of doing the same thing.  That worked.  Translate it into a spreadsheet to auto-calculate and...ta da.  Another thing half done.

Because desipte having spent...I don't know, three weeks doing this, I'm still not done.

Ok, part of it is my life intruding.  But most of it is because I keep going off on one tangent, deciding against it or running into a brick wall, and going off again.  That part of the class I got confused on?  Was about calculating slope.  Which I first tried to do using inches and the slope of a line formula, and couldn't quite even out the slope to go where I wanted it to in stitches.  That's when I watched that segment of the class.  So I've done that part about three times now.

At this point I could technically cast on.  I have the stitch count where I need it, I just need to adjust for my size directly (I've been using standard measurements so I have a constant).  However, since my efforts have been all over the place, I'm not sure if I have everything to at least easily calculate where to proceed.  And I'm still not done with the class.  Decisions, decisions. The problem with designing is there is no base and way too many decisions.

So, I'll probably continue on to the end of the class, then do a quick look at what I have and start writing/knitting  But it's taking all my effort not to get frustrated at all the wasted planning and just cast on already.  However, we know where that goes.  It goes like this:

Badly.

Why You Should List a Gauge For Your Pattern

I seem to have a knack for finding the patterns that don't give a gauge.  It annoys me.  I usually use the pattern anyway, but it still annoys me.

Granted, this tends to happen on free patterns, so you would think I shouldn't complain.  However, as someone who also has developed free patterns, I know how easy it is to get and list the gauge for most patterns.  Yardage missing?  Sure, that's pretty hard to guess at and you need a ounce scale to properly calculate it (and I know I don't own one of those).  Gauge?  No excuse.  None.  I behove anyone who's releasing a pattern to the world to give the gauge, and here's why (and why it shouldn't be an issue):

1. It allows the user of your pattern to make sure they'll get the same product you did. People knit and crochet differently and have different tension.  That means while you got an adult sized hat using size 6 needles, someone who knits/crochets tighter than you could end up with a child sized hat following the same instructions.  If you don't give a gauge, there's no way for the user to check to make sure they're going to get that adult hat without following your pattern and ending up with disastrous results.


2. It allows to user to adjust the pattern themselves.  Sure, if it's a free pattern, you could be lazy and only give one size.  That's ok; we understand.  But when you do that and don't give a gauge, the user will be left either wondering what to do to adjust for, say, using a different brand of yarn (which will affect gauge even if the same weight) or how to adjust for their particular size (after all, why go through all the work of making it if it's not going to fit right?).  A stubborn yarn crafter like me may reverse-engineer it, but that's asking a lot from your users just to make sure they get what the picture shows.


3. It's not hard to calculate and list.  This is the crux of the above.  Sure, there are many useful details that can be in patterns, but some of them require special equipment or some major calculations.  I understand if you don't want to go through that.  But gauge is not one of them.  You did a swatch and/or created the item you wrote a pattern for, right?  You may have winged it and wrote the pattern later, but that means you have the finished item.  Get a ruler out and measure your gauge.  If you're simply writing the pattern, you either got the gauge from a swatch or you're using a set gauge to calculate out your pattern.  Show you work; list that gauge!  There is no excuse not to know that information.  List it on the damn pattern.

So, yeah, you get what you pay for.  But if you have any ounce of kindness towards those you wish to use your pattern (or don't want a flood of emails from the users), list the gauge.  You should know it, so let your users know it too.  Yes, I know that some items it doesn't matter so much (like, say, blankets), and it's not so bad seeing no gauge listed there.  Still, it'd be nice to let you users know because they may end up with a lap blanket when they were trying to create a full one.  Anything wearable?  List gauge; no excuse.  It's needed. Socks are one of those items.  Hats are too.  Some people have big/small heads or big or small feet than 'average'.  Even if the pattern is 'one size', list gauge.  Give your users the tools they need to make your pattern work for them. It'd make everyone happy in the end.

I Have No Excuse

Actually, I do have a few excuses.  They're just not very good, so I'll save the hee hawing about how I haven't done anything with this blog in more than a month and just catch up with the projects I finally managed to have time to sit down and start.

First off, though, do you remember these socks I made?

Yeah, I don't expect you to.  Anyway, they were my first pair that I knit up using a skein of

Fiber Optic Yarns Foot Notes that I randomly bought the first time I went to Rhinebeck. Just so you know, they made one tough pair of socks.  You see, they're the only wool socks I own at the moment.  Any of you in the northeast on Memorial Day weekend know that it was cold and rainy that weekend.  I went camping in it, well, until the wind broke most of our common tents on Sunday and we had to pack up and call it a trip.  However, the worst of the rain and cold was Saturday, and I wore those socks throughout most of that day (because who cares if they're not period when you're getting rained on all day).  They got wet, muddy, and absolutely trashed, to the point that they were so soaked I had to take them off because my feet were going numb from the wet and cold. 

Because they were so messed up when I got back to my parent's house, I decided to throw all caution to the wind and run them through the washer (well, that and my parents don't have a good place to handwash things.  And I already had asked them if I could wash my boots in the kitchen sink).  And taa da:

They look just as good as they did before the camping trip.  Granted, this was after I washed them again in my sink so I could block them properly (I noticed they bled somewhat when I did that, which never has happened before I machine washed them.  Luckily, I washed them alone in the sink, and with dark clothes in the machine).  But I have to say, not the softest or warmest yarn for socks, but pretty tough. Which is good.

So, now that I have more time, I've finally set down and started designing the tank I wanted to do.  Did I ever mention that before?  Anyway, I've wanted to do a purple and silver tank for awhile, though the design in my head has changed every now and then.  About a month or so ago, my knit group went on a field trip to WEBS, and I got a lot more yarn (<sarcasm>because I don't have enough of it at the moment</sarcasm>):

There, I managed to find a cotton yarn that wasn't Prima Cotton for once:

I then changed my whole idea of what I was doing and stopped there because I had other shit to do.  However, this weekend I managed to finally sit down and calculate out the measurements and stitch counts I needed to at least start the tank:

Hopefully it doesn't become a wreck.  If I'm really lucky, I'll be able to size it and have a new pattern!  Honestly, writing a shirt or sweater pattern has spooked me a bit, but that's another post.

Also, I started swatching for a baby sweater:

Because as luck would have it, right before I went to WEBS I found out another cousin of mine is having her second child.  So I bought yarn to do a baby sweater, which of course ended up being a sport weight yarn despite the fact that half the patterns I have are for worsted.  However, it turns out that my gauge isn't too far off for this sweater, and I just have to go a size up from the size I want to do to get that size.  It should also make a nice, lightweight cardigan (since most of my cousins live in warmer climates...boo...).

Finally, I'm still working on those other socks:

One and a half done, another half to go.  A good, easy, project with some yarn from Rhinebeck.  I tend to buy sock yarn at Rhinebeck, don't I?

Anyway, I should get back to actually getting some knitting done.  Or maybe other things done.  But knitting's better.

Distractions and Old Obsessions

I figured that my next post would be the results of the test.  Didn't happen.  I still got one more swatch to do, and then I got to record everything.  I should be done next week.

And why am I not done?  Couple of reasons.  One, I hate swatching, so I'm procrastinating.  Two, I got distracted by a thousand other things.  This post is about those projects.

First off, I spent my week 1)starting the baby sweater (having done all the math for the body of the sweater, at least), 2)realizing my choice of increase sucked and therefore frogging the sweater, 3)restarting it with a new increase, 4)noticing that it looked a little big, measuring it, realizing that it was in fact an inch too big, re-measuring the gauge, realizing that I had had a gauge accident, and therefore frogging the sweater again.

This was followed by an investigation as to why I had had a gauge accident, which was found to be due to my own stupidity.  My swatch didn't lie, in fact the first swatch I did for the baby sweater was at the same gauge I was getting for the sweater itself.  The problem was that I measured it wrong the first time, and therefore every bit of math and planning I did for this pattern was 100% wrong for the size I wanted.  Yeah.  Ripping out 11 rows and having to re-do all the pattern math was not what I was aiming to do this week.

Anyway, having done that, I did get it started again:

And it is in fact the right size this time.  I checked three times.

As well, as I was knitting a garter stitch square, I was thinking about how I really shouldn't be knitting a square for my Log Cabin Afghan, and should really switch the needles back to the Crazy Cable Blanket so I could get some of that done.  Except then another train of thoughts went through my head.  You see, the baby sweater needs to be done by June (as well as the one that still needs buttons. I haven't had any luck with that).  Also, I want to knit up a small shawl using my other skein of Merino Light, and that will also need to be done by June, as I wish to wear it to my brother's bar mitzvah.  Surfing for patterns for that, I realized that I need to get my brother a present.  But what to get him...hm...what did I get for my sisters...oh, shit, I made them crocheted kippot.

This needs some back story.  You see, I originally got interested in pattern design for one reason.  When I was in high school and actually not only considered myself Jewish but was a constant participant in one of the youth groups, I wanted to make myself a kippah. I tried finding a pattern online, but that didn't net me much back in the early 2000's.  I had a vision, and I wanted that.  So, I spent most of my high school years making and trying to come up with a pattern for the perfect kippah.  Two of my best efforts of this ended up going to my sisters for their bat mitzvahs, one of them actually being very good. Unfortunately, I crocheted it as I was watching the Columbia disaster unfold on TV and therefore didn't write down what I did, and never managed to recreate it.  I, after making a bunch of failed efforts, gave up when I went to college.  This left me with a shit-ton of crochet thread that I've, for some reason, always kept around but have not done anything else with.

So guess what made a reappearance recently:

Yay stash.  Anyway, in my time on Raverly, I've noticed that they had a whole category for kippot, so I went and clicked it.  Lots of free, basic knitted and crochet patterns for kippot.  Only one problem.  None of them are for crochet thread.  So, guess what I've been doing today?

I'm once again trying to create a kippah pattern so I can also make my brother a kippah for his bar mitzvah.  In June. Oye.

Of course you may look at the start of that effort and go, 'wait, doesn't that look a little feminine for a boy?' and you would be right.  That's because after my third time starting (and after buying three different sizes of steel crochet hooks...no wonder I sucked at making kippot last time, I didn't even have the right size hook for the yarn!), I got the ripple effect that I had achieved on my only good effort last time I did this.  So I started writing down what I was doing and went with it.  Not that this little side effort hasn't given me an idea of how to make a more standard kippah, but yeah, this isn't for my brother.  Don't know what I'm going to do with it, assuming I get something out of it.  Maybe give it to my mother, since I've never made her one either (when she had her (adult) bat mitzvah, I bought her a kippah).

Now I've started something else, this leave me with four projects in progress (where did my rules go?  Threw them out when I moved, it looks like), two active which need to be done by June, and one that needs to be done by next December (given this is Crazy Cable Blanket, this isn't a sure thing.  I have to get rows done every week to potentially make that deadline).  I also have another project that isn't started that I would like to be done by June (but honestly, if I don't get my shawl it's not the end of the world).  And yarn I just bought for a hat I was hoping on making before winter ended.  And eight done squares and one in progress for a blanket I don't need, but since it's a mindless project, it gets worked on more often than Crazy Cable Blanket does.  Oh, and that swatch for my test. Do you think I've bit off more than I can chew here?

How Not to Wind a Hank, with Some Reflections on Designing

So, this weekend, I didn't get much knitting stuff done.  Did a couple of rows on Crazy Cable Blanket, worked on a couple of squares (partly while waiting in a waiting room; partly during the Super Bowl, though I didn't get nearly as much done during the Super Bowl as I thought I would.  Something about being at a party and being from NY, that kind of thing).  Oh, and decided I was going to swatch for this baby sweater/shirt/whatever that I can't really decide what I want it to look like, let alone actually sit down and do the math.  But anyway, that little side journey was thrawted by one of the hanks of cotton.  You see, I had these hanks:

And one, once a swift and ball winder were utalized, quickly became this:

However, the second hank quickly became this:

(Yes, that wooden thing is a swift.  It's an Amish-style swift, verses the more common umbrella type)

Yep.  A big, steaming pile of yarn mess.  Why did it become such a mess?  Well, whoever wound the hank up did a shitty job.  Both ends of the hank were tangled up with the other strands of the hank, making winding off a swift impossible.  I tried.  For awhile, I was weaving the ball winder in and out of the hank on the swift when needed.  Then, I got to a point where the space the yarn went through was not and could never be big enough for the ball winder to go through.  So, I took the partial cake of yarn off the winder, tried winding it by hand off the hank, watched the partial cake start to disintegrate while the hank tangles became more numerous, and therefore got frustrated and took the hank off the swift.  Which meant that it disintegrated into the mess in the picture above.  And that's after I spent an hour attempting to untangle it.

Ug, how hard it is to wind a hank, people?  Big circle of yarn.  Really now.  The last time I had this issue was also a hank of cotton, too.  Different company though.

I finally did get it untangled and wound up into a non-disintegrating yarn cake, though it took me at least two hours to do it, split across two days.  Which meant I got no swatching done.  Oye.

Of course, the whole swatching and knitting of this yarn is another issue.  I want to create the pattern for this baby sweater/cardigan/whatever myself and write it down.  I have some ideas, and some constraints (needs to be short-sleeved, gender-neutral, and I only have one hank of each color plus some black cotton from another FO), and no idea how the variegated yarn knits up, which is a problem I need to fix.  But what this also means is that I have to sit down, do the math for whatever I design (which will probably be way too complicated and will therefore have to be toned down), knit it, hack it, fix my math, and then figure out how to size it.  I've never done a sweater pattern before (well, I tried once, but while I did get a FO out of it, I did not get anything I liked or useful to write a pattern up with).  I have 'till June for the FO. 

Which brings me to another mistake of mine that I realized somewhat recently.  You see, when I first started writing my patterns down (back when I just crocheted), I thought that designers usually designed while knitting/crocheting, wrote down what they did, and then released it into the world.  So that's what I did, both successfully and not.  I BS'ed a pattern while I created it, tried to keep track of what I was doing and not do anything too crazy,  made it pretty and posted it.

Well, except that's not how it works in the real world.  Most designers write the whole pattern first, or at least most of it.  And, there are designers out there that never make the patterns they write.  They write the pattern, and then send it off to be tested by other knitters/crocheters.  This blew my mind.  Really?  You can design something before you make it?  How do you know it's going to work, or what it's going to look like?

Then I actually thought about it, and realized that I'm an idiot.  Of course you can write a pattern before you make it.  It's like writing pseudo-code or planning out a program to the function level.  If you know what you're working in and what it's supposed to do, you should know what's possible or not, and therefore write fine code or patterns without ever executing it or making the pattern.  Theory and thought will show you what will work or not.

Of course...I also plan a lot of my programs partly on the fly.  It's just the way I think; I need to see it working to really say 'yeah, this works'.  Now, don't get me wrong, I do plan the logic flow, gather requirements, do mockups of screens, and all the other fun planning steps that come with coding.  But I tend to plan the actual structure and/or some details of the program itself by just coding it and getting it up and running.  So is it really surprising that, knowing no designers or anything about the process, that's how I was designing as well? 

Except that, why I don't mind coding this way (to a point), on-the-fly planning in yarn craft is way more annoying.  See, to change something in code can be very simple (well, I should say in the environments and languages I currently work in).  You go, you figure out what you want, you write it (or copy and paste it), and you run it.  All the rest of the code you've written and tested is still there.  To change something while making it in yarn usually ends up requiring scrapping part of the project.  Or the whole project.  Or even the yarn you bought for the project.  You can't reuse stitches you knitted after the change, at least not usually.  And a different construction?  You can't just copy and paste what you want and piece it back together, you know.

Hence, I'm planning on writing down most of this baby sweater/cardigan/whatever pattern before I attempt to knit it.  I'll swatch to see what color and stitch combinations look good, I'll do the math and write down everything.  Sure, something will change after I start it.  But I won't be doing half-assed math calculations that lead to a too-wide neckline like my last sweater project.  Or a too-loose gauge that just didn't work, that I didn't bother pulling out because that meant losing everything I'd done before.

Famous last words, I know.

In Which I Learn the Importance of Researching Before Pattern Writing, and Get Addicted to Garter Stitch

So, my plans once again get made, and the fall into the dust.  I should be working on either the baby sweater to be made with my new yarn, or the crazy cable blanket, but I'm not.  Actually, I've managed to start another project in the meantime:

This is from a pattern in 60 Quick Baby Knits called "Log Cabin Afghan", except that I'm altering it.  The square is actually supposed to have two more blocks of color going around it, but I decided I didn't want to do that and stopped early (yes, I know that means more squares will have to be done.  But it also balances out color usage).  That, and since I'm using whatever yarn I have right now, which is mainly Caron Simply Soft with some Berocco Vintage for the middle square, the squares aren't all going to be the same color (though I haven't decided what to repeat or not yet, still thinking about it.  Also, I do not kid myself that at some point, more yarn will have to be bought to finish this).  As well, despite the pattern source, I doubt it's going to any baby.  My color scheme of worsted weight yarn in my stash isn't exactly baby friendly.  Thirdly, I really should learn to read patterns carefully before starting them.  You see the pile of center squares?  That's because I didn't realize that you didn't bind off on the first square, but kept knitting, and then turned.  I'm having to undo the bind off and then continue for all those squares because someone didn't follow instructions.

You would think I would have been driven mad by all the garter stitch done in those squares (and hell, I'm not even a big fan of garter stitch as a look), but I'm oddly addicted to it right now.  I guess my mind just needs something not complicated.  I've had better weeks.  At least it'll be a better project to work on during the Super Bowl.

In other news, I was pretty much done with the baby hat pattern I posted just now last week, except that then I actually bothered Googling 'Mistake Rib'.  You see, I learned a 1x1 version of mistake rib that wasn't reversible, leading me to decide to make a 'brim up' and a 'brim down' version of the pattern.  Then I found out that proper mistake rib is a reversible pattern.  Oops.  I could have saved my ass from having to do two hats (though doing the second hat reveled some other math-related mistakes in my pattern, so it still wasn't a waste of time).  However, changing it now would dictate a completely different pattern, as the math doesn't work out with my current stitch count.  So I apologize for that.  I could have made it easier, and I didn't.  I really should do my research before embarking on pattern writing wild goose chases.  It's because of this that I almost didn't post the pattern, thinking that it shows that I'm a bit of an idiot.  But I put a descent amount of work into it, so I decided to post it anyway.

However, between the pattern below, the squares, and some idea sketching for the baby sweater (which I'm most likely not going to use, but anyway), I haven't had time to do much else.  It's odd. I've gotten a lot done, yet it seems like I haven't done anything.  Oye.

Depressing post is depressing.  Will have to post later when I'm in a better mood.