Saturday was my 20th #Wikipedia editing anniversary.
I have created: * over 25 content articles (that have survived), averaging just over 1 per year * over 100 redirects to make it easier to find pages, and to find topics which are only documented as sections of existing pages.
I have had quite the range of experiences editing and creating articles.
Many of my contributions to pages eventually disappeared after iterative edits or outright rewrites. I have seen repetitive wiki edits, repeatedly undoing changes made.
I have also seen others build on my edits, sometimes taking a correction I made and expanding upon it, with more citations, more details, or both.
Over time I learned various techniques, or patterns for editing, especially for creating new pages, to increase their chances of survival, while also discouraging vandalism or other attacks. I have found ways of writing that somehow get other editors to show up and help defend articles.
If I could summarize it in a few words, I'd say aim for short, boring, and factual content (with high-quality citations). New articles work best when they’re similar to and based on existing well-established articles, no matter how small.
I have learned that it is possible to defend the accuracy of an article even if you are outnumbered, by accurately documenting erroneous additions or changes on the article’s :Talk page, along with calm and thorough refutation of those erroneous additions. Doing so makes it much easier to revert any similar changes, and point to the pre-existing analysis on the :Talk page to discourage repetitive edits.
Wikipedia has a fascinating set of rules, guidelines, and mechanisms for working in the open, and especially in the context of attacks by all sorts of bad actors, whether griefers, or politicians and businesses scrubbing (or self-promoting) their image.
I believe every open source project and open standards organization can learn from how Wikipedia works and thrives, especially in the face of antagonists large and small. I certainly have.
If you do not have a Wikipedia account, I recommend creating one and using it to edit so you too can learn firsthand. Make an account, then browse your areas of interest or expertise to see if you can find pages to improve. Be bold.
I was proud to add the 20 year editor badge to my User page.
{
"type": "entry",
"published": "2025-10-27 21:30-0700",
"url": "https://tantek.com/2025/300/t20/wikipedia-editing-anniversary",
"category": [
"Wikipedia"
],
"content": {
"text": "Saturday was my 20th #Wikipedia editing anniversary.\n\nI have created:\n* over 25 content articles (that have survived), averaging just over 1 per year\n* over 100 redirects to make it easier to find pages, and to find topics which are only documented as sections of existing pages.\n\nThis year I\u2019ve created five content articles (so far). Most recently:\n* https://en.wikipedia.org/wiki/Governors_Public_Health_Alliance\n* https://en.wikipedia.org/wiki/RaptureTok\n* https://en.wikipedia.org/wiki/Northeast_Public_Health_Collaborative\n* https://en.wikipedia.org/wiki/West_Coast_Health_Alliance\n* https://en.wikipedia.org/wiki/Take_California\n\nI have had quite the range of experiences editing and creating articles.\n\nMany of my contributions to pages eventually disappeared after iterative edits or outright rewrites. I have seen repetitive wiki edits, repeatedly undoing changes made.\n\nI have also seen others build on my edits, sometimes taking a correction I made and expanding upon it, with more citations, more details, or both.\n\nOver time I learned various techniques, or patterns for editing, especially for creating new pages, to increase their chances of survival, while also discouraging vandalism or other attacks. I have found ways of writing that somehow get other editors to show up and help defend articles.\n\nIf I could summarize it in a few words, I'd say aim for short, boring, and factual content (with high-quality citations). New articles work best when they\u2019re similar to and based on existing well-established articles, no matter how small.\n\nI have learned that it is possible to defend the accuracy of an article even if you are outnumbered, by accurately documenting erroneous additions or changes on the article\u2019s :Talk page, along with calm and thorough refutation of those erroneous additions. Doing so makes it much easier to revert any similar changes, and point to the pre-existing analysis on the :Talk page to discourage repetitive edits.\n\nWikipedia has a fascinating set of rules, guidelines, and mechanisms for working in the open, and especially in the context of attacks by all sorts of bad actors, whether griefers, or politicians and businesses scrubbing (or self-promoting) their image.\n\nI found this article on Wikipedia\u2019s systems and their resilience particularly inspiring:\n* https://www.theverge.com/cs/features/717322/wikipedia-attacks-neutrality-history-jimmy-wales\n\nI believe every open source project and open standards organization can learn from how Wikipedia works and thrives, especially in the face of antagonists large and small. I certainly have.\n\nIf you do not have a Wikipedia account, I recommend creating one and using it to edit so you too can learn firsthand. Make an account, then browse your areas of interest or expertise to see if you can find pages to improve. Be bold.\n\nI was proud to add the 20 year editor badge to my User page. \n\nhttps://en.wikipedia.org/wiki/Template:User_Twenty_Year_Society\n\nIt\u2019s never too late to start.",
"html": "Saturday was my 20th #<span class=\"p-category\">Wikipedia</span> editing anniversary.<br /><br />I have created:<br />* over 25 content articles (that have survived), averaging just over 1 per year<br />* over 100 redirects to make it easier to find pages, and to find topics which are only documented as sections of existing pages.<br /><br />This year I\u2019ve created five content articles (so far). Most recently:<br />* <a href=\"https://en.wikipedia.org/wiki/Governors_Public_Health_Alliance\">https://en.wikipedia.org/wiki/Governors_Public_Health_Alliance</a><br />* <a href=\"https://en.wikipedia.org/wiki/RaptureTok\">https://en.wikipedia.org/wiki/RaptureTok</a><br />* <a href=\"https://en.wikipedia.org/wiki/Northeast_Public_Health_Collaborative\">https://en.wikipedia.org/wiki/Northeast_Public_Health_Collaborative</a><br />* <a href=\"https://en.wikipedia.org/wiki/West_Coast_Health_Alliance\">https://en.wikipedia.org/wiki/West_Coast_Health_Alliance</a><br />* <a href=\"https://en.wikipedia.org/wiki/Take_California\">https://en.wikipedia.org/wiki/Take_California</a><br /><br />I have had quite the range of experiences editing and creating articles.<br /><br />Many of my contributions to pages eventually disappeared after iterative edits or outright rewrites. I have seen repetitive wiki edits, repeatedly undoing changes made.<br /><br />I have also seen others build on my edits, sometimes taking a correction I made and expanding upon it, with more citations, more details, or both.<br /><br />Over time I learned various techniques, or patterns for editing, especially for creating new pages, to increase their chances of survival, while also discouraging vandalism or other attacks. I have found ways of writing that somehow get other editors to show up and help defend articles.<br /><br />If I could summarize it in a few words, I'd say aim for short, boring, and factual content (with high-quality citations). New articles work best when they\u2019re similar to and based on existing well-established articles, no matter how small.<br /><br />I have learned that it is possible to defend the accuracy of an article even if you are outnumbered, by accurately documenting erroneous additions or changes on the article\u2019s :Talk page, along with calm and thorough refutation of those erroneous additions. Doing so makes it much easier to revert any similar changes, and point to the pre-existing analysis on the :Talk page to discourage repetitive edits.<br /><br />Wikipedia has a fascinating set of rules, guidelines, and mechanisms for working in the open, and especially in the context of attacks by all sorts of bad actors, whether griefers, or politicians and businesses scrubbing (or self-promoting) their image.<br /><br />I found this article on Wikipedia\u2019s systems and their resilience particularly inspiring:<br />* <a href=\"https://www.theverge.com/cs/features/717322/wikipedia-attacks-neutrality-history-jimmy-wales\">https://www.theverge.com/cs/features/717322/wikipedia-attacks-neutrality-history-jimmy-wales</a><br /><br />I believe every open source project and open standards organization can learn from how Wikipedia works and thrives, especially in the face of antagonists large and small. I certainly have.<br /><br />If you do not have a Wikipedia account, I recommend creating one and using it to edit so you too can learn firsthand. Make an account, then browse your areas of interest or expertise to see if you can find pages to improve. Be bold.<br /><br />I was proud to add the 20 year editor badge to my User page. <br /><br /><a href=\"https://en.wikipedia.org/wiki/Template:User_Twenty_Year_Society\">https://en.wikipedia.org/wiki/Template:User_Twenty_Year_Society</a><br /><br />It\u2019s never too late to start."
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "46356142",
"_source": "2460"
}
If you plan to participate in TPAC breakouts, whether in-person or remote, take a look and give the ones that look interesting to you thumbs-up 👍, heart ❤️, or rocket 🚀 reactions.
{
"type": "entry",
"published": "2025-10-27 19:23-0700",
"url": "https://tantek.com/2025/300/t19/tpac-breakouts-reactions",
"category": [
"w3cTPAC"
],
"content": {
"text": "Numerous #w3cTPAC breakout sessions have been proposed. \n\n* https://github.com/w3c/tpac2025-breakouts/issues/?q=is%3Aissue%20state%3Aopen%20sort%3Acreated-asc\n\nIf you plan to participate in TPAC breakouts, whether in-person or remote, take a look and give the ones that look interesting to you thumbs-up \ud83d\udc4d, heart \u2764\ufe0f, or rocket \ud83d\ude80 reactions.\n\nFor more information about TPAC 2025 Breakout sessions and how they work, see: \n* https://github.com/w3c/tpac2025-breakouts",
"html": "Numerous #<span class=\"p-category\">w3cTPAC</span> breakout sessions have been proposed. <br /><br />* <a href=\"https://github.com/w3c/tpac2025-breakouts/issues/?q=is%3Aissue%20state%3Aopen%20sort%3Acreated-asc\">https://github.com/w3c/tpac2025-breakouts/issues/?q=is%3Aissue%20state%3Aopen%20sort%3Acreated-asc</a><br /><br />If you plan to participate in TPAC breakouts, whether in-person or remote, take a look and give the ones that look interesting to you thumbs-up \ud83d\udc4d, heart \u2764\ufe0f, or rocket \ud83d\ude80 reactions.<br /><br />For more information about TPAC 2025 Breakout sessions and how they work, see: <br />* <a href=\"https://github.com/w3c/tpac2025-breakouts\">https://github.com/w3c/tpac2025-breakouts</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "46353855",
"_source": "2460"
}
I quite enjoyed KPop Demon Hunters. Loved the animation style, quite funny, and some good bops. It’s one I probably wouldn’t have considered without a friend’s recommendation, so I’m passing it along.
{
"type": "entry",
"published": "2025-10-27 16:16-0700",
"url": "https://gregorlove.com/2025/10/i-quite-enjoyed/",
"category": [
"movies",
"music"
],
"syndication": [
"https://bsky.app/profile/gregorlove.com/post/3m47kqbph6m2x"
],
"content": {
"text": "I quite enjoyed KPop Demon Hunters. Loved the animation style, quite funny, and some good bops. It\u2019s one I probably wouldn\u2019t have considered without a friend\u2019s recommendation, so I\u2019m passing it along.",
"html": "<p>I quite enjoyed <a href=\"https://en.wikipedia.org/wiki/KPop_Demon_Hunters\">KPop Demon Hunters</a>. Loved the animation style, quite funny, and some good bops. It\u2019s one I probably wouldn\u2019t have considered without a friend\u2019s recommendation, so I\u2019m passing it along.</p>"
},
"author": {
"type": "card",
"name": "gRegor Morrill",
"url": "https://gregorlove.com/",
"photo": "https://gregorlove.com/site/assets/files/6268/profile-2021-square.300x0.jpg"
},
"post-type": "note",
"_id": "46353274",
"_source": "95"
}
{
"type": "entry",
"published": "2025-10-26T01:00:24-0400",
"url": "https://martymcgui.re/2025/10/26/machine-knitting-sleeves/",
"category": [
"machine-knitting",
"sweater",
"KnitFactoryImpl",
"sleeves",
"knitalong"
],
"name": "Machine Knitting: sleeves!",
"content": {
"text": "This post will be part of a series, as I join KnitFactoryImpl's knitalong of a set in sleeve crew neck sweater for channel members. KnitFactoryImpl (aka Carson)'s videos have been a huge help and source of inspiration on my short knitting journey so far, so it's really fun to get to join in and participate!\nI got serious about learning machine knitting just this year, and only just finished my first sweater (which I need to post about!), so I think I\u00a0barely\u00a0qualify to do this project. It uses a combination of techniques that I have used in isolation, like increases, decreases, and short rows, but all together. I recently got an attachment for doing ribbing, which I've barely learned to use, but I want to do ribbed hems.\nAdding to the challenge, I didn't quite know what sweater I actually wanted to make! Thankfully, producer Amy saw some promise in our yarn stash and made a request of a 4-color striped sweater made from some cotton yarn in sorta-trans-pride-flag colors.\nAlways be swatching\nFollowing the instructions for the knitalong, and Carson's evergreen advice, I made gauge swatches for the body, with a couple of different striping options, as well as a sample swatch of ribbing. I used a tension that I've been pretty comfortable working with this yarn so far. We plan to machine wash and dry the finished sweater, so we treated the swatches the same way to see how the fabric turned out.\n\n\nWe were both pleased with how the swatches came out! I think the finished sweater will look nice based on these. More importantly, during swatching I learned that I absolutely do not have it in me to do a 4-color striped knit at the point in my knitting journey! \ud83d\ude05 Until I am able to invest in a color changer, I am going to focus on fewer colors, so we agreed on a pattern of black and purple stripes, evenly spaced at 12 rows each.\nSensing a pattern\nWith gauge swatches in hand, it was time to visit the pattern generator for the set in sleeve crew neck sweater\u00a0and punch in my gauge measurements, as well as producer Amy's measurements for how she wants the final sweater to fit.\nThe resulting pattern is a set of written instructions for each part of the sweater: front and back panels that are worked the same from the bottom but differ as you approach the top, sleeves worked up from the cuffs, and the neckline which is worked as you combine the pieces.\nCarson recommends starting with a sleeve, for many reasons, and that's the topic of her first video for the knitalong, so that's where I started!\nOne does not simply knit a sleeve\nEach sleeve is a journey, starting with a cuff (25 rows of ribbing, in my case), then switching to stockinette (\"regular\") knitting for the long body of the sleeve, with regular increases as you widen the sleeve from the hand to the arm hole. At the maximum width, we're not quite done. We bind off some stitches for the underarm, then do a few different sequences of gradual decreases, and finally some round shaping with short rows, before finishing the piece to remove it from the bed.\nFor this sweater, color stripes would add extra complexity. No matter what else was happening in the pattern, I would need to stop every 12 rows to switch out one color for the other. In theory, the mechanics of each is not difficult - my machine has a little notch at the ends to park one yarn while the other works. But I would have to make a color switch every 12 rows while also following the rest of the pattern, such as increasing every 10 rows. In a way, I would be working two sets of instructions at once. Thankfully, I once again followed Carson's advice and printed the pattern on paper. After much fidgeting and scrunching of my face, I was able to scribble out number sequences until I was pretty sure it would work.\nSleeve time let's go!\nWith pattern in hand, I set up the machine and got to work. I followed my machine manual instructions for casting on 1x1 ribbing at the required number of stitches and knit the cuff. I transferred all stitches to the main bed for the body of the sleeve and knit my first 10 rows to an increase. Two more and it was time to switch colors. Increase again at the next multiple of 10. Then another color change at 24 rows and oh god-\n\n\n\n Knitting machine with the carriage removed and set aside. Most of the knit piece has dropped from the bed with only a few inches still on working needles.\n\n Viewed from below, the weighted cast-on comb dangles at an angle as most of the knit piece has dropped.\n\nI believe I improperly set the yarn in the feeder after changing colors. With the incoming yarn failing to feed, the machine promptly dropped switches from their needles. I was most of the way across the bed before I realized this.\nIn theory, it was possible to save this piece. I used my transfer tools to pick up a few stitches, but between the weights on the work and my clumsy fingers I was going to have to rework a lot of stitches. I decided to cut my losses, unravel everything so far, and call it a day.\n\n Sleeve time, let's\u00a0carefully\u00a0go\n\nThe next day I started again, this time taking extra care to check that the yarn was properly ready to feed whenever I changed colors. Keeping track of all the changes was challenging, and at times during the decreases and short rowing I ended up off by a stitch here or there. But I made it through!\n\n\nAt this point I took a break, cast my ballot in early voting, and enjoyed my afternoon.\nWhat's another sleeve?\nWith one sleeve done, the second was sure to go faster. I felt much more confident in the rhythm of the changes and techniques. I even stopped to take a progress photo!\n\n\nThis photo was taken after the long sequence of increases, which end with binding off some stitches on either end to make a \"shelf\" for the under arm. Completely by coincidence, I took this photo right before I made a horrible mistake.\nAfter the bind-off for the underarm shelf comes a sequence of decreases, at difference cadences. Starting from this photo, I was meant to knit 12 rows, decreasing a stitch on each side each row, followed by a couple of sequences which involved decreases only every third row.\nI got mixed up and did 12 rows at the slower cadence of decreases. \ud83d\ude2d\nI'm not skilled at it, but I was able to \"unknit\" a couple of rows, pulling the previous stitches back onto their needles. I suspected this would become confusing or problematic when I got to the rows where I had decreased, requiring complex moves to \"un-decrease\". However, before I got to that point, the unknitting process was causing stitches to fall off needles entirely, multiple at a time.\nAt this point I needed a new strategy. Thankfully, another of Carson's videos, where she makes this absurdly wonderful wolf sweater, had the answer.\nI removed the weights from the piece and carefully removed the piece from the needles. Then, I found the stitches from the row in the photo above, just after completing the bind-off for the underarm shelf. I carefully re-hung that row of stitches across the number of needles from that row of the pattern.\n\n\nThen I tucked the knitting back in, added weights, and restarted the pattern as if I had\u00a0not completely goofed it.\nAnd... this worked out totally fine! After finishing the piece I went back and unraveled the \"teratoma\" from my miscounted piece. The anomalous row is barely visible, and I think the only side-effect is that I'll have a couple of extra ends to work end during assembly. Whew!\n\n\n Lolly came to help. Ok really she is here to ask why dinner is late.With two sleeves completed, I could not resist asking producer Amy to help me complete a familiar shot from Carson's videos.\nOne sleeve on the machine. Two sleeves on the machine!Next time...\nNeither of these sleeves is perfect, but I think overall they look\u00a0really nice, and the little imperfections will be hidden in seams as it all comes together. Producer Amy is really loving the look so far, and we're both looking forward to how it shapes up after washing and assembly.\nThe body panels are expected as the next pieces in the knitalong. However, I'm not going to have much time to knit in the next couple of weeks! \ud83d\ude05\nI look forward to checking out other folks' progress and a (careful, controlled, certainly not rushed) busy weekend of catching up when I get a chance.\nThanks to everyone involved in making this knitalong possible! I am grateful to be learning so much and feeling like part of a community of folks doing the same!",
"html": "<p>This post will be part of a series, as I join <a href=\"https://www.youtube.com/watch?v=1kntNWiaZVM\">KnitFactoryImpl's knitalong of a set in sleeve crew neck sweater for channel members</a>. KnitFactoryImpl (aka Carson)'s videos have been a huge help and source of inspiration on my short knitting journey so far, so it's really fun to get to join in and participate!</p>\n<p>I got serious about learning machine knitting just this year, and only just finished my first sweater (which I need to post about!), so I think I\u00a0<i>barely</i>\u00a0qualify to do this project. It uses a combination of techniques that I have used in isolation, like increases, decreases, and short rows, but all together. I recently got an attachment for doing ribbing, which I've barely learned to use, but I want to do ribbed hems.</p>\n<p>Adding to the challenge, I didn't quite know what sweater I actually wanted to make! Thankfully, producer Amy saw some promise in our yarn stash and made a request of a 4-color striped sweater made from some cotton yarn in sorta-trans-pride-flag colors.</p>\n<h2>Always be swatching</h2>\n<p>Following the instructions for the knitalong, and Carson's evergreen advice, I made gauge swatches for the body, with a couple of different striping options, as well as a sample swatch of ribbing. I used a tension that I've been pretty comfortable working with this yarn so far. We plan to machine wash and dry the finished sweater, so we treated the swatches the same way to see how the fabric turned out.</p>\n<a href=\"https://media.martymcgui.re/e7/f8/76/c1/d48bc966ddcb57207ab5ec3ddb369db5c00d79539ab9bb5925dd6071.\"><img src=\"https://res.cloudinary.com/schmarty/image/fetch/w_960,c_fill/https://media.martymcgui.re/e7/f8/76/c1/d48bc966ddcb57207ab5ec3ddb369db5c00d79539ab9bb5925dd6071.\" alt=\"Left: square swatch of ribbed fabric in black. Right: rectangular swatch with stripes in black, pink, purple, and blue.\" /></a>\n\n<p>We were both pleased with how the swatches came out! I think the finished sweater will look nice based on these. More importantly, during swatching I learned that I absolutely do not have it in me to do a 4-color striped knit at the point in my knitting journey! \ud83d\ude05 Until I am able to invest in a color changer, I am going to focus on fewer colors, so we agreed on a pattern of black and purple stripes, evenly spaced at 12 rows each.</p>\n<h2>Sensing a pattern</h2>\n<p>With gauge swatches in hand, it was time to visit the <a href=\"https://abstractknitfactoryfactory.com/set_in_sleeve_crew_pullover\">pattern generator for the set in sleeve crew neck sweater</a>\u00a0and punch in my gauge measurements, as well as producer Amy's measurements for how she wants the final sweater to fit.</p>\n<p>The resulting pattern is a set of written instructions for each part of the sweater: front and back panels that are worked the same from the bottom but differ as you approach the top, sleeves worked up from the cuffs, and the neckline which is worked as you combine the pieces.</p>\n<p>Carson recommends starting with a sleeve, for many reasons, and that's the topic of her first video for the knitalong, so that's where I started!</p>\n<h2>One does not simply knit a sleeve</h2>\n<p>Each sleeve is a journey, starting with a cuff (25 rows of ribbing, in my case), then switching to stockinette (\"regular\") knitting for the long body of the sleeve, with regular increases as you widen the sleeve from the hand to the arm hole. At the maximum width, we're not quite done. We bind off some stitches for the underarm, then do a few different sequences of gradual decreases, and finally some round shaping with short rows, before finishing the piece to remove it from the bed.</p>\n<p>For this sweater, color stripes would add extra complexity. No matter what else was happening in the pattern, I would need to stop every 12 rows to switch out one color for the other. In theory, the mechanics of each is not difficult - my machine has a little notch at the ends to park one yarn while the other works. But I would have to make a color switch every 12 rows while also following the rest of the pattern, such as increasing every 10 rows. In a way, I would be working two sets of instructions at once. Thankfully, I once again followed Carson's advice and printed the pattern on paper. After much fidgeting and scrunching of my face, I was able to scribble out number sequences until I was pretty sure it would work.</p>\n<h2>Sleeve time let's go!</h2>\n<p>With pattern in hand, I set up the machine and got to work. I followed my machine manual instructions for casting on 1x1 ribbing at the required number of stitches and knit the cuff. I transferred all stitches to the main bed for the body of the sleeve and knit my first 10 rows to an increase. Two more and it was time to switch colors. Increase again at the next multiple of 10. Then another color change at 24 rows and oh god-</p>\n\n<a href=\"https://media.martymcgui.re/bb/21/78/08/64cb7879e99820741d2d1fa295be5c9f8348eb1117687b61445156c2.\"><img src=\"https://res.cloudinary.com/schmarty/image/fetch/w_480,c_fill/https://media.martymcgui.re/bb/21/78/08/64cb7879e99820741d2d1fa295be5c9f8348eb1117687b61445156c2.\" alt=\"64cb7879e99820741d2d1fa295be5c9f8348eb1117687b61445156c2.\" /></a>\n\n Knitting machine with the carriage removed and set aside. Most of the knit piece has dropped from the bed with only a few inches still on working needles.<a href=\"https://media.martymcgui.re/6c/7b/94/2f/490448b40266b133edac3a08bdc9e7144c82632927665e60fd0e8ac4.\"><img src=\"https://res.cloudinary.com/schmarty/image/fetch/w_480,c_fill/https://media.martymcgui.re/6c/7b/94/2f/490448b40266b133edac3a08bdc9e7144c82632927665e60fd0e8ac4.\" alt=\"490448b40266b133edac3a08bdc9e7144c82632927665e60fd0e8ac4.\" /></a>\n\n Viewed from below, the weighted cast-on comb dangles at an angle as most of the knit piece has dropped.\n\n<p>I believe I improperly set the yarn in the feeder after changing colors. With the incoming yarn failing to feed, the machine promptly dropped switches from their needles. I was most of the way across the bed before I realized this.</p>\n<p>In theory, it was possible to save this piece. I used my transfer tools to pick up a few stitches, but between the weights on the work and my clumsy fingers I was going to have to rework a lot of stitches. I decided to cut my losses, unravel everything so far, and call it a day.</p>\n<h2>\n Sleeve time, let's\u00a0<i>carefully</i>\u00a0go\n</h2>\n<p>The next day I started again, this time taking extra care to check that the yarn was properly ready to feed whenever I changed colors. Keeping track of all the changes was challenging, and at times during the decreases and short rowing I ended up off by a stitch here or there. But I made it through!</p>\n<a href=\"https://media.martymcgui.re/a0/dc/69/ba/c6880d7a4c20cf131cea65814d2f47785ec85dad60083d8e7e46096e.\"><img src=\"https://res.cloudinary.com/schmarty/image/fetch/w_960,c_fill/https://media.martymcgui.re/a0/dc/69/ba/c6880d7a4c20cf131cea65814d2f47785ec85dad60083d8e7e46096e.\" alt=\"Knitting machine bed with a completed sleeve panel in stripes of black and grayish purple. On the right, the ribbed cuff in black yarn pulls inward. Moving left, the sleeve widens and narrows again. At the very left, short rows in purple cause the knitting to curl over.\" /></a>\n\n<p>At this point I took a break, cast my ballot in early voting, and enjoyed my afternoon.</p>\n<h2>What's another sleeve?</h2>\n<p>With one sleeve done, the second was sure to go faster. I felt much more confident in the rhythm of the changes and techniques. I even stopped to take a progress photo!</p>\n<a href=\"https://media.martymcgui.re/e3/e3/9b/6a/af58e502452d8cefa062c2cb8ffb332ccb5c8e0644410a57cae91f83.\"><img src=\"https://res.cloudinary.com/schmarty/image/fetch/w_960,c_fill/https://media.martymcgui.re/e3/e3/9b/6a/af58e502452d8cefa062c2cb8ffb332ccb5c8e0644410a57cae91f83.\" alt=\"Knitting machine with long piece of knitting hanging almost to the floor.\" /></a>\n\n<p>This photo was taken after the long sequence of increases, which end with binding off some stitches on either end to make a \"shelf\" for the under arm. Completely by coincidence, I took this photo right before I made a horrible mistake.</p>\n<p>After the bind-off for the underarm shelf comes a sequence of decreases, at difference cadences. Starting from this photo, I was meant to knit 12 rows, decreasing a stitch on each side each row, followed by a couple of sequences which involved decreases only every third row.</p>\n<p>I got mixed up and did 12 rows at the slower cadence of decreases. \ud83d\ude2d</p>\n<p>I'm not skilled at it, but I was able to \"unknit\" a couple of rows, pulling the previous stitches back onto their needles. I suspected this would become confusing or problematic when I got to the rows where I had decreased, requiring complex moves to \"un-decrease\". However, before I got to that point, the unknitting process was causing stitches to fall off needles entirely, multiple at a time.</p>\n<p>At this point I needed a new strategy. Thankfully, another of Carson's videos, <a href=\"https://www.youtube.com/watch?v=4udlEiD5OC8\">where she makes this absurdly wonderful wolf sweater</a>, had the answer.</p>\n<p>I removed the weights from the piece and carefully removed the piece from the needles. Then, I found the stitches from the row in the photo above, just after completing the bind-off for the underarm shelf. I carefully re-hung that row of stitches across the number of needles from that row of the pattern.</p>\n<a href=\"https://media.martymcgui.re/24/b7/5e/bb/5b29c3e72a1cc4346235ad507e833a8e4af3965cf0788d656761e6d3.\"><img src=\"https://res.cloudinary.com/schmarty/image/fetch/w_960,c_fill/https://media.martymcgui.re/24/b7/5e/bb/5b29c3e72a1cc4346235ad507e833a8e4af3965cf0788d656761e6d3.\" alt=\"The working piece, now without weights, re-hung on the machine. This photo was taken about 90 minutes after the previous.\" /></a>\n\n<p>Then I tucked the knitting back in, added weights, and restarted the pattern as if I had\u00a0<i>not completely goofed it</i>.</p>\n<p>And... this worked out totally fine! After finishing the piece I went back and unraveled the \"teratoma\" from my miscounted piece. The anomalous row is barely visible, and I think the only side-effect is that I'll have a couple of extra ends to work end during assembly. Whew!</p>\n<a href=\"https://media.martymcgui.re/13/16/92/dc/613e91516265d7eaa682b75ea85e3166c76935e5d4a2899f6c75c391.\"><img src=\"https://res.cloudinary.com/schmarty/image/fetch/w_960,c_fill/https://media.martymcgui.re/13/16/92/dc/613e91516265d7eaa682b75ea85e3166c76935e5d4a2899f6c75c391.\" alt=\"Finished sleeve resting on the knitting machine bed. A cat is beside the machine, staring up at the camera as she climbs into a chair.\" /></a>\n\n Lolly came to help. Ok really she is here to ask why dinner is late.<p>With two sleeves completed, I could not resist asking producer Amy to help me complete a familiar shot from Carson's videos.</p>\nOne sleeve on the machine. Two sleeves on the machine!<h2>Next time...</h2>\n<p>Neither of these sleeves is perfect, but I think overall they look\u00a0<i>really nice</i>, and the little imperfections will be hidden in seams as it all comes together. Producer Amy is really loving the look so far, and we're both looking forward to how it shapes up after washing and assembly.</p>\n<p>The body panels are expected as the next pieces in the knitalong. However, I'm not going to have much time to knit in the next couple of weeks! \ud83d\ude05</p>\n<p>I look forward to checking out other folks' progress and a (careful, controlled, certainly not rushed) busy weekend of catching up when I get a chance.</p>\n<p>Thanks to everyone involved in making this knitalong possible! I am grateful to be learning so much and feeling like part of a community of folks doing the same!</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "article",
"_id": "46338643",
"_source": "175"
}
{
"type": "entry",
"published": "2025-10-25T14:56:10-07:00",
"url": "https://aaronparecki.com/2025/10/25/26/",
"category": [
"triplex",
"365"
],
"photo": [
"https://aperture-media.p3k.io/aaronparecki.com/5af77b7f2c8db955e7b2defb3d701e8973a75036c46417aa4636b25aa36644d7.jpg",
"https://aperture-media.p3k.io/aaronparecki.com/87ecec24d915581fe30f3856f17e0148cdd1dd0b35dae36bca762f2e3efb2728.jpg"
],
"content": {
"text": "The live edge desk is done! We put the table legs on it today and moved it into place!"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/41061f9de825966faa22e9c42830e1d4a614a321213b4575b9488aa93f89817a.jpg"
},
"post-type": "photo",
"_id": "46337173",
"_source": "16"
}
