You might not have ever knit a Transcendent Project, but you certainly have knit (or attempted to knit) a Cursed Project. The biggest problem with the Cursed (KUR-sehd) Project is that you don’t know that you’ve got one until you’re already committed to it.
Before I go on, I should make clear that a project being cursed doesn’t mean you don’t eventually finish it, nor does it mean that it’s not a cool project. I did finally finish the skull sock you see in the photograph above, and I even finished the second one. My father, who was the recipient of those socks, is probably wearing them as you read this. A Cursed Project is not an unfinished project. It’s just a project that unravels you as you unravel it.
How do you know you’ve got a Cursed Project on your hands? Ask yourself the following questions:
- Did your yarn snarl before you even finished casting on?
- Do you have to adjust your knitting budget to include a visit to the chiropractor?
- Instead of ripping out your work, have you considered throwing it out?
- Have you reread the pattern for biohazard signs?
- Did you consider handing your knitting over to your cat?
- Does the airlines’ earlier ban on knitting needles make perfect sense to you right now?
- Do those scissors suddenly look like a lot of fun?
If you answered YES to any of the above, you are knitting a Cursed Project, and there’s not a thing to be done about it. No one knows what brings on the curse. Quitting won’t help; the unknit stitches will call out to you in your dreams, slowly driving you insane. It pains me to say it, but there’s only one way to break the curse on such a project.