In software programming, there’s a particular experience that is bug reporting.
There are many forms of this experience. One example: you’ve downloaded a feature package, a library of code, to (re)use. You use it, and some thing is wrong. The behaviour isn’t what you expected nor documented. But you can pinpoint the problem. You start to wonder if you’re the first. You go on forums, boards, scour the web for this report. If you don’t find anything, you go and report the bug. If you’re really good, you report the fix as well. It’s a particular feeling of happiness that you’ve reached a point in understanding of the library, the programming language etc. that you no longer question if you’re wrong.
Likewise, in knitting, there’s an experience that’s similar.
You work on a pattern, you look for published erratas and you start. You knit until you see a problem. You wonder if you’ve read / interpreted the pattern correct, and in the end, you know it’s a bug. You go and look for corrects of it on the publishers site, ravelry, designers site etc. In the end, you think up the solution and go ask the designer if it might be a mistake.
Then you hear back from the designer, and you know, you’ve reached a new level of understanding.
Popularity: 7% [?]
Tags: 1 Comment
1 response so far ↓
[...] except for fixing an errata and adding a visible snap [...]