But, on to iterative development. I got some helpful feedback from Tien after I emailed her that her WeaveTech post was turning out to be very useful for me right now. I had also commented on iterative development on facebook and received a reply from a retired IT friend of mine, Bill who was just on the Alaska adventure with me and my husband and Bill's wife Mary. Mary is a pretty serious knitter, so Bill was able to see how iterative development might apply to a fuzzy goal (I love the bad joke there) such as "become a better knitter". I added that using iterative development, one might decide over time to specialize in 1 or more specific types of knitting. The beauty of it is that that decision would not have to be made right up front, or even ever really. It would just emerge. Anyway, it was helpful to me that Bill also recognized what I was getting at.
So, feeling that the pressure to perform is now off, I assigned a particular area of endeavor to each of the 5 weekdays. Of course, this is flexible and subject to change, but it ensures that I don't get stuck on any one project or type of work. For the moment, Friday is beadwork day. Today I made a new neckpiece for a much-loved elaborate locket. The previous neckpiece had broken twice. I'll fix something once, but if it breaks again, it clearly is a design that isn't working well. I also didn't want to spend a lot of time on it. I had earlier made a multi-strand ribbon neckpiece with a beaded clasp for a similar locket, so I used that idea for a variation for this locket. Done. What I learned is that my beading skills are a little rusty. Surprise, surprise.
Dinner was Trader Joe's lasagna. But, I think I've found a scarf pattern for my skein of qiviut.
No comments:
Post a Comment