Curious about tech editing but not sure what it involves?

In this video, I’ll give you a peek behind the curtain.

You'll learn:

  • what makes a good tech editor

  • the tools a tech editor needs

  • the different paths to becoming a tech editor 

BUt first — What is a tech editor?

Take a look at the following "patterns":

Version 1: Cast on 100 stitches. Rnd 1: K2, p2 to end. Round 2: Knit. Continue this way until work measures 60 inches. CO all sts.

Version 2: Cast on 100 stitches. Join to work in the round, being careful not to twist stitches. Rnd 1: *K2, p2; repeat from * to end. Rnd 2: Knit. Repeat Rnds 1 & 2 until work measures 60" / 152.5 cm from cast on or until desired length for scarf. Cast off all stitches.

The first could have very well made it through test knitting, but no good tech editor would let it go like that. They would guide a designer to something much more like the second which is clearer, more consistent in style, and least likely to cause problems for the knitter. That's why a designer hires a tech editor. 

So what is a tech(nical) editor? A tech editor is the writing editor equivalent for knitting and crochet patterns. A tech editor goes through a pattern top to bottom, line by line, checking for errors, inconsistencies, problems, better ways of writing things, and so on. They meticulously go through the pattern with a fine tooth comb; checking stitch counts, making sure the gauge gives the right measurements, looking at wording, looking for deviations from the style sheet. It's a lot of work and a good tech editor is able to do this quickly and efficiently. 

In contrast to a tester, a tech editor does not make the item -- they don't need to in order to check it. Now is testing better than tech editing because they actually work the item? I don't think so. I know of patterns that have been knit thousands of times and suddenly a knitter will find an error. That said, test knitters and crocheters are great for many things. It's helpful to get feedback from makers who come from a wide variety of backgrounds and experience levels. Designers also use testers to generate social media buzz and as a way of getting projects up as soon as the pattern is released which helps with sales. But for all their wonderful qualities, testers should not be used to catch errors. Mainly because testers are usually doing it for free and it would really suck for them if to get a pattern full of errors to knit or crochet. That's going to result in a lot of ripping out and wasted time and frustration. I'd rather see testers get a clean pattern so the knitting process actually mimics the experience a buyer will have. The feedback about that experience is going to be way more useful than feedback about a pattern full of errors. 

Now on to the video!

Note: The structure of the Learn to Tech Edit Knitting course has been updated a few times over the years (we do not have the academy mentioned in the video). Please go visit the course page for the most up-to-date version description. If you are interested in just tech editing crochet, check out this course here.

or WATCH me edit a shawl pattern!