Showing posts with label stupid mistakes. Show all posts
Showing posts with label stupid mistakes. Show all posts

October 18, 2018

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.

June 22, 2014

Misadventures in Shawls, Part 3: The Pitfalls of Combined Knitting and Stitch Markers

I have to say, despite my semi-laziness in devoting time to working on this, I've gotten pretty far.  Things are speeding up a bit, as I'm well into the part where there's a lot of decreasing going on:

On row 81 yay.

When you hit chart C and beyond, though, it may lose stitches but it gets way more fiddly for a good section of it.   Unfortunately, my tension during that part was shot to hell, and there are stitches and yarn-overs that are small, and others that are huge.

Also, I have two running problems with my stitches at the moment:

1) The markers denoting the repeats are after a purl stitch, which means my purl stitch there is waaaay to loose, as it's eating the slack going around the stitch marker (this is not the first time I've had this problem, but I haven't figured out how to correct it yet other than taking out the stitch marker, which isn't an option here):

This is the back of the work, if you're wondering.

2)   My usual knitting style is a combined style. For me and many combined knitters, this means I knit 'normally', where I twist my yarn around the needle so the right leg is facing the knitter, but I purl in a manner that results in the right leg facing away from the knitter (I've talked about this before).  There turns out there's one issue with that.  When you yarn-over counter-clockwise after or before a stitch that was knitted or purled clockwise, the yarn-over pulls the other stitch down, and makes it really hard to find the right leg of either one.

It took me more than a few rows to realize why my stitches looked screwed up, or where my 'missing' yarn-overs went.  There is several places in the shawl where I knitted the stitch wrongly by working the wrong stitch or side of the stitch.  Luckily, since this always happens near a yarn-over, it just looks a bit messy and the yarn-over is a bit smaller or bigger than normal. I might have ripped it all out when I realized I had been reading those stitches wrong, but I don't have the patience or time for that at the moment.

So, how do you read this mess to work it correctly?

If you have a stitch with the right leg out before a yarn-over, you'll usually see it as this:

Ignore my lovely pajama pants; it might have been around midnight when I took these

The first stitch you need to work is not that string that looks like a loop below the weird twist (that's the stitch below your last one), it's the outer loop tilted away from you here:

Green arrow, not the red

There's the right leg...


So just work that loop as instructed:



Once you drop the stitch, you should be able to see the yarn over much better: 


Work it as instructed, and then you're done with that.


On the other hand...

If you have a stitch with the right leg out after the yarn-over, it'll look like this:

The difference to the set above is that the first stitch you see there is longer and usually angled more to the left, and the twist where the two stitches meet is more towards the knitter (this is because the YO is pulling it down towards the knitter, vs above where it was pulling it away).  Also helps to know where you are in the pattern.

The yarn-over is actually the yarn bar slightly below the needle towards the knitter:



Use that loop to work as instructed:



Once you slip the yarn-over off, then the other stitch will look like a normal stitch (for combined knitters at least).  Work that as instructed.

And that's it.  Now, if there were some easy way to correct those darn huge purl stitches.

March 1, 2014

In Other News, I'm Still Here

So I am a lazy bum who just got out of obsessively watching the Olympics for over two weeks and realized that I haven't written a blog post in over a month.  However, this lazy bum also has been spending half her free time studying for the GRE, and the other half trying to keep up with social obligations, projects, and the fact that she really needs to keep her apartment a little cleaner since a roach decided to chase her out of the kitchen yesterday (I'm no where near a slob and the kitchen wasn't insanely dirty either, but I had been keeping dishes in the sink overnight.  Not that you could ever get a kitchen to a level of cleanness that completely stops them from coming in, over, whatever.  I also have a roach phobia so...yeah).

Anyway, I did get my cardigan done, finally:



Of course, this was after I ripped out the collar three times on top of all the stupid little mistakes I make while knitting.  My swatch lied, or otherwise I was blinded with my love of this yarn, this pattern, or both, because when I blocked it the thing grew.  Not massively, but enough that it felt like it was just hanging on my shoulders, with a huge neckline and floppy collar.  Also, I spaced the buttons out too far and they were gaping.  After throwing it into a corner and sleeping on it so I didn't rip the whole thing out in spite, I ripped out the collar and button band.  I then ripped out three rows of the back before realizing that that section was the only one with live stitches and now I had to pick them back up (which didn't work 100% -- there was an unexplainable gap where the extra yarn hung out at the end of the live stitches and the start of the bind-off -- but I was able to hack it enough and the collar hid it anyway).  Once I fixed that, I decided to go down several needle sizes and re-knit it with new yarn (well, that wasn't a choice because I murdered the yarn when I ripped it out).  Along the way I decided to put one more button and less spaced out, and put less decreases in the collar.  The first thing worked (though I did bind off a bit too tightly), the second thing didn't.  Collar was now too small.  So I ripped that part out again, added more decreases and knitted over the short rows a bit more so the fronts were bigger.  That produced a do-able collar, though I had to sew it down to keep it folded.

I'm still not completely happy with it; it really needs a tighter gauge (damn worsted weight acting like a DK), one button band is slightly tighter than the other, and the collar isn't exactly what I would like...but it does fit more or less now and is extremely warm.  Oh well.  Shit happens.

I probably should do a proper debrief, but right now it's 11pm and I'm tired, so I'm off to bed instead.


November 23, 2013

The Tale of a Broken Needle, Part 2, Or Why You Shouldn't Switch Needles in the Middle of a Project

The good news is that I finished my Mom's Hanukkah socks with time to spare:


The bad news is that, contrary to every other sock set I've knitted so far, the second one came out a bit bigger than the first:

 
Which sucks because the first was the perfect length.

Now,  I know I did the exact same thing for both of them.  Thing's like these types of cable, lace, motif, whatever patterns make it easy to write 'stop at row x' and to do so, since you're keeping track of rows and can see where you are via the pattern.  No, I'm pretty sure the difference in size is due to the fact that I had to switch needles to knit the second sock.

If you go back to this post, you'll see why that was unavoidable.  However, you'll also note that I mentioned that my gauge shouldn't be that different with another pair of nickel-plated needles.  So, I got all excited and ordered new sock needles for that size:



And just cast-ed on and went, conveniently forgetting that my analysis was based on the fact that the Knitter's Pride Nova needles and the KnitPicks Options are very similar (I wouldn't be surprised if the same manufacture makes them).  What isn't that similar are those Addi's I decided to buy because ooh, needles made for Magic Looping socks!  Must have!

So I failed, and now have two slightly different sized socks: one with a gauge of  11.25 rows per inch and another with a gauge of about 11.75 rows per inch.  And it's not like I can just rip back and adjust it so they're the same length because of the pattern; it'll be very obvious if I did that.  So...it is what it is and hopefully my Mom doesn't mind.

Of course, what I should have done, had I not been blinded by nice, new needles, was go buy the same needle brand.  But what's done is done, and it's not that far off that they're unwearable (and it's better to be bigger than smaller).

