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.

My Life is Baby Projects

Jeez, where do I start? Well, I guess that one of the reasons I haven't posted any of my projects in half a year is that my life is currently baby patterns, and for awhile I couldn't even talk about it.

I was merrily carrying along up to the end of last year working on things like the sweater pattern I swore I'd create and the sky shawl when one of my sisters announced she was pregnant.  In my family's house, that goes quickly from 'yay!' to 'oh, shit now I need to buy yarn and make stuff!'

Well, maybe that was just me.  But other members of my family are also making stuff.

Anyway, so for the past 6-8 months or so, almost all of my projects have been baby stuff.  I made this sweater:

I have to credit the woman who works at the button section of the notions store I go to.  I'll be looking at something that would work, and then she'll come up with completely different buttons that work perfectly.

and a matching hat and booties:

and then started this blanket (haven't finished it yet, though):

and then got this out of the way:

and then started another, cooler weather sweater, for which I have no picture yet.

We're not going to talk about the amount of yarn I bought for this (more than I've used, certainly). I always get into this 'I can make all the things!' mode when it comes to special things like having an excuse to make really nice baby items (since this is my niece).  However, it turns out that, no, when you work full time and go to school part time and have to do things like keep up with an apartment and get distracted by my fiance and my attention-whore of a cat:

Who then proceeded to attack the sweater.  He's already claimed the extra, wrong-sized, baby bootie.

, let alone all the scheming and planning I've done for various things, one being the baby shower, you in fact cannot make all the things.  I can barely make the baby stuff; I haven't even touched the other projects in months, and I'm still in the middle of it.

My niece is due next month.  Oops.

Emergency Baby Sweater

I used to have an extra baby sweater lying around, a couple of years ago, until I decided to gift it to my previous downstairs neighbors who had just had a kid.

I should have made one to replace it.  I wasn't expecting to be told a relative of mine was having a kid only two months before being due to have said kid (communication?  Why would there be communication?). However, I decided to try, and managed to pull off making a baby sweater within a month.

The pattern is Preppy Cardigan from 60 Quick Baby Knits, the yarn Cascade Yarns Pacific (which is one of my favorite acrylic/wool blends now; it worked up wonderfully and you can throw it in the washer and dryer no problem.  This is after I washed and dried it, by the way).

And because of that, there's a happy ending to this story.  I managed to mail out the sweater to have it arrive just in time for the baby to be born (as in, the relative I mailed it to took it to the hospital with her to give to the new parents). So I have that going for me.

As well, this is on top of the other relative I've known was pregnant for longer, which luckily is due in March and therefore that project is on the back burner, because holidays are coming up fast and I had to start making presents. I've already made at least two of my presents already and am working on a third:

I based this off of a pattern on Ravelry called Squishy Soft Cowl, but I cast-ed on a lot more stitches. And accidentally twisted the cast on, so it's now a mobius cowl. Oh well.

Pattern is Brain Waves, also on Ravelry.

Yeah, I've got the socks done.  And a baby sweater.  And a cowl. And part of a hat.  Wow, that's a lot given that I've had no time recently (going to grad school on top of everything can do that to you.  Oh, and getting this fur-ball doesn't help either:

This is Murphy.  This is Murphy sleeping on the bag my project is in that I brought over to knit on because he was trying to sleep next to me on the couch. Instead, he immediately sat on the bag and fell asleep.

). At least I still have my commuting time to work on things.

Of course, the one thing I did sacrifice this year was making a Halloween costume, so I did forgo something. Can't have it all.

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.

Mistake Rib Baby Hat

 

Mistake Rib Baby Hat

Errata: 
10-30-2018:  fixed 6-12 month decrease section to align with written stitch count.

Craft Type:

Knitting

Skill Level:

Easy

Sizing:

For sizes 0-3 months (3-6 months, 6-12 months), 12” (13”, 15”) round largest part of hat, unstretched, and 6” (7”, 7.5”) to i-cord tie.

Gauge:

23 stitches and 35 rows = 4” in stockinette stitch

Materials:

