
Why I built NodeStitch: a data scientist who writes crochet patterns
I built NodeStitch because writing crochet patterns in PowerPoint and then Canva meant doing the same manual steps over and over: typing every round number, renumbering photos, and making new versions of a pattern just to check the stitches. I work in data science, and my brain goes straight to “can I automate this?” NodeStitch is my answer. It uses AI in a few optional places, and it does not write patterns. It helps a designer write their own.
My brain goes straight to “can I automate this?”
I work in data science, and I code. Maybe I’m just lazy, but I don’t think that’s it. I just can’t stand repetitive work, and I think that’s true of most people. I’m probably just more motivated than most to do whatever I can to get rid of it. Whenever something felt repetitive, my first thought was: is there code I can write to make this easier, or to automate it entirely?
A lot of my job was writing code to make my own work and my peers’ work easier. But it was never only code. A big part of it was applying machine learning and AI models to streamline work, like making my peers’ reporting much easier. That meant finding the right models, implementing them and containerizing them.
So that’s how my brain works. Is there a shortcut? Can I make this easier? Can I automate it?
When I started writing patterns and kept running into the same manual steps, my brain went right there.
Where I started: Reddit, then PowerPoint, then Canva
When I first started making patterns, I went looking for the right tool and couldn’t find one. Nothing was dedicated to writing patterns. So I went to Reddit threads to see what other designers were using.
That’s how I ended up in PowerPoint, and I absolutely hated it. I made maybe two patterns in it before a very small YouTuber’s walkthrough introduced me to Canva.
Canva was better. PowerPoint was clunky with images and clunky to move things around in. Canva was more elegant and easier to use for pattern making, mostly because moving things around the canvas was so much easier.
But it still didn’t fix the parts that actually ate my time.
The parts nothing fixed
- Numbering every round. Round 1, round 2, round 3, typed by hand. Even when you copy a line, you still have to change the number.
- Renumbering photos. Add a photo and every photo after it needs a new number. Then you have to fix every place in the pattern text that refers to those photos. It’s double work.
- Checking my stitches. I’d make multiple versions of a pattern just to make sure the stitches lined up and the whole thing made sense.
- Retyping everything. I write my patterns in a notebook first, so every pattern meant typing it all out again.
Here’s how that compares now:
| What I did by hand | What NodeStitch does | |
|---|---|---|
| Round numbers | typed every one, and changed it on every copy | numbered as I type |
| Photo numbers | renumbered every label, then fixed every reference in the text | labels renumber on their own, and linked references follow |
| Stitch counts | made new versions of the pattern to check it | Pattern Review flags a round whose math does not work |
| Notebook draft | retyped all of it | photograph the page and it comes back as numbered lines |
| Etsy listing | copied an old listing and checked I’d changed every detail | reads the pattern, writes it like my other listings, and sends it to Etsy as a draft |
Could I build this?
Machine learning models have come a long way, and they’re my profession, so I also wondered whether I could use them to make pattern writing easier. Stitch counts are basically math, but a lot of people struggle with them.
It started as a simple what if. What if I could build this, and what would it look like? One day I decided to just start and see what happened.
About eight or nine months later, I had software that actually worked, and it solved most of the problems I’d had making patterns. If I was running into these issues and annoyances, I figured other designers had to be too.
I enjoy crocheting, and I enjoy making patterns. But what I really enjoy is bringing an idea to life. The process of writing a pattern is not fun. Honestly, it’s pretty painful, especially when you’ve drafted it in a notebook first. That was a big part of why I wanted to build this.
Stuck in the middle on AI
Data science is my world. I keep up with the latest technology and the latest models and what they can do, and it’s what I’m getting my master’s degree in.
So this is the part I want to be honest about. Some people have pushed back on NodeStitch because it uses large language models in the background. It’s a strange spot to be in: my profession and my favorite hobby are in a real cultural conflict. I’m trying to bring the two together in a way that respects the concerns fiber artists have, without pretending the technology isn’t here. It is, and it’s probably not going anywhere.
Plenty of people are using it to put out fake patterns and fake images and flood Etsy with garbage. But I want to be clear: that’s people, not the models. The model isn’t the enemy. The people abusing this creative space with it are.
It’s like getting mad at a hammer because someone used it to break a window. That isn’t the hammer’s fault. The hammer is a tool, and that’s how I see AI and how I’ve built it into NodeStitch.
Still, the friction is real, and I’ve seen it firsthand:
- I’ve gotten emails from people very suspicious of how their data is used.
- I’ve gotten emails from people suspicious of the tool itself, simply because it uses any AI.
- I’ve had people offer to test NodeStitch and then ghost me completely the moment they realized there was AI on the back end.
That happened even though those features are optional. Numbering rounds and photos, laying out the page and drawing charts all work without them. The AI is in the parts that read your pattern, like reading a handwritten page or Pattern Review, and you choose when to run those.
I’ve also taken extra steps with the features that do use it. Your patterns are never used to train AI models. When a feature sends your pattern out to be read, it only goes to providers whose terms prohibit storing it or training on it. It goes out to get an answer back, and that’s it. Your pattern is your IP, and it stays yours. The privacy policy lists exactly which features send what, and where.
Even with all of that, there’s a lot of friction. I’m in the middle: deep in the AI world for my profession, in a hobby that’s openly hostile to it.
If you want to see everything NodeStitch does and doesn’t do, it’s all written out here.
There’s an iPhone app now too, on the same account. It reads my notebook pages into rows, builds and follows stitch charts, and follows my patterns with a row counter while I’m away from the computer.