Since one of the reasons for this blog is learning from my mistakes, the moral of this story is that you should never switch needles in the middle of a project if you can help it, unless you're able to adjust for it.  And if you do have to, use the same exact needle brand and type (I shouldn't have to mention they need to be the same size too, right?).  Because your gauge really does differ between each needle, no matter if they're made of the same material, no matter how slightly, and that can be the difference between a perfect fit and slightly too big or tight.

On the other hand, the Addi Sock Rockets are really nice needles, and I loved working with them.  May have been worth it.

October 30, 2013

So I Went to Rhinebeck and Brought Back More Photos of Cats Than Yarn (Rhinebeck Debrief 2013)

I said I was going to post about Rhinebeck and...I don't know what to talk about.  I re-read my post from last year and realized that my experience was pretty damn similar.  I went upstate, stayed with family, went to the fair, had a fun time, and went back home.  It was great but it was pretty much a repeat of last year, minus the class I took then.  I didn't take a class this year, so I can't even talk about that.

So, I guess I'll just picture dump then (not that I have many good ones.  I seriously have just as many pictures of cats this year, and none of the yarn):


The view from the porch of the building my sister's apartment was in (slightly north of Duchess County).  Pretty leaves. Still loooove the fall upstate, though it was freezing cold both mornings (it was better during the day).  Dunno what was going on at that church over there though.