• A lot less than 1 skein of Bernat Softee Baby in Gray Marl (for reference, I managed to to a small baby cardigan and two of these hats out of one skein). If you have about 100-150 yards of another DK weight yarn around, you could use that (and if you don't like acrylic, you won't want to use the yarn I used anyway. It's standard acrylic).
• US 4 (or whatever you get gauge on), 40” circular needle or longer (for magic looping) or a set of US 4 (or whatever you get gauge on) DPNs (if this is your preferred way of working in the round).
• Darning Needle

Abbreviations (US terms are used):

CO – Cast On

YO – Yarn Over

K – Knit

P – Purl

K2tog – Knit two together

Notes:

This is done using a 1x1 mistake rib, so it's not reversible.

Instructions surrounded by * symbols indicates repeat sequence until the end of the round. Instructions where there is a number followed by numbers in parenthesizes indicates different numbers or steps for the different sizes. If you only see one number or step, it's for all sizes. If there are different instructions for the brim up or brim down versions, they appear under brackets stating what version in the order 'Brim Down/Brim Up'. If the instructions apply to both, they are started with a set of brackets as such. To note, the main difference is the brim pattern and where to measure the hat from for the body. After that, it's the same.

Instructions:

[Both]:

CO 66 (70, 86) stitches. If using DPNs, spread out stitches evenly across all your needles. If magic looping, split evenly.

Brim:

[Brim Down]:

Round 1: *K, P*

Round 2: *K*

Repeat 1-2 until ribbing is an 1” long.

[Brim Up]:

Round 1: *K, P*

Round 2: *P*

Repeat 1-2 until ribbing is 1.5” long.

Body:

[Both]:

Round 1: For 0-3 month and 6-12 month sizes, K2tog first two stitches, then K to end of round.  For 3-6 month size, just K whole round.

[Brim Down]:

Work in stockinette stitch until hat measures 4.5” (5.5”, 6”) long from CO edge.

[Brim Up]:

Work in stockinette stitch until hat measures 4.5” (5.5”, 6”) long from the start of the stockinette part.

Decrease Rounds:

[Both]:

(For 6-12 month size, start here)

Round 1: *K15, K2tog*

Round 2: *K*

Round 3: *K14, K2tog*
Round 4: *K*

Round 5: *K13, K2tog*
Round 6: *K*

(For 3-6 month size, start here)

Round 7: *K12, K2tog*

Round 8: *K*

(For 0-6 month size, start here)

Round 9: *K11, K2tog*

Round 10: *K*

Round 11: *K10, K2tog*

Round 12: *K*

Round 13: *K9, K2tog*

Round 14: *K*

Round 15: *K8, K2tog*

Round 16: *K*

Round 17: *K7, K2tog*

Round 18: *K*

This should leave you 40 stitches on the needle. If you don't have this amount, please adjust accordingly until you do.

Hat Closure and Poof Top:

[Both]:

Round 1: *K2, YO, K2tog*

Round 2: *K, P*

Round 3: *K*

Repeat 2-3 until ribbing is ½” long. Cast off on round 2 in pattern. Weave in ends.

I-Cord Closure:

[Both]:

Knit a three-stitch, 8” i-cord. If you want more decorative loops, you can make it longer. (If you don't know how to make an i-cord, click here). You can use the same needles as the project, or go down a size or two if you want a skinnier i-cord. Do NOT weave the ends of the yarn into the cord, and make sure at least one end is on the longer side.

Weave the i-cord in and out of the YOs, making sure that both the ends of the i-cord are outside of the hat at the end and are the same length (you may find that putting a darning needle on one of the loose ends makes this a lot easier). Pull tight to shut hat.

Cross the two ends and wrap them around the top of the hat (level with the skinniest part of the poof). Tie ends into a knot on the other side (like the first step of tying a shoe. It doesn't need to be secure, just together.).

Determine which piece of yarn on the ends of your i-cord are longer. Take the shorter one and weave into the i-cord like normal, then tuck the end of the i-cord under the knot, making a small loop on one side. Thread a darning needle on the other piece of yarn, and use it to tuck in the other end of the i-cord under the loop like above. To do this, draw the needle through to the inside of the hat under the knot, making sure to go through the other end of the i-cord already tucked under there, and pull. Then, thread the yarn in and out from inside the hat through the ends of the i-cord and the knot to secure the i-cord and it's ends to the hat. End with yarn inside the hat and weave in the end like a cast off. This should leave tiny loops above and below the i-cord where the knot was placed.

Happy knitting!

* * *

If you find any errors in this project, please e-mail: CompileYarn[at]gmail[dot]com, or leave a comment  here or on Raverly.  Copyright (c) invisican/CompileYarn(). .

I Seem to Plan These Things at the Last Minute

So, in true me fashion, I found out last week that Vogue Knitting Live was being held this weekend in Manhattan, and therefore made last minute plans to go.  Which I can do, since I now don't just live close to the city, but now live close enough where attending was just a matter of hopping on the subway.

Unfortunately, having just moved (as well as had some other unforeseen cost sinks) meant I couldn't afford to take any classes, not that there was a good selection the last week of registration anyway. I ended up doing the 'I Heart NY' package, since paying for that cost just as much as paying for two day marketplace pass, and got you a lecture on top of it.  It ended up working out, as I not only went Saturday to attend the lecture as I had planned to in the beginning, but went Sunday to attend one of the free panels as well.  Though, being in the marketplace for two days didn't help my budget much.  But let me start from the beginning here.

In General
At first, I wasn't too sure about this event.  I walked around the marketplace first, saw projects I liked, but not a lot of yarn caught my eye.  Contrasting that to Rhinebeck where I saw tons of yarn I liked, it was a little disheartening at first.  I'm thinking that part of the reason was that I was trying to be more cautious with my money and space (in contrast to Rhinebeck, where I didn't have a budget or space constraints), and therefore only glanced at all the nice cashmere and silk yarns that are at these events.  The other was that the projects I've been thinking of doing were more warmer weather projects, and a lot of the yarn was cold weather stuff (on top of that, none of my project ideas were solid 'I'm doing X' things, which didn't help). The third is that this seems more geared towards the fashion-forward crowd, whereas I'm picky about what I like and it usually isn't popular (for example, I really didn't see any colors I like that wasn't some brand name yarn I can get elsewhere for the same price if I want it).  Also, I was hoping I'd find buttons for my baby sweater, but there were very few button sellers.  I don't think it helped that I've been in a weird mood for unrelated reasons. 

However, there were some interesting thing there.  As I said, I did see a couple of projects on display that I loved as a project, though I wasn't interested in the yarn used.  One of the vendors had a nice shrug with a stockinette body and cabled collar, with mid-length sleeves.  I fell in love with it the first time I saw it.  However, the yarn used was some weird yak/wool blend which wouldn't have worked for when I needed the shrug (I have a event in June that I was thinking of making a shrug for), the color choices didn't thrill me, and the yarn wasn't cheap either.  As far as I could tell, the pattern itself wasn't on sale.  The other projects I saw was just displays of patterns from magazines, and the last thing I need is a magazine subscription.  Something to think about, but nothing to do.  At first this bugged me, but now it doesn't.  I have food for thought, at least.

The Lecture
I scheduled myself to go to the 'Passionate Knitter Takes the Next Step' by Jo Packham, mainly because the time worked for me.  However, having played with this blog and the idea of trying to design more complicated patterns, I was thinking it may be helpful.

Now, don't get me wrong, the talk was interesting and Packham was funny and entertaining.  However, the talk was geared more towards those really trying to break into the industry as writers and entrepreneurs, and so a lot of the advice wasn't useful to me.  I was thinking I would get more advice on blogging, designing, and other quirks in the knitting world as a means to itself, not as a tool to market a brand so one can freelance as a creative person. I blog, design, and otherwise knit because I enjoy it and want to share, not because I'm looking to make it my job or use it to break into another job.  Hell, I think there's one person who actually knows who I am, who also knows I blog about this stuff.  I know there's very few people who know how much I truly lurk in the knitting world (and I mainly lurk.  That's what needs to change first, I think).  I guess if the lecture did anything, it showed me that I'm a lot more out of the knitting world than I was thinking, and that's ok with me.

Fashion Shows and the Panel
I found the fashion shows by accident; I just happen to be walking by when one was going on, and decided to watch.  I didn't think I'd be interested, but it ended up being one of the better things about this event.  I say that despite the fact that I am horrified at the trends coming up in the knitting world.  Maybe that's why I did enjoy it.  Because I'm horrified.

I first caught part of the Trendsetter fashion show.  I've never heard of them before this event, and their line of yarns seem to consist of, what's it called, specialty yarns?  Ribbon yarns, sparkly yarns, bobble yarns, all sorts of demented not-yarn yarns.  I was under the impression that specialty yarns were what they tried to spring on new knitters (I know that my learn-to-knit book had more than enough projects made out of Fun Fur.  Why certain people think fun fur and the like is appropriate for beginners is beyond me).  That they're the yarns big box stores sell to one in a blue moon hobby knitters.  But here they all, bobbles, sparkles, and all that jazz, in projects that models are wearing down the runway at a major knitting event.  I don't think I need to tell you that I've never liked such yarns or styles.  I wasn't happy that they seem to be picking up again, despite the fact that I shouldn't be surprised.  After all, when did those ugly fir vests, boots, and hats start selling in department stores? Last year?

Anyway, I decided to stick around and watch the next show (despite the fact that, at this point, I was tired and hungry).  This show was for Skacel, which is another company I've never heard of.  The good thing is that they didn't overdo the specialty yarns.  The bad thing is it seems like the next knitting trend is modular knitting, at least according to this company.  I'm not a huge fan of the 'bunch of squares put together' look outside of some afghans; it was one of the reasons I've gotten into knitting over crochet for such things.  They didn't change my opinion.  Another trend they used was weird garment shaping.  Now, I'm not automatically against unique shaping, but not like this.  These garments had bat wings, sweaters that looked like bags with cuffs, weird cowls attached to the garment, that kind of thing.  Yes, I like knitting rectangles too, but I rather deal with garment shaping than wear a rectangle.  Again, some of the stuff here was just reflecting store trends that I hate.  Oye.  However, there were a couple of things I didn't mind, and I have to say that swing dress is pretty neat, though I'd probably never wear such a thing if I knit it.

After this show I left to get food and go home.  That would have been the end of my Vogue Knitting Live trip, except I guess I enjoyed see all the bad fashions more than I thought, as I found myself looking at the Sunday schedule and going: 'Oh, I could go see the Vogue Knitting show at 2.'  So, I came back on Sunday in the afternoon to see the what Vogue Knitting was offering.

I have to say, while there was maybe one thing I would actually want to really wear (maybe two, if I modified the second a bit), they were a lot saner than the other shows.  There were several garments I was going: 'Oh, that looks really interesting, I wouldn't mind knitting something like that.' or even 'Hm, I wouldn't do that but that's an interesting idea.'  Of course, there were a couple of things where I went 'What the hell?', mainly a long, weirdly shaped cardigan with a long twisted attached cowl in the front (at least the other garments with cowls in this collection were not attached).  Also, cowls in the summer?  Summer ponchos?  I don't get these trends.

After this was a panel on knitting as a career, which was the second reason I went back on Sunday.  As I thought, it was interesting and amusing to hear the stories of people, some whom I've read their blogs, or just names we all have heard around the knitting world, tell their stories on how they ended up doing it for a living. 

Purchases
Despite wondering around the marketplace for hours on Saturday because nothing really caught my eye, I did end up buying some yarn (of course):

This will be for a baby sweater for that baby I've been making the other things for (which, I should mention, one good thing about this event was all the knitting time I had during and between shows and events.  I got the baby hat done. Also, being surrounded by people knitting during shows was great).  I picked this yarn because it's 1) cotton and 2) wasn't in the classical pastel blue/pink colors and 3) I've never seen a colorway like that red/orange one, and I thought it'll be interesting, especially since I still don't know the baby's gender, and while I'd have no issue putting pink or flair-y things on a boy or blue on a girl, my relatives would.  So, I thought the red/orange combo would be gender neutral enough, in a short-sleeve cardigan with stripes (or maybe with sleeves, not sure yet).

When I went back on Sunday, I had plans to not buy anything else.  Not only did that not work, I also manage to make an ass out of myself.  Here's what happened:

1) As I was walking around the marketplace right before it was set to close, I passed the Knitty City booth. At the Knitty City booth were two knitwear designers with books out, both which I've heard of but never owned their books.  One happens to be a known designer who I: 1) have favorited patterns on Raverly for but never got around to making, 2) have read their blog since they were featured in Brave New Knits, and 3) just released a book I was just looking at on Amazon as something I may be interested in. 
2) I go up to the known designer's table and say 'oh, I was just looking at this book on Amazon', hereby throwing all proper social introductions out the window.  I pick up the book and start looking through it.
3) After some niceties about the book with a Knitty City staffer, I get told that the author of said book is sitting at the table (which I knew).  I go 'Oh, yes, *mumble, mumble, looking at book not people*, I know, I hang around the Internet.'  At this point I then realize that I: 1) failed to maintain proper social etiquette from the get go, 2) didn't make much sense to anyone else but myself, and 3) now sound like some deranged stalker.  Author has smiled at me, but not said anything but hello.  Unsure what to do, I just keep looking at book.
4) Knowing that there was no graceful way out now, I ask how much book is.  Another mistake.  Knitty City employee flips over book and reads price off of back (duh).
5) I ask to buy book, hand book I'm holding to author.  I still haven't bother explaining myself about the internet comment, or saying anything like 'Oh, I've read your blog' or anything to that nature because I'm afraid of sounding more like a crazy idiot.
6) At this point, another person reads my name tag and asks about where I live.  I tell her that I just moved.  Turns out, she lives in the same 'hood and informs me that there are a lot of knitters there and they meet up.  I mention that I 'didn't know that because I didn't find it on the Internet' (why did I say that?), and I live on the other side of the 'hood from the place she was pointing out they meet.  She did at least tell me a Raverly group for knitters in the area. I make mental note to check it out.
7) Author hands book back.  I say thank you at least two times.  Author thanks me.  I look around and bow away from table to pay for book.

