Machine Knit Double-Bed Sock: Short Row Heels Without Holes

Let’s face it. Sometimes you just want to knit a plain, no-frills sock — short row heels and toes, nothing fancy. It shouldn’t take more than a couple of hours. But no matter how hard you try, you knit and frog until you’re completely frustrated as you sit and stare at a pile of crinkled yarn and bare feet.

I’m going to show you how to knit what I call the good-enough-4-me heel. Well… eventually… first I’m going to tell you what causes those nasty little holes in the first place.

Knitting is created with one long continuous thread. When the thread of one stitch isn’t connected to the stitches on either side, you get a hole. That’s really handy if you want a buttonhole, but not so good for a sock heel.

Since you form your short row heel on one bed, the trick is to make sure the edge stitches on both beds are connected when you either begin or end your short rows. You can use this method on both Japanese and French machines for toe-up or cuff down socks regardless of whether you knit your heel on the front or back bed.

How To Knit The Good-Enough-4-Me Heel

When you’re at the end of your circular rows, the last carriage pass must be done on the bed opposite the heel. If you’re going to shape your heel on the back bed, the last pass is on the front bed and vice versa. This may mean that the front of your sock has one more row than the back, but that’s okay. It’ll work out — I promise.

On my Superba, my carriages only knit right to left on the front bed and left to right on the back bed. I shape my heel on the back bed so after knitting my last circular row, my carriage is to my left.

After knitting the last circular row, pull the edge needle next to the carriage to hold. See how the yarn running from the carriage runs underneath the needle? This will manually wrap the needle when we knit across.

Now knit across. Notice how the yarn travelled from the non-heel bed and floats across the held needle. That’s the thread that will connect the last circular row to the first row of your short rows on this side.

The carriage is now on the right side.

Pull the needle next to the carriage to hold…

… and knit across. You now have two needles in hold — one on each side. You’ve done two carriage passes and the carriage is back at the side where you started your short rows. For me, that’s on the left.

On the carriage side, notice how the thread from the carriage is laying on top of the edge needle. We want to manually wrap the edge needle a second time, so grab that thread…

… and move it underneath the edge needle so it will manually wrap the needle on the next carriage pass.

Pull one more needle on the carriage side to hold…

… and knit across. See how the yarn is now floating over the two edge needles. Yes, it looks strange, but ignore it. This is exactly what you want.

Now do the same for the other side. Move the yarn underneath the edge needle…

… pull another needle to hold and knit across.

You now have four needles in hold, you’ve done four carriage passes, the two edge needles are manually wrapped, there’s a short float running on top of the two edge needles on both sides and the carriage is once again back at the side where you started your short rows.

That’s the end of the manual wrapping for now. Continue to work normal short rows: pull the next needle to hold on the carriage side and knit across, but when you get to the last needle, don’t knit across yet… you need to end the decreases and start the increases on the opposite side in the same row. In other words, at the same time you pull the last needle to hold, you’ll want to push the centermost held needle opposite the carriage back to UWP. Then knit that row. If you happen to forget, it’s not the end of the world — just push that needle to UWP and knit it off manually.

Continue with the increases until only the two edge needles remain in hold. The carriage will be on the side opposite to where it was when you started your short rows. In fact, it must be on that side in order for this to work. The only way the carriage can end up on the wrong side is if you didn’t hold the same number of needles on each side or if you forgot to start the increases in the same row as the last decrease.

We’re not going to knit those last two held needles until after we’ve switched back to circular. The next carriage pass will be on the bed opposite the heel, so you need to use a one-prong tool to manually move those two edge needles back to WP with their stitches and floats in the hooks. If you just push those needles to UWP on a White/Superba, they’ll knit off before they’re supposed to and that’s not what we want. Japanese machines may work differently, but if you want to play it safe — just push them to WP.

Notice that the yarn coming from the carriage simply floats above the edge needle next to it — just like it did when we held the first needle on the other side. This is exactly what you want. This is the thread that’s going to connect the stitch on this side of the heel to the next stitch on the opposite bed.

Set the carriages to circular making sure that the next pass of the carriage will knit on the bed opposite the heel. Continue knitting the rest of your circular foot or ankle.

It doesn’t matter whether Android is better than IOS

The problem has never been Android. Android is Android and IOS is IOS. They’re just different.

The problem is the device manufacturers and software publishers. For two years I went through a cycle where my Motorola Droid wouldn’t pair with my Garmin GPS. Every software update on one side or the other broke connectivity. Garmin blamed it on Moto and Moto blamed it on Garmin and it was broken more often than it worked.

My two year old iPhone has never failed to connect — not once.

Moral of the story: When it comes to technology, being better doesn’t matter. If it doesn’t work, it really doesn’t matter whether it’s genius or a piece of crap.

For every market, there’s an equal anti-market.

Apple Is Doomed!

Not. The Motley Fool is living up to its name in the Doug Erhman interview.

It doesn’t take a genius to look at the past successes and failures of Microsoft, Google, HP and others to realize that new and different is not always new and better, and certainly not always a consistent measure of the person at the helm.

Me thinks that maybe Erhman should be ousted for not answering the questions with anything of substance.

Has anyone stopped to think that while the pundits are manufacturing doom and gloom out of the rumors about release delays for an imaginary (unannounced) product (iWatch)? Or a CEO that hasn’t wow’d the tech community in two OMG-that’s-way-too-long years? After all, isn’t it obvious that Steve Jobs invented, developed and released all of his cool gadgets in mere weeks or months?

I’m secretly hoping that Wall Street bets the farm on this bit of news and Apple’s stock takes a nose dive. Because I believe that Steve Jobs was a really smart guy… smart enough that in those ten years he was grooming his successor, he may have actually planned for a few surprises to emerge after his death. And I’m still hoping for a chance to redeem myself for not buying Apple at $90.

Trying to make the world a better place…

I challenge all my friends and followers:

  1. In the next 24 hours, I want you to bestow some random act of kindness to a total stranger or someone you don’t know well.
  2. Ask all your friends to do the same.
  3. When you’re done, reply to this post… not with what you did or who you did it for, but how it made you feel.

Go ahead… I dare you!