Crappy picture; got taken through my windshield
The billboard on the way to the fair!  They seem to use the same design every year, though this is the first time I got a picture.  I shouldn't have been on 9G anyway (the billboard is at the intersection of the road from the Kingston-Rhinecliff bridge (it's also a highway, but I forgot the name) and Rt. 9G.  It's meant for people coming from the bridge, which is why it's at a weird angle here)  Turns out you can drive straight down Route 9 through Red Hook to the Fairgrounds.  Duh.  I turned in Red Hook, got on 9G, and got stuck in all the traffic coming off the bridge to the fair.  Took me 30 minutes to get through it.  On the other hand, when I went Sunday, there was no traffic and I got there early because I was expecting to crawl for at least 10 minutes.

I got to the fair with plenty of time though, and got to see everything this time, more than once (several times in some cases...hey, you miss stuff the first two times). Saturday was crowded (figures with all that traffic), so I did more looking than shopping that day, though my mother and I are a bad influence on each other and so we both ended up with unplanned things that Saturday (favorite quote from her this year: 'I'm buying so  many things for myself this year and not for other people!'  I told her that was a good thing, that she should make stuff for herself).  Sunday I ran around with my sisters, and bought most of the yarn I wanted.  I also convinced my poor college student of a sister that she had to buy some yarn there, he he he.

For some reason, I have no pictures of the actual fair, but a few of sheep:




...and a llama (llama llama duck.  You're welcome for the earworm):


Wait, I took this bad picture of a shawl I really liked and want to knit:


I did buy yarn to do it at the fair, and by buy yarn I mean I bought a skein of heavy laceweight dark blue yarn to go with some royal blue fingering weight yarn I bought two years ago and still haven't used...for a sport weight shawl.  Oops. All sorts of fail there.  For some reason I thought that vendor only sold fingering weight yarn.

Of course I then went a bought what ended up being three skeins of sport weight yarn for a fingering weight shawl I've wanted to do since Phil Plait,of all people, linked to the Ravelry page for it, because of course Socks that Rock Mediumweight isn't actually standard sock weight yarn.  At least that just gets you a bigger 'shawl' (it will most likely go on my wall, not get worn.  It's just awesome).

And before you ask, no, I can't use the yarn I bought for the second shawl for the first and vice versa (well, I could do that first one, but I don't want to).  I need a dark black-blue yarn for the second one and two different colors for the first one.

So...wait, did I mention I have tons of photos of cats? I won't derail completely so I'll just post a few that go with a story about yarn.  Saturday night I spent lazing around my sister's apartment. Of course I had bought some of the yarn I bought that day (not the stuff above.  Other yarn.  You'll see). One of her cats (she has two) first decided it liked the yarn I was knitting with:


And then decided it wanted to get the new yarn in my bag:


And then decided that on top of my yarn and bag was a good place to sleep:

Yes, the socks in the bottom corner are my Crazy Purple Socks.  Had to wear something I made to Rhinebeck...

I eventually moved the yarn to the suitcase so it didn't become cat toys overnight.

On Sunday we did dinner and then I drove back to my parent's place.  Since I was lazing about on Monday as well and never made it to the bus to go back to the city (took off Friday and Monday.  Yay four-day weekend), I took pictures of what I bought:

Lots of gray and black this year

...and then decided to go check out the new yarn store that opened up the next town over this year.  Because Rhinebeck wasn't enough yarn.  Anyway, it ended up being a pretty nice store, and I had a nice chat with the owner since I was the only one there mid-day Monday.  Turns out she had organized a bus trip to Rhinebeck on Sunday, and she also had bought more yarn than she needed (her actual statement was closer to: 'I bought some yarn and then asked myself why I was buying yarn; I own a yarn store').  I also bought a skein of yarn, and signed my mother up for the mailing list because she keeps saying she's going to go check out the store and never does (I also told the owner about her so now she has no excuse). 

After the yarn store, I went to a local park and took more pictures:


I also sat in the island in the middle of the lake and knitted a bit.  Because why the hell not;  I had an hour left on the meter for my car.

And that was my weekend at the New York State Sheep and Wool Festival.  And with the cats.

Next year I'll take photos of the fair instead, I promise.

January 18, 2013

Stupid Human Brain

Pictured below is a perfectly cromulent hat, right?  It looks fine (other than that the needle was taken out already).  It's nine cables, and now has the right number of stitches picked up:


Well, it's not.  I miss-crossed every single cable, and didn't realize it until I started reading the directions for the decreases.  I was too busy trying to knit it on the subway and at lunch to bother really reading the chart.  Oh, don't get me wrong, I looked at it.  I looked at it long enough to memorize what rows to cross on and to see that it was a 5 x 5 braided cable.  But for some reason, I completely mis-read the cable symbols.  For this I have no excuse, as they're not unclear (and there's a symbol key right next to the chart in case they are).  I remember looking at it and thinking I comprehended it, though, so I never took a second good look.

'What else is new?', is all I can say now.  I make this error more times than I care to admit.  I do my quick-read and think I got it, it's easy, I can't possible screw it up...just to see later that I was wrong, and it was in front of me all along.  It's not always that I don't bother reading ahead and assume (which I sometimes do too, but that's another issue), it's more like my brain's putting what I was seeing together differently than what was actually there.  Or maybe I'm not looking with enough attention, and my brain is filling in the gaps so I think I read it. 

It's a funny thing, actually, the way the brain does this.   Most people don't notice, especially when, you know,  it works as intended (that is, we fill in the gaps from what we see and are right).  Humans are really good at seeing patterns and connecting the dots, so good, we'll see them when they aren't there. And this is only one way we can be tricked by our brain (if you're interested about this topic, a good book is Don't Believe Everything You Think by Thomas E. Kida). 

However, knowing about it doesn't mean one stops doing it, especially when one is being sloppy and self-confident.  I'm not self-confident about many things, but at this point, I consider myself a decent knitter.  I don't know everything by far, but the things I know I can do pretty well.  But this sometime leads me to skimming patterns in the interest of time or laziness, and thinking I know what's going on. Or thinking I know something and I really only have a hazy idea (or remembered wrong).  Being a fast sight-reader doesn't help this matter; I can read fast, but if I'm being less than attentive I will think I just read it fast when I didn't really capture everything on the page (and again, the brain connects the dots).  Which is how I get the wrong instructions stuck in my head, follow them, only to find out later that if I had just looked more carefully at the paper, I wouldn't be wasting the time in which I could be knitting my main project ripping out and restarting my travel one.

August 17, 2012

Deadlines and Stupid Mistakes

Bad things happen when you actually start to think about deadlines.  Sure, we've all had them, for knitting or otherwise.  Sure, they're sometimes a good thing.  But it's nice when you can take your time with a project as well.

The latter was my first approch to Crazy Cable Blanket.  You know, this one:



This was mostly to preserve my sanity.  Imagine setting a deadline on that sucker...at best, it would have been so far into the future it'd been useless.  Anyway, a week or so ago, I sat down and calculated around how much I needed to knit if I wanted to get it done by next Hanukkah (which is in the middle of December this year).  A rough estimate concluded that if I knit 4 rows a day, I can get it done by November (which would maybe give me time to smack a border on it.  Because all this time-sink of a blanket needs is more work done to it).

Four rows a day?  How hard is that?

Well, pretty hard, actually.  For starters, there are some days I'm just not really home until late, and I have to go to work the next morning, so forget about staying up to work on it.  Despite what I did yesterday, it's not really a good project to bring to a bar, nor to travel with in general.  Some days, I just have other crap to do, or I just don't want to sit down for an hour and a half and knit, or I get distracted by other things (like now).  Despite this, I'm sticking to my goal of four rows a day, even if in reality it's more like 14 to 16 rows a week (about 2.29 rows a day)  This is because this is the most I've worked on it, and even if I don't quite make my deadline of Hanukkah, I'm at least making visible progress.  Also, I really don't want to be talking about it a year from now. 

Of course, attempting to speed things up a bit has it drawbacks.  Like noticing almost 75 rows later that you did this:



...and, even worse, this:



It figures.  Not only did I mis-cross the easiest cable in the blanket, I noticed it way after I did it.  Not like I'm going to frog half the blanket to fix it, so I'm pretty much stuck with this visible emblem of my stupidity.  Well...I did search for a way to fix it, and there happens to be another way.  However, I'm not so sure I want to try cutting just the right piece of yarn to re-cross the cables. Knowing me, I'll cut the wrong piece and ruin a year's worth of work.  A pre-teen won't care about a stupid mis-crossed cable and I'm just being anal, right?

P.S.: By the way, there should be no more interruptions in my life of the unplanned, life-taking-over, variety...at least for now.  That doesn't exclude laziness in posting, so I'll ask you to forgive me now for infrequent updates.