So, the end result is that I bought something completely unplanned, and there's a well known designer who may think I'm a complete idiot. Oye.  But, hey, I have a signed knitting book, and the note is very nice despite my, um, behavor.  And there are a couple of patterns in there I would love to do once I get the time and money.


Conclusion
I had fun, believe it or not.  Even it was the 'hey, let's see what absurd thing we can see today' kind of fun.  It also made me think about what I'm doing as a knitter, and where I want to go with my hobby.  That's something I'm still thinking about, though it did lead me to do yesterday's post.  Because, honestly, I know I'm talking to myself right now.  I don't really participate in the knitting world.  I just lurk, and think that's enough.  What this event let me see is that it's not enough.  Even if I sound like an idiot at first, I need to participate more, talk more, share more.  Because, after all, one of the things that attracted me was that there is a 'knitting community'.  That's impressive in its own right.  And I don't have to make it my job to participate, though I have to keep in mind that I am a budding intermediate knitter/crocheter and not a designer, despite the fact that I have two designs on this blog.  They're basic; I haven't done anything yet.  However, the other fact is that I can learn to be a hobby designer, but I can't rush the process or do it alone.  My goal, therefore, is to get to a point where I do have some better designs, and to not get frustrated when my fantastical ideas that I have right now don't work at first.  To sit down and do, instead of dream, and to do for the knitting community.

