More from Liz Denys
While on a short road trip and then recovering from surgery, I hand quilted and hand embroidered a linen lilypad quilt. And yes, I did make this little quilt for my Frinos plush from Hades II to have a nice place to rest.
I've worked out of a handful of different community studios at this point, so I figured I'd share a (probably incomplete) list of you might want to consider when picking a community ceramics studio for your practice. Cost, location, value: I'm not going to comment too much on this as costs vary highly depend on what city/metro area/etc. you're in and you best understand what value you'll get and what you can afford. That said, if you live somewhere walkable and are planning on making at home, you might want somewhere you can walk to or get to with fewer transfers or shorter walking to make transporting fragile greenware simpler. Regardless of your budget, it's good to know all the costs up front: class tuition, membership fees, open studio time fees, firing fees, materials costs, etc. Also, if you live somewhere with a high demand for community ceramics studio access, you may not get to be that picky if you want to start sooner! Equipment and space: What equipment is provided? What condition is it in? How many wheels? How many wheels per member? How many wheels per student? Is there a slab roller? What size? Do they have dedicated canvases or mats for different color clay bodies? Which do you use if you use a non-studio claybody (if you're allowed). Is there an extruder? Which extruder dies does the studio have? Can you use your own if you buy more or make custom dies? What are the policies for who gets to use what equipment and training? Stricter policies usually means equipment will be in good condition, but only if it's enforced. Ask about how often equipment has needed repair and how to report issues, even if they have good policies. What do the workspaces look like? How much space is generally available per person? What kinds of chairs and stools are provided? Are stools at wheels adjustable? Are there bricks or similar available for resting feet on if that helps your wheel positioning? Are handbuilding and glaze area seats comfortable for you? What height are those work areas/chairs? This may not seem very important, but standing height tables can be much less comfortable if you're primarily going to sit. What does your storage space look like? Are shelves shared or do you get dedicated space? How much capacity and weight work on the shelves and how does that fit into your practice? Remember you may be storing tools and clay/reclaim as well as works in progress. There can be lots of politics around shelves - ideal ones are neither too high nor too low, all else equal, and can be very competitive to get. Highest shelves may also be highly coveted since you may be able to stack things very high and store more! How easy is it to move around the studio? How easy is it to get your pieces from the storage space to the working areas to the places where you set them to fire? Are there separate spaces for members and students? Even if there are dedicated student classrooms, do additional classes spill over into other areas or shared areas? How frequently? Is this information easy to find out before you get to the studio? Does the studio provide bats and wareboards? Remember, even if bats and wareboards are provided, you may want to bring your own that you can keep in better condition or have different properties. Are there shared studio tools? What condition are they in? Is there communal newspaper? Communal plastic for slowing down drying? Newspaper is easy to get yourself, but dry cleaning bags are hard to buy in individual-use quantities. Materials: What are the studio claybodies? Do they fit well in your practice? Are they smooth or groggy enough? Which colors of claybodies are available? How durable and food safe are they? Will they reach vitrification and achieve low absorption rates if you're making dinnerware or other vessels intended to hold water? Is clay communal or do you purchase your own? If so, does the studio reclaim for you or is it communal practice? What is done to ensure reclaim isn't short? If clay is not provided, can you buy it at the studio? 25 pound blocks of clay are heavy and annoying to transport if you walk, bike, and take transit everywhere like I do, so this can be a big deal! Can you do agateware/neriage/nerikomi? (Make sure you're doing this with compatible clays, of course.) This question is especially relevant if clay is communal as you cannot simply throw blended clay blocks into reclaim bins for a single clay as this would create a new claybody unexpectedly. Maybe you are required to reclaim yourself, maybe there's a miscellaneous reclaim, or maybe they accept a small amount of loss (remember you can minimize this by ensuring you use all your blocks up - the end can usually be wedged up into a new claybody and made into a little pinch cup or bowl worst case). Can you use outside claybodies? If yes, what's the approval process? Even if you are not personally interested in using outside claybodies, it's good to ask as free-for-alls can result in low fire clays melting all over shelves and ruin other people's work at hotter temperatures. Does the studio provide decorating slips and underglaze? If they don't provide, can you bring your own in? What's the approval process? Can you make your own decorating slips or colored claybodies with Mason stains or oxides? What's the approval process? What are the studio glazes? Are they clearly labeled as food safe vs. not? If multiple claybodies are common in the studio, how many glazes fit each and is this clearly labeled? Are there test tiles for every studio glaze on each studio claybody? Are there any test tiles for glaze combinations? Reminder that test tiles aren't a replacement for doing your own testing - different surface slopes, your dips may be longer or shorter - but they help give you a sense of what's compatible with which clay bodies and which are runny vs. stable. How and how often are studio glazes tested? Are new batches tested before they're put out for use? Are studio glazes typically kept in consistent conditions? Large buckets of glaze can change consistency over time. Is specific gravity monitored periodically so water can be added as needed? Are glazes flocculated well/kept well in suspension or are they often hard-panned? Can you use non-studio glazes? Typically, this means commercial glazes as homemade opens a gigantic can of worms. What's the approval process? Reminder that low fire materials used in higher temperature firings can mess up more work than just where they're used, so even if you're not planning on ever using non-studio glazes, it's good to know what checks are in place to avoid this issue. Does the studio provide wax? Wax brushes? What condition is it in? Does the studio provide oxide washes? Are you allowed to make your own if it doesn't? What's the approval process? Firings: What temperatures does the studio fire to? How does this match their claybodies? A lot of claybodies, especially commercial claybodies, claim to support a range of firing temperatures, but they're not fully vitrified at all of those temperatures, especially at the lower end of their ranges. If a studio fires to both cone 6 and cone 10 and you plan on working primarily with cone 6 glazes, either studio or commercial, and make food-safe pieces, is there an appropriate claybody that will reach vitrification or are they secretly really all meant for cone 10? If you're only interested in making non-functional work, this may not matter to you as much as someone making mugs or vases. Are there special firings, e.g. luster firings? If there are luster firings, make sure to inquire about their safety protocols around luster firings - even if you plan on never using luster, poor safety policies around luster can endanger the health of everyone in the studio. How quickly is work turned around? Faster isn't necessarily very important once you've settled in as you want to be in a flow that has work at all stages at all times so you always have something to do, but it can be helpful to plan your rhythm. What is being done to ensure quality materials and firings? Are cones used in every firing? Is work that is too wet or egregiously overglazed set aside or fired alongside everything else - causing frequent explosions and glaze mishaps that affect other people's work? Cleanliness and safety: How clean is the studio? If you can visit on a few different days, that might help. Do people generally clean up after themselves well? Don't forget to check glazing areas and the undersides of tables and such - lots of clay dust can hide there! Are people taught safe practices (wet cleanup, no dry sanding, etc.)? How often do they actually follow them? What supplemental cleaning does the studio staff do? How frequently? Are there air filters? What quality of cleaning do they provide and are they appropriately matched for the size of the studio? Are there air quality monitors? Note: this doesn't seem very common to find at community studios in my area, but it would be a good sign if the studio did! Access and security: Are there signups for specific space to use or is it a free for all? Signups can be frustrating, but you're guaranteed specific space at a specific time. I've noticed people are better at sticking to an appropriate amount of space for their work that's mindful of those around them when it's a space they have to sign up for, but the flexibility of being able to drop in whenever can be great, too! If studio time is signup-based, are new slots released at clear, consistent times that work for you or will you always be getting picks long after most others do? Do students and members have 24/7 access to the space or do they only access to the studio when it's staffed or it's their class or for times they've signed up for? When is the studio open? It can be especially helpful to check in on drying and potentially spray a piece with a little water if it's getting too dry before you're able to do work, even if it's not a time you can do work. It's also great for getting a sense of how quickly pieces dry at the beginning of new seasons/studio temperature and humidity conditions. Who's allowed in the studio? Are there video cameras? Staff on site? Studio flow: Getting a sense of a studio's flow is easiest by seeing and trying out the studio! Take a tour, attend a workshop, take a class! If you're interested in membership, it may still make sense to take a multiple-week class first, and at least in Brooklyn, a lot of studios require you to take a class at their studio before getting a membership to learn how their studio operates day to day. If you're interested in membership, note that membership flows and class flows might be different - different spaces, different open studio policies, different storage situations for work and tools, etc. for example, a studio I loved to work out of as a member was a terrible experience during a handbuilding class because it tried to cramp too many people in too small of a space, but members weren't in the member handbuilding areas as much all at once, so I could finally enjoy the studio. Also, students often share a communal shelf in my area, while members have more dedicated storage space, allowing for more projects at once and storing more tools and other items used in their practice. Community vibe: Is it more social? More get down to business? Loud? Quiet as a mouse? How do you vibe with the community? Does the studio have a code of conduct? Is it a good code of conduct? Does wearing headphones generally mean "don't bother me" or do people interrupt everyone frequently? How do the owners and staff interact with staff? How do owners and staff interact with students and members? What are their expectations of members? I've been at studios where the owners and staff really don't want to ever interact with you, but I also once worked out of a studio where the owner would roll in and interrupt whatever was going on to use whoever was at studio as their personal therapist... even though it was time those members and students were paying her to use the studio. While the latter is a pretty extreme example, I've heard from ceramist friends in many areas that it's sadly not that uncommon to encounter overbearing owners that sour the experience. Miscellaneous: Are you allowed to sell work you make there? Are there community shows/sales? Are there official or unofficial limits on the volume of work? Some studios only want potters who aren't making very small quantities of work or only small to medium sized pieces because they don't actually have the capacity for high throughput or larger work... but not all of them will have clear policies on this. If there's a limit but it's only an unofficial policy, it will likely be applied unevenly. Finally, while it's unlikely that every community studio, or perhaps even any community studio, will be a completely perfect fit for any given potter, I've personally found my practice to be enjoyable at every community studio I've been at with a good community vibe. The goal of this list isn't to find a reason to avoid any particular studio as much as knowing how a studio's choices or limitations might affect your practice so you know what to expect and how to adapt!
Like so many other hat knitters, I've knitted the classic WWII watch cap, which is also known as Beanie no. 212, more than a handful of times. (You can find it on Ravelry here and here, respectively.) It's a charming, quick knit that's easy to resize, but I've never really liked the crown shaping on the original. I've knit a lot of these hats, and only one's had the original crown shaping for the decreases. I'm sharing two crown shaping variations I keep going back to below. I always knit this hat in the round, and my crown shaping patterns assume you will be knitting in the round, too. Alternate crown shaping 1 This alternate crown shaping follows the 6x2 ribbing of the previous section for the bulk of each round so that the ribbing continues throughout the entire hat. Written out: Divide stitches on 3 double pointed needles with stitches evenly divided among the three needles or mark out even sections with stitch markers if decreasing across 2 circular needles or with magic loop. (k1, ssk or skp, k if previous row was knit or p if previous row was purl until 3 stitches are left on the needle/before the next marker, k2tog, k) x3. Repeat step 1 until 4 stitches remain on each needle/in each marked section. Cut and draw yarn through the remaining 12 stitches 2-3 times. Tie off and weave in the ends. Alternate crown shaping 2 This alternate shaping both maintains the ribbing throughout the crown shaping and accentuates it by creating a sort of three-pointed star with 3 of the 2-stitch-wide purl parts from the previous 6x2 ribbed section. This shaping really only makes sense when making a size hat where the number of stitches is evenly divisible by 24, so I typically only do it on size "small" hats (cast on 96 stitches). You could adjust the needle size and gauge for a yarn that works well at that gauge to make this work for different sizes. Written out: Stop the last 6x2 ribbed row 1 stitch early and divide stitches on 3 double pointed needles with stitches evenly divided among the three needles or mark out even sections with stitch markers if decreasing across 2 circular needles or with magic loop. Ensure that each needle transition or marker has a single purl stitch on each side. (p1, ssk or skp, k if previous row was knit or p if previous row was purl until 3 stitches are left on the needle/before the next marker, k2tog, p) x3. Repeat step 1 until 4 stitches remain on each needle/in each marked section. Cut and draw yarn through the remaining 12 stitches 2-3 times. Tie off and weave in the ends. Additional project notes Needle: US 7 - 4.5 mm Gauge: 19 stitches and 24 rows = 4 inches in stockinette Hats made for me should generally be a small (cast on 96 stitches), and hats made for my partner Matt should generally be a medium (cast on 104 stitches). Footnotes Either of these will create a left-leaning decrease, use whichever one you prefer.↩ Ibid.↩
After five different drivers, including a school bus driver, aggressively close-passed me in Midwood last night and two of them threatened me just for being on the street, I realized there's a huge gap in educational outreach about bike rules in NYC: drivers. I decided to make a mini-zine that demystifies the behavior of law-abiding bicyclists like myself and helps drivers better understand what to expect when sharing the road: All text and illustrations in the mini-zine are my own. Many thanks to Matt Denys for help proofreading! This zine is licensed under the Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License, so you can copy and distribute this zine for noncommercial purposes in unadapted form as long as you give credit to me. Gas stations, car dealerships, auto repair shops, rental car offices, parking lots, book shops, restaurants, coffee shops, and other commercial establishments are welcome to give out these zines, too - as long as the zine itself is free! Check out the NYC Bike Rules for Drivers mini-zine on the web or download the pdf to print here!
Here's how to fold a mini-zine, featuring my mini-zine So you want to make a public comment! Fold the printed mini-zine page in half, then half in again, and then in half again as shown. When you open the piece of paper, each of the pages should fit fully within a set of folds. With the mini-zine page completely open, fold it in half with short ends touching ("hamburger style") so the text is on the outside. Using scissors, cut a across the dotted line. When you reopen your paper, there will be a slit in the middle of the sheet. Fold the paper in half lengthwise with long ends touching ("hotdog style"), hold the paper at either end, and fold the sheet into itself to form an 8-page booklet. Make sure the cover is on the front!
More in programming
My now-traditional “summary” of the conference along with my own commentary and thoughts.
Every year, browser vendors collaborate via the Interop project to synchronize their efforts on new HTML/CSS/JS features. This year, there’s a ton of super exciting features being considered! In this blog post, we’ll explore the CSS of the future, to get a glimpse of what we’ll soon be able to do.
Imprint’s average engineer is merging 4x more PRs than 2 years ago. Yay. Aggregated behind the average is something even more interesting: we have two teams that are merging 10x their PRs over that period. One engineer is merging 25x the PRs per week of our average engineer two years ago, and a number are merging 10x. That’s pretty neat, and the slope of the line suggests our average in a year is going to look much closer to today’s p90 than today’s p50. Even more importantly, we aren’t just shipping more, our quality has improved: incidents are down 42% half-over-half, and critical incidents are down 78% half-over-half. I think we’ve always known the quality/velocity tradeoff wasn’t a particularly useful construct, but that’s undeniable today. As we’ve walked this path, we–like everyone else progressing down it–have run into the problem of pull request review. The p50 pull request review took about 33 minutes to complete 2 years ago, but now takes us about 77 minutes. The slope here correlates tightly with the number of pull requests getting merged. Tightly enough that addressing it became one of my priorities for the week. We solved it! Just kidding, we’ve absolutely not solved it, but I think our current approach is an interesting one, which we call the small-change. The work discussed here was shaped and done by many folks at Imprint including Dan, Joy, Daniel, Lenny, Taylor, Ted, and Annie, among many others. Why review pull requests? There are four reasons we review pull requests: Knowledge sharing between author and reviewer – software engineering is generally learned via apprenticeship, and reviews are a primary mechanism of experienced engineers teaching others what good software looks like. We believe the current volume means that this knowledge sharing will have to move towards operating on clusters of pull requests, rather than individual pull requests Preventing errors – review has always been an expensive time to catch errors, and we believe that effective CICD along with harness verification techniques like poteto’s pstack are more effective mechanisms for preventing errors than review Preventing malicious behavior – my experience is that even careful code review will generally miss competent malicious behavior, although fortunately most malicious behavior is incompetent. We believe both sorts of behavior are best identified using a combination of fixed rules (modifying these specific objects/classes/files requires review), anti-abuse mechanisms that we’ve refined in our LLM-based member support experiences, auditing, and audit log inspection Compliance obligations in our documented controls – these can be changed, but today they require that an independent human reviews changes in a subset of our repositories In the modern development paradigm, we think there is a better solution for each of these problems. But, we also want to make these changes very cautiously. Small steps with small-change We believe we move fast by finding narrow, contained ways to validate new practices, so to iterate our way into an effective solution, we’ve developed the concept of a small-change. Here’s how it works: When a pull request is marked ready, CICD determines whether it is eligible to be a small-change. This is represented as a passing Github check. There is also a label for visibility, but it is the check itself, managed by the build and not human modifiable, that determines eligibility. (The label is used for initial filtering, but the check is still independently verified.) Something is a small-change if it meets all of these criteria: It is less than 1,000 lines of code There are no p1 or p2 findings from our ai-code-review automated review bot The author has “experience” in the service or application, defined as 10+ prior merged pull requests into that service or application’s directories. For changes working across multiple services or applications, the author must have experience in all of them to qualify Impacts fewer than N distinct services or applications. N is 1 on our frontend monorepo, and N is 3 in our backend monorepo, where typical changes will modify both a gRPC service and a common HTTP gateway Shared libraries and utilities files are not eligible for small-change Each repository has a .small_change file which allows per-path customization while we continue to tune the behaviors. For example, a service dealing with money movement can be excluded Our Slack automation tags every reference to a pull request with reacji labeling the state of that pull request, for example if it has failing tests, if it has been approved but tests are still running, or if it is ready to merge. We added a small-change reacji that indicates which of those pull requests meet the small-change criteria In our internal skills repository, we created two skills that have been distributed across harnesses: review-small-change which takes a list of repositories and reviews all open, non-draft, small-changes, including providing approval if they meet the review’s criteria (all checks pass including small-change check, and not touching on sensitive topics such as payments and security) review-pr-cluster which reviews batches of pull requests to identify common themes that came up, and suggest opportunities for discussion and adding verifications We set the social expectation that any error caused by a small-change is a failure in our system, and has to be solved at the system level: improvements to ai-code-review, to our verification mechanisms, to our CICD, to our harness, etc. This took about two days of infrequent attention to implement and rollout, although I imagine we will be tuning the knobs here for a long time. Maybe forever. fleet: centrally orchestrated harness I’ll briefly mention our other approach to reducing code review volume, which anchors on our centrally-orchestrated harness, fleet. (Which is similar to Stripe’s Minions although not following the one-shot approach in particular). We rely on fleet to implement and verify software in a highly controlled harness running in the cloud, with independent evaluation mechanisms to identify the correct number of independent reviewers for any given change. That number can be as low as one (e.g. fleet writes, one human reviews) for changes evaluated as safe. Results / next steps / reception I’ll be honest, it’s too early to give a useful result here. From early results, about 10% of changes qualify as a small-change. Those are now eligible for very fast approval, and generally get it unless they trip a flag, generally due to touching a security or money adjacent topic. While 10% is a small percentage, the core concept here is working, and ultimately will succeed or fail based on our ability to expand that percentage over the next few months in tandem with expanding our verification mechanisms to be increasingly comprehensive. This is ultimately going to fail or succeed depending on our ability to improve our verifications, which does require more difficult sorts of techniques to accomplish in low scale-complexity, high domain-complexity software than in the high scale-complexity, low domain-complexity products where many techniques like incremental rollouts are exceptionally effective. (Don’t get me wrong, they still work, they just provide less coverage when most users have different configuration and behavior.) Folks have not been uniformly excited about this, it’s a substantial change from how we’ve learned to be good engineers, and it’s uncomfortable to reevaluate whether a long-held best practice has become merely dogma. The most energizing part of the current cycle is that we get to reevaluate these practices we grew up on every week; the most painful part of the current cycle is that we’re likely to fall behind if we ever stop reevaluating them.
The park near my house has lots of chestnuts and my kids have been collecting them like crazy (it’s actually their favorite post-school activity). We accumulated quite a hoard. I thought it would be fun to make a launcher so we had something to do with our new chestnut collection. I wanted to go with a very simple crossbow-style design (like the famous D2 item) using latex tubing and a leather pouch for holding the chestnuts. This is what I came up with. It launches chestnuts about 220 feet, and it’s simple enough to build in an afternoon. The frame is a 42 inch 2x2 and a spare IKEA bed slat for the crossbeam, glued and screwed together. A 3/8 inch eye bolt goes through each end of the crossbeam, and the latex tubing is tied to those and to the pouch from a leather shepherd’s sling. Tying the tubing was the fiddliest part. It has to be stretched while you wrap it with butcher’s twine, so I clamped a couple of scrap blocks to my workbench to hold it. I like this design because the tubing can be wrapped around the eye bolts to easily add more tension and power. The Trigger My favorite part of the design was that I decided to use an archery release like this one for the trigger. It provides a safe and reliable way to hold the tubing back, and it’s made to let go cleanly. I 3D printed a little housing that mounts the release securely to the back of the stock, and the release clips onto a loop of archery D-loop cord on the back of the pouch. Then I added a dowel for a rear grip and an old handle I had previously removed from my shop vac. How Well Does It Work? We tried it at the park and it works surprisingly well. Aimed at about 35 to 40 degrees, it sends our chestnuts (on the small side, about 10 to 15 grams) about 220 feet. Thanks to the archery release, we haven’t had a single misfire. I got curious and did some rough math. To go that far with air drag, the chestnuts are leaving at somewhere around 85 to 100 mph, which works out to about the same energy as a paintball. So safety glasses are important and you never point it at anyone. You can find the 3D print on Printables and a full build guide on Instructables. Make sure to always use it with adult supervision :)