<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Eduardo Puerta on Medium]]></title>
        <description><![CDATA[Stories by Eduardo Puerta on Medium]]></description>
        <link>https://medium.com/@eduardopuertac?source=rss-648f11225c52------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*GSmYAcr8RR3RQmpDnTjXVg.jpeg</url>
            <title>Stories by Eduardo Puerta on Medium</title>
            <link>https://medium.com/@eduardopuertac?source=rss-648f11225c52------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 21:25:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@eduardopuertac/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Notes From Under the Temperature Blanket]]></title>
            <link>https://medium.com/@eduardopuertac/notes-from-under-the-temperature-blanket-c7abb7754997?source=rss-648f11225c52------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7abb7754997</guid>
            <category><![CDATA[data-art]]></category>
            <category><![CDATA[data-physicalization]]></category>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[fiber-art]]></category>
            <category><![CDATA[crochet]]></category>
            <dc:creator><![CDATA[Eduardo Puerta]]></dc:creator>
            <pubDate>Thu, 04 Dec 2025 21:09:42 GMT</pubDate>
            <atom:updated>2025-12-04T21:09:42.818Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This blog piece accompanies a paper I co-authored with Sydney Purdue, which was recently presented at IEEE VIS in Vienna and is available open access </em><a href="https://vis.khoury.northeastern.edu/pubs/Purdue2025StitchingMeaningPractices/"><em>here</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8jRlF_6IhkDvo0T_dZu51w.jpeg" /><figcaption><em>Fig 1: Enrico Bertini’s couch, with pillows Sydney and I made, encoding the time and category activities that went into writing our paper. These will be exhibited at TEI in Chicago next year.</em></figcaption></figure><p>Like many people, I began my crocheting experience during COVID, as I was looking for creative endeavors to occupy some of my time. I had just graduated with my bachelor&#39;s degree from a liberal arts college, where I was strongly exposed to the intersection of mathematics and the arts, and I was directly mentored by wonderful faculty who themselves practiced some of these crafts. That is to say, my conception of fiber arts has always been closely linked with mathematical ideas, and though not data per se, in a way, it feels like they exist in similar planes. Now that I’ve embarked on this PhD journey studying how people think about data, these ideas sprouted a collaboration with my good friend, Sydney Purdue, which, like many craft projects themselves, has been several years in the making. Given that this paper was just presented at IEEE Vis, one of the most important conferences on data visualization and computer graphics, I wanted to reflect on my experience writing and thinking about what has been one of the most intellectually stimulating and fun projects of my PhD career.</p><p>So, to briefly — and not doing it enough justice — summarize, Sydney and I wrote a paper characterizing some common patterns and practices of people who use fiber arts (crochet, embroidery, knitting, etc,…) to encode information, which we call <em>data textiles</em>. One of the most common examples of such a project is a temperature blanket, where each row is a day, and the color of the row corresponds to that day&#39;s temperature. My first exposure to these kinds of data textiles was through the <a href="https://www.adkwatershed.org/wool-water">Wool &amp; Water Project</a>, as part of the Adirondack Watershed Institute, when they had an exhibit at the Traditional Arts in Upstate New York (TAUNY) Center back when I was wrapping up my undergraduate studies in Canton, NY.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F1_BBIqSZIX71030zTcb2Q.jpeg" /><figcaption>Fig. Example of a Temperature blanket made by Sarah Moerdyk, who administers a Facebook group about temperature blankets with more than 96 thousand people as of the time of writing.</figcaption></figure><p>Actually, if you take away anything from this blog post, the community of creators in this space is massive and incredibly dedicated. In general, many folk, both as individuals and as part of organized groups, undertake wonderful creative projects that often address societal issues, the environment, and community. While our paper spans 159 projects with 61 follow-up surveys, the community is very active and much larger than we were able to sample. We recruited people by interacting with subreddits and Facebook groups, by reaching out to local craft store mailing lists in communities spanning tens of thousands of people, and by contacting specific community projects. There are too many to name, but we do want to acknowledge the aforementioned Wool &amp; Water, the <a href="https://www.tempestryproject.com/">Tempestry Project</a>, the work of <a href="https://archivy.net/">Rachel Ivy Clarke </a>(who also provided us with some epistemological guidance), and I’ll acknowledge some local Boston businesses later in the post. Anyways, part of why this project was so compelling to me was that we were not innovating on practices surrounding data encodings, but documenting already existing, interesting things that interesting people in the world are currently doing and have been doing for many, many years.</p><figure><img alt="A knitted white scarf simulates the color of ice. The scarf has large circular holes throughout, arranged in a consistent pattern (diagonal lines of 5 holes), and some of the holes are embroidered with blue thread along the edges. One side of the scarf has a couple of embroidered holes, while the other side has them more frequently." src="https://cdn-images-1.medium.com/max/1024/1*WGeygqWzyXQRI9GJr2TykQ.jpeg" /><figcaption>Fig x. Ice Fishing Blues by Michale Glennon, who leads the Wool and Water Project. This knitted and embroidered piece shows several winters over time, with each hole representing a different year. Holes with blue edges represent winters that, on average, were too warm to host the Adirondack Ice Fishing Derby, underscoring the impact of climate change on local traditions through a melting-ice metaphor.</figcaption></figure><p>With all that, the paper is structured around the commonalities across data types and domains, the creator&#39;s practices and experiences, and the encoding mechanisms of the artifacts themselves. For a more detailed overview of our findings and methods, please <a href="https://osf.io/preprints/osf/eyw2r_v1">read the paper</a>, but I hope this blog provides a little window into my way of thinking and some little details that were maybe too speculative to go into the paper itself.</p><h4><em>Communication is not always at the center of the creation.</em></h4><blockquote>P51: “This notion of what it means to be able to decode the puzzle is fascinating. Rethinking about Bertin and the semiology of data viz, there is a strong emphasis on the reader, but there is something about the being able to read in the first place that holds some significant value (like trust from the creator)”</blockquote><p>One of our participants, who is clearly familiar with some data visualization theory, shared a valuable insight about their experience. Specifically, they discussed the vulnerability of personal data encoded in their craft and who gets access to the key as a meaningful facet of the visualization. While their reflection is specific to their experience, their comment on the relationship between reading, perception, and the creative process applies to many of the works in the corpus. Namely, broad readability is often not the primary purpose of creating these data textiles. Participants are motivated by a slew of reasons, including how they engage with their practices and their personal relationships with data.</p><p>Therefore, early in this project, Sydney and I realized we wanted to frame our findings from the perspective of the creators of the work and their practices, rather than how readers of these artifacts decode the data, or the hierarchy of encoding channels for the medium. Do not get me wrong: many readers reflected on the implications of their data, highlighting interesting patterns, such as the duality between local and global changes of temperature over time. Others explicitly worked on advocacy projects, whose role is about communicating to broader audiences. However, we found that projects take unconventional approaches to traditional data visualization practices, leveraging their medium beyond mere data comprehension. We found that some creators are particularly interested in visual variance and perfecting specific craft skills (so many mentions of color-change and weaving ends), often using color palettes with double-digit numbers of colors (up to 48!) and interesting, varied shapes, even in the face of channel interference. We found that some people use these activities to process emotions, to grieve family members they associate with the data or craft, and make gifts for people they care about — encoding data about meaningful years in their lives.</p><h4><em>There is a strong metaphoric congruence between the domain and the process.</em></h4><p>One of the main themes we identified in this project was the many mentions of time, which were often both relevant to the creators&#39; experience and among the main data domains encoded. While these two ideas of time are partially separate, Sydney and I postulate that there is congruence between time as data and the process of making fabrics. Many descriptions of time throughout history posit the metaphors TIME is a LINE and TIME is a FABRIC, and these conventional metaphors in our language align well with the kinds of projects people create. Namely, there is an inherent sequentiality to the practice of yarn crafts, and a lived temporal experience when making. Crochet and knitting are additive crafts in which creators construct the fabric they are working on as they go, often in sequence. For this, I argue that the time encoding almost feels natural, especially for the temperature blankets, where the temperature of the day being added to the blanket is often the same day it is added (or at least planned to be). The mapping between the data and the process is one of compression, where a full day of temperature data is compressed into some hours of making. While the “day of temperature” is encoded in a spatial dimension through the fabric, our experience of making fabric is so deeply tied to time that this chain makes it feel natural.</p><p>Namely, there is something about crafts that require being linear, additive, and sequential, that pairs nicely with encoding data that also has these properties.</p><p>Similarly, when thinking about encoding a quantity of things that occur frequently, the process of making requires us to encode them frequently. This is also true for encoding size, since large data points result in physically massive fabrics. This congruence makes these artifacts really compelling; it just seems to make sense to encode time with such a medium, and it is pleasing to do so as a creator.</p><h4>Temperature blankets as prototypical examples.</h4><p>Internally, we used the language of prototypes to think about the kinds of projects and how to categorize them among ourselves during the coding process. Specifically, a prototypical example of a category is the most common image that comes to mind when thinking of that category. For example, a prototypical chair might be a wooden dining chair with four legs and a backrest, even if other kinds of chairs can vary in materials and construction.</p><p>This project was strongly influenced by the fact that temperature blankets were the prototypical example of data textiles. This came in handy two-fold. First, we wanted to be inclusive in our definition of data textiles, yet still scope it so it&#39;s useful when discussing them. So in our initial classification of projects, we thought deeply not about what unifying properties are shared across all the examples, because sometimes there were none, but about how much they deviated from prototypical examples of what we considered data forms. This meant, for instance, that some projects that encoded random numbers or theoretical distributions (like the random pattern of this knitted narwhal) made the cut because of how similar they were to potential encodings for other data domains; while literal representations of images (which could arguably be data) felt less useful to describe the concept of data textiles (even if there’s a world in which both are analogous to colored pixels on a screen).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aQGceDZqgR3v9_PRAxJMng.jpeg" /><figcaption>Fig. The speckled skin of this narwhal is determined by generating random numbers, created by Sasha Kopf.</figcaption></figure><p>Second, this is something that we found incredibly useful to categorize projects internally as we discussed the properties and coding schema we developed. Internally, we segmented our corpus into projects that shared weather encodings over time and then projects that shared other characteristics with this prototypical example. So temperature socks and book blankets neither share form nor data domain, but they still both have characteristic traits that unite them with THE prototypical example. This was particularly handy to index the kinds of projects so we could find them quickly when it came to identifying the artifacts, so if you gave me a picture of a project in our corpus, I know where it is on our spreadsheet based on what it shares with temperature blankets. While this did not make it fully into the paper, if you read it and wonder “why are the projects ID’ed with these weird tags (WP, TM, VI…)?” they are shorthands for broader categories about how projects share data domains and encoding schemas (Weather Projects, Tallying Marks, Visualizations — referring to conventional digital visualizations).</p><p>Participants also discussed this themselves! When discussing the motivators for their projects, people explicitly wanted to create alternatives to temperature blankets. We got several “this is like a temperature blanket, but I wanted to give it my own twist” kind of examples that altered in both form and data type/domain. I also believe this is very powerful when I think about my own relationship with creativity when remixing and replicating things with my crafts.</p><blockquote>P37: “This was actually my fourth of five temperature garments. I’ve always been intrigued by the idea of a temperature blanket. I think the idea of having my knitting dictated to me by some random thing in my environment is a lot of fun. But I didn’t feel motivated to make a blanket. I like making wearable garments, so I decided to do that instead.”</blockquote><h4><em>Parting thoughts.</em></h4><p>There is so much to be said not only about the internal insights of the scientific process — which we barely discussed here and included many post-it notes and rolling whiteboards — as well as the larger cultural context in which the research is happening. The history of data textiles is strongly linked with women, feminism, queer folk, and many other communities, and documenting these practices does not exist outside of those contexts. So, while Sydney and I had the opportunity to catalog some of these practices and encodings to communicate to a broader data visualization space, ‘tis but a speck in the greater understanding of the interesting practices of interesting people in the world do; often to advocate for themselves, the environment, and the communities they care about, or for the mere act of creating, immensely valuable in its own way.</p><p>Also, I’d love to acknowledge a few places that helped us throughout this project. Craft stores <em>Hipstitch Brookline,</em> g<em>ather here, and Stitch House Dorchester </em>in the greater Boston area helped us distribute our survey, and we sourced materials for an accompanying workshop from local re-used craft supply stores, <em>Make and Mend </em>in Somerville<em>,</em> and the <em>Rainbow Nook </em>in Jamaica Plain<em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*stvTevmiK_kcUsc-s7X2sw.jpeg" /><figcaption>Fig x. Sydney and I, with our accompanying pieces to the work.</figcaption></figure><p>Finally, the last few timekeeping items for the curious. Throughout the paper, we use the term <em>creators </em>rather than artists, crafters, or makers<em> </em>because these terms either have distinct connotations in the Human-Computer Interaction field or carry baggage in different communities. However, these creators often self-identify with various titles.</p><p>Beyond the pillow I crocheted with Sydney, which will be exhibited at the Griffin Museum of Science and Industry in Chicago for TEI in March, I am currently working on a crocheted scarf that encodes the books I have read over the past year, and I have dabbled in representing graphs/networks with crochet, too.</p><p>Also, I have been reading a bit of George Lakoff, which has strongly influenced how I think about thinking, and comes across in the metaphorical and prototypical frameworks. And yes, one of the case studies in the paper is a scarf that shows Arsenal FC’s results for the 2015–16 season (which, in all fairness, props to Leicester) because, of course, I wanted that to be a case study.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7abb7754997" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>