Also, I hope that for next year, I can afford a class or two.  Because I think one of the better things about this event is the classes, and honestly, they would have helped me a lot more.  But that is life.

Oh, and I do have pictures from the event, but they're on my phone, and I'm not sure if I'm allowed to share them, as most of them are of one of the shows.  Sorry.

I Know, I Know...

I actually had a whole post planned revolving my completion of the Bucket and Brims hat remake, since I realized that it would be a perfect segway into my one major mistake when I was learning to knit, but then life got in the way.  I'll still get around to that post, but it's not going to happen any time soon.  Sorry about that.

Quick updates: I did get all the hats I needed to done for the holidays, and the recipients liked them, so that's a good thing.  I'm currently finishing up my first baby sweater for this other baby on the bus right now (sorry, don't have a picture).  I should be done tomorrow (minus the buttons...which will have to wait because I have a ban on myself from buying any craft stuff right now).  I did change the sleeve length to short sleeves since this is supposed to be a late spring baby in an area of the country that gets pretty hot. 

Then I'll have nothing to do on the bus for the rest of the week.  Then I won't need it.  That's all I'm going to say for now.  I'll try to get back to really posting when my life settles down. 

A belated happy holidays to everyone, and have a happy new year.

The Milk Maiden Write-and-Dash

Since I can't seem to actually sit down and write something when I have time on the weekends, here's the promised notes from my experience with making the Milk Maiden pullover, plus some other observations.

The Sweater
Well, it was an interesting knit.  It came out nicely, but I ended up winging a lot of little changes, despite the fact that I actually took the time to sit down and plan out how I was going to shorten this sweater.  This is because it has an odd construction in the sleeve area and is shaped.  I don't have much of an issue with shaping.  I was worried about screwing up the sleeve construction, having never done something like it before (it involves doing half the sleeve, and then attaching the sleeve to the sweater by decreases, which creates the sleeve cap.  It also means that the sleeve width is the height of the sleeve, something I figured out a tad too late).  However, I did manage to get the sleeves on mostly right.  Yay me.

Oh, and while I was stupid and didn't write every change I made down, I did get a good chunk of them onto my Raverly for this project (the details may be a little lacking, but heh).  But since I'm being lazy, I'm not linking.  My profile link's on the side bar if you're really interested.

The Yarn Used
Madelinetosh yarn....oh, I love your colors, I love the way the color looks in this sweater, but you bleed, and bleed, and bleed!  I set you in vinegar three times, I put so much into the water that it had to be half vinegar, but every time I took you out of the vinegar, you still bled!  How do I set your pretty colors?  How?  Three times I've had to block projects made out of you, and all three times I couldn't stop the yarn from bleeding. Oye.

Other Observations
1) I actually saw someone knitting on the subway a week or so ago.  I've never actually seen someone else knit in public, and here was this woman sitting on the crowded subway, merrily knitting away.  I tried taking a sneaky picture (yeah, I know, it's a little creepy), but the camera in my phone sucks and the subway was too crowded.  (I should note that I don't knit on the subway since I have a very short ride on it).

2) I then finished a hat (it is a present) and a short scarf (probably will be a present) with the alpaca from Rhinebeck.  I now have another hat to do (another present), maybe another project that will also be a present, and a bunch of baby stuff since I now have another relative that's expecting.  I would usually be 'yay' happy about the baby stuff, but I was kind of hoping to start on a cardigan for myself.  You know, so I stop wearing the same store-bought one to work every day.  Oh well.  It'll give me a chance to clear out some of the baby yarn in my stash, given that I'm not over-estimating my knitting abilities again (Which I am.  Can I really do two sweaters after a hat and [retracted] before buying some nicer yarn to make a nicer baby sweater?).

