I'm sure you've planned on this but I would love to see some of the crochet work you made as part of the presentation!
I love the diagrams you included, and more of those or especially works-in-progress pictures could be really great!
love how this shows the parallel of how both fields help you create an end product that you can be proud of and ones that can be useful in a really fun and elegant way! If you do it in an organized way ^_^
I actually attempted to make a small flower that really didn't turn out even though as far as I could tell I followed the pattern. This is a good example of what happens when there are bugs in the code or the code was written in a disorganized way.
ooooooh, what if test swatches are unit tests :O :O :O
When looking at the diagrams (since I haven't used those for crocheting before), my initial reaction is being overwhelmed/confused -- but this is actually a great way to point out that we need to help people understand our documentation that we write about our code, and also use standard patterns so that developers that come after us can understand our code!
I really like the "Writing the program is the easy part" section -- this seems like a good takeaway!
Did anything jump out to you as jargon-filled, tenuous, or unnecessary?
I think once you streamline the thoughts into themes and conclusions it will sort itself out!
And putting the certain examples under those themes will help people understand how they tie in.
The technical or crocheting terminology could seem like a lot but I feel like that could be the point -- as developers we are used to receiving a lot of overwhelming information that we don't understand and then slowly learning it part by part, which is kind of what you are explaining is one of the shared takeaways -- incremental learning/building what you initially didn't understand or have built.
What would you expect to get out of a talk with this title and abstract? Did you feel like this outline delivered on that?
Hmm I think just learning an interesting perspective that could give me fresh excitement or insight into how I approach programming.
Personally as I read your thoughts it feels inspiring to think of how creative, problem-solving, and comfortingly logical both are! The joy of coding! Hehe ^__^
Come to think of it, "creative yet comfortingly logical" is definitely what got me into both programming and crocheting. Hmm.
Would you add or cut anything?
Did anything jump out to you as jargon-filled, tenuous, or unnecessary?
I think once you streamline the thoughts into themes and conclusions it will sort itself out! And putting the certain examples under those themes will help people understand how they tie in. The technical or crocheting terminology could seem like a lot but I feel like that could be the point -- as developers we are used to receiving a lot of overwhelming information that we don't understand and then slowly learning it part by part, which is kind of what you are explaining is one of the shared takeaways -- incremental learning/building what you initially didn't understand or have built.
What would you expect to get out of a talk with this title and abstract? Did you feel like this outline delivered on that?
Hmm I think just learning an interesting perspective that could give me fresh excitement or insight into how I approach programming. Personally as I read your thoughts it feels inspiring to think of how creative, problem-solving, and comfortingly logical both are! The joy of coding! Hehe ^__^ Come to think of it, "creative yet comfortingly logical" is definitely what got me into both programming and crocheting. Hmm.
Any other thoughts?
N/A 🐱 👍 ✨
Your name or handle
Tori Chu