3) I really want to know where the phrase 'sharpen your knitting needles' came from.  My mom said it to me when announcing the baby news.  I've never heard that before, and I've never heard of being able to sharpen your needles.  Probably because I use metal ones.  A web search for another day.

Internal Rules and Current Projects

I know I wrote last time that my next post would be on something different.  That was last week.  I'll get there at some point, I promise.

For now, however, I'll cover something that's currently on my mind, and in the meantime cover what I'm working on now (as well as a couple of past projects).  Therefore, I present the first set of my Internal Rules for Knitting.  These are some rules that help keep my knitting under control, which means they're broken half the time.  Anyway:

1) I will only buy yarn if I have a project in mind for it  After all, this is what I ended up with the first time I didn't do this:

Yeah, that's a current picture of some ugly Lion Brand Swede sitting in my stash

I told myself after that little incident that I would never buy yarn on a whim again.  I would wait until I had picked it for a specific project.  Especially if it was on sale or cost a pretty penny. This would keep my yarn spending under control, and make sure I use what I buy.

However, it also seems that it's quite valid to make an exception when I feel bad about returning yarn to my LYS because I was allergic to it and bought the substitute yarn online.  That's how I ended up with two skeins of this:

The yarn is Madelinetosh's Tosh Light in their Baltic colorway, which I am rather attracted to.  That shawl is the first skein, and came out of the fact that I bought this yarn on a whim.  This, of course, leaves the second skein just sitting there, because while I enjoyed the challenge of learning how to knit lace, I'm not touching it again any time soon. It's this pattern, no modifications. My notes on it here.

It also seems that I'll make an exception I find out some distance relative is having a kid, and I have lofty goals and loads of motivation that I'll make dozens of baby things.  That's how I ended up with all of this:

At least I got a project done for said baby, though it only took one skein of that grey yarn in the back (Bernat's Softee Baby in Gray Marl by the way, though if you can't stand acrylic, don't get it.  It works up like acrylic, though it softens up in the wash)  That sweater is a modified version of this pattern. For notes, go here.

2) I will not spend more on yarn for a project than it would cost me to buy the finished product retail.  This will make my knitting practical, and save me money.  Well, sometimes.  It turns out that an alpaca sweater can retail for $130-140 dollars, which of course is only a little higher than I spent on making this:

However, spending a year and making several projects while twisting your knit stitches is priceless. But that's another post.  This is a modified version of this pattern.  My notes here.

It was also a gift to my mom, so I really didn't care about that one so much.  Given that she's spent more than that making a crochet bedspread that I grew to not like pretty quickly, among other things.  However, it also seems that the rule goes out the window if I like the colorway, which is how I ended up with this:

Project notes are here

This is my current bus project.  The pattern is the Milk Maiden Pullover from Brave New Knits, and it's one of the only reasons I bought the book.  The yarn is Madelintosh's Tosh Sport in their (new?) colorway Fathom. I officially love this colorway. Look at it, my favorite color combination, just slightly variegated enough to be interesting. It's perfect for this pattern too. I had to get it. I don't care if I can get a sweater for $40 bucks and this cost me almost $70, it's worth it. And I'll break rule number 1 if a Madelinetosh Sock onesie pops up in this colorway. Or this colorway gets discontinued. Love, love, love.

And yes, I've modified it, since I modify almost everything.  Why I tend to modify everything is another post, though. Back to the rules.

3) I will use up most of my stash before buying more yarn. Yeah, never managed to follow this one:

Most of my stash. It's a combination of whim yarn and extra skeins from other projects. It lives under my bed and out of my mind for the most part.

The only thing that makes me feel better about that is that it seems that most people I read about online have much larger stashes.  Hey, mine (barely) fits in a Tupperware container. Then again, they seem to have much nicer yarn in their stashes too. Yay?

And now for a rule I'm actually not currently breaking:

4) I should only have one bus project and one at-home project at a time.

First, I'll define what I mean by 'bus project' and 'at-home project'. Bus projects are, obviously, projects that I can do mostly on on the bus. This means that they get worked up faster, but they tend to be simpler. Though 'simpler' is a bit relative, as I have no problem including some sweaters in this pile, as you can see from my bus project above. If it fits in my briefcase and doesn't require either being chained to the pattern or a chart or a lot of color-work, I can usually do it on the bus. Lots of stockinette or very repetitive patterns are a plus here, though I have done drop stitch lace, finishing off projects, and cables on the bus successfully. On the other hand, at home projects are usually things I want to make, but are way too big and/or complicated to work on on the bus. This officially started when I made that lace shawl above, as I realized that in order to make a lace shawl, I was going to need to be chained to the pattern and be able to finish a row in a sitting. I can't do this on the bus without really annoying my fellow passengers. I decided to spare them.

I'm now working on this:

My project notes are here

This is the pattern St. Ciaran from the new and expanded version of Aran Knitting. I'm not really mortifying it (gasp!), though I'm using Berroco's Comfort Worsted to make it instead of a wool-based yarn. This is because I'm making it for my brother, who's still a kid and still trashes things. Therefore, it had to be 1)washable and 2)not too expensive to make. I picked the pattern out, though he approved it. I like torturing myself, though I'm not finding it too hard at this point, just tedious. I should be working on it right now.

I'll go do that.