<?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 Alex Kimi Wolfe on Medium]]></title>
        <description><![CDATA[Stories by Alex Kimi Wolfe on Medium]]></description>
        <link>https://medium.com/@w0lfe?source=rss-916052e51fa3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*t_RMd_H54mabOzfDJIC2pw.jpeg</url>
            <title>Stories by Alex Kimi Wolfe on Medium</title>
            <link>https://medium.com/@w0lfe?source=rss-916052e51fa3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 19:44:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@w0lfe/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[The case of the eternal blur]]></title>
            <link>https://medium.engineering/the-case-of-the-eternal-blur-ab350b9653ea?source=rss-916052e51fa3------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab350b9653ea</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[webclient]]></category>
            <dc:creator><![CDATA[Alex Kimi Wolfe]]></dc:creator>
            <pubDate>Wed, 02 May 2018 18:39:26 GMT</pubDate>
            <atom:updated>2018-05-02T20:59:32.793Z</atom:updated>
            <content:encoded><![CDATA[<h4>a bug hunt horror novella</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VDKh38cAPOicNxEfabm_1Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aPt02pVSduYpuplXubVzMw.png" /></figure><p>This story documents a bug fix, a particularly elusive one. The kind you encounter when trying to build something in a stack where the original architects were brilliant, but no longer around, and maybe didn’t completely agree on how some fundamentals should work together.</p><p><a href="https://medium.engineering/2-fast-2-furious-migrating-mediums-codebase-without-slowing-down-84b1e33d81f4">Damn, it would be satisfying to rewrite the stack one day</a>, but until then you have to navigate + make the best of what you’ve got. It’s probably the skill I’ve developed most working at Medium.</p><p>So <a href="https://medium.com/u/3aa0e1951a05">Brad</a> + I have been working on these elevated collection pages + posts for a small eternity. We forked the post page, ripped out all the cruft, and made this rad index page that shows off all the posts in the collection with some branding. We’ve had a few different collection concepts on Medium, but this one is optimized for our editorial team to showcase some of the collabs they’ve been working on, like <a href="https://medium.com/s/unrulybodies">Unruly Bodies</a> with Roxane Gay.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0zEbM3nwpxtSB05tBoLArg.png" /><figcaption>our new shiny collection index page</figcaption></figure><p>We identified the last stray bugs, patched them, and I made some time for some purely engineering improvements I couldn’t squeeze into our first version before I bounced for 🌴 hawaii 🌴 for a bit of workcation.</p><p>One of these improvements was to make that giant blue Unruly Bodies cover image progressive + to have a nice placeholder for it while it loads. (Before, the text would jankily shift to the right on first render, then the image sloooowly painted in over mediocre connections)</p><p>Our progressive image code takes a super tiny version of the image that loads in quickly + blurs it out as a placeholder until the real one is ready. This unfortunately synonymous with when javascript is ready, but it’s still way better than a jagged paint-in.</p><p>We used to only use this image treatment on our post page (rendered in the backend) and for horizontal images. I moved the template generation code over to the client, flipped the logic on its side to support vertical images and was extremely pleased with myself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2VciB5aubbfKPm2R4Z1Pjw.png" /><figcaption>ahhh yeah once that image loads in this is gonna be so premium</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rxYSd2H0PAsEANZ9.png" /><figcaption>TLDR: my progressive image is definitely broken</figcaption></figure><p>Top of the next morning, our valiant editorial team files a bug with me over slack. The issue is a weird one, transient, and I can’t reproduce at all. The blurry placeholder image loads in fine but then is never swapped with the real asset.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BgbmYHjpGxyEWCvevORTTQ.png" /><figcaption>I have some wild stabs in the dark theories, but it’s impossible to say until I have my very own eternally blurry image in my grasp.</figcaption></figure><p>I give up for the evening, 🙏 for transience and eat a spam musubi on the beach for dinner + fall asleep.</p><p>Design + Editorial do not give up trying to help me conjure this eternal blur on my laptop, and are on it top of the morning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pKwV_49GUw2w5rbSYKjslg.png" /><figcaption>brad is the best, and this is sherlock level sleuthing</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SJoKc_sb5_dLoPXJZiKwYg.png" /><figcaption>pray to be blessed with wonderful co-workers willing to help you repo obscure things, especially when you’re the only eng on a project with a million threads to pursue</figcaption></figure><p>Brad + Euni notice the issue only happens at very specific browser sizes and seems to happen reliably in one window size vs another.</p><p>Equipped with something to look for, I brace myself to flail around some of our more ancient code.</p><p>THE SCENE</p><p>Alright before we delve into the progressive image code looking for view height clues, let’s set the scene of this heinous bug crime.</p><p>This page looks pretty basic, but there are a few moving parts that have some fairly interesting front-end components. There’s the full bleed <strong>progressive image</strong>, and also an <strong>infinite scroller </strong>that handles pulling in new pages of posts.</p><p>There’s also a <strong>footer</strong> that scrolls into view after you reach the end of the potentially infinite div full of posts. (The code for the footer only exists stashed on an in-progress branch on my computer at the time.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ix2-vTGpNvMOxcv6XdSxaA.png" /><figcaption>a rough dom → component breakdown. We have a js framework that imposes enough reality to get the job done, and a single Screen component coordinates the rest. It also can fetch data from some app wide singleton services they all share.</figcaption></figure><p>All of these components (and my fledgling footer code) subscribe to two services: <strong>DomMonitor</strong> and <strong>ElementTracker</strong> . These are singleton services, that intercept scroll events and read element positions in a performant way that doesn’t trigger a re-paint.</p><p>These two are key to the rest of this rabbit hole, so lemme quickly flesh them out for you.</p><p><strong>ElementTracker</strong> is a clever piece of code by <a href="https://medium.com/u/e3c4b8ef596f">Daryl Koopersmith</a> that’s a cornerstone of how we handle scroll events in our web client.</p><p>Basically scrolling is trash, the browser emits events constantly, and even accessing an element’s layout properties to see where it is on the page can trigger a repaint. If you’re constantly triggering repaints while scrolling tied to the native scroll event you’ve got yourself some choppy garbage animations.</p><p>🗑 ☠️ 🗑</p><p><strong>ElementTracker</strong> “tracks” elements by measuring their start position, keeping track of user scroll actions, and estimating where they’ll be on the page given the scroll delta and the current viewport. It then hooks into window.requestAnimationFrame, (which if you’ve ever done canvas animation will be familiar), which is only emitted when the browser does a natural repaint, and piggybacks on that to do our element checks. This is a key optimization in our rendering, because it avoids the excessive repaints in the naive approach.</p><p>The draft W3C <a href="https://www.w3.org/TR/intersection-observer/">interaction observer API</a> does something similar and I’ve been dying to mess with it, but our version works on IE and is fairly battle tested.</p><p><strong>ElementTracker</strong> sits on top of our <strong>DomMonitor </strong>service that does the heavy lifting of listening to the browser’s real scroll events and emitting the optimized versions we use for our code.</p><p>SLEUTHING</p><p>Alright back to the bug at hand, our image loading code. Progressive images are loaded when <strong>ElementTracker</strong> is “refreshed”, e.g. on throttled scroll or a performant repaint.</p><p>I dig into the event handler, and it dictates we decide whether we need to load an image by extending the viewport by 3x (which captures a page above and below), and then we check to see if there are any progressive images within that extended viewport. If so, it triggers some javascript to load the full-resolution image + implement the swap.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MNIxK0KvCnT9SslZoKHWfw.png" /><figcaption>on post pages it works a bit like this, checking for images within the window (one page up and one page after) and ensuring their images are loaded in. It does this by making sure the pink rectangle intersects with our progressive image.</figcaption></figure><p>Our image is smack in the middle of the viewport + this code is also run once when the ProgressiveMediaLoader is activated. We should be fine for triggering an interception/image load.</p><p>But it also seemed like a sensible place to start debugging and sanity check. I print out the viewport + the rect that represents my progressive image</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vnAMfaMzN6IHCEytXIcn6g.png" /><figcaption>……theres some random negative garbage in here</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FPy7cUZIYEwCqrVQnVQiOw.png" /><figcaption>I submit a plea for help into the slack void</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I2SIRM2Vheljz2MfwrHZOQ.png" /><figcaption>these are the two rectangles that progressiveMediaLoader is looking at</figcaption></figure><p>Instead of accurately representing the elongated viewport, the ProgressiveMediaLoader on the index page is looking waaaaaay to the left. The bounds for the image are also way off!</p><p>Ahh damn. They’re like a hair’s width apart. It’s probably a pixel rounding thing on certain screen sizes triggering an overlap.</p><p>But why are these rectangles so recklessly flinging themselves into the void?? Why is this happening only to me?? I get a shaved ice to fend off my existential crisis and eat it on the beach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5HIwj0pmUEKNjccmpUjvSw.png" /><figcaption>the usual culprit</figcaption></figure><p><em>FLASHBACK: a week earlier</em></p><p><strong>euni: </strong>oh hey alex <a href="http://medium.com/s/aztec-yoga">aztec yoga</a> is getting cut off, it’s only showing 10 posts.</p><p><strong>me: </strong>damn, this page used to pull down every post in the sequence async, and i just put in some real paging. 10 posts come down now with the first page load, and the rest are supposed to come in on scroll.</p><p><strong>me: </strong>let me see what’s up with these scroll events</p><p><strong>euni:</strong> cool, we’re rolling out 15 posts for unruly bodies on monday, can we fix it by then?</p><p><strong>me:</strong> for sure</p><p>(<em>this conversation is summarized + semi fictional</em> 😂)</p><p><em>FLASHBACK (bug inception!! don&#39;t stress, quick pagination detour)</em>:</p><p>Lists of thing that paginate on infinite scroll is Medium’s bread + butter. The code patterns for this are pretty set, I just broke them trying to be clever with this layout. We’re under time pressure for a fix so I want to patch it fast.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5aBmlHFpp6PGGUIhJQfHbA.png" /><figcaption>Normally you’d just make the image on the left + the metabar fixed. Fixed elements can’t interact with any others in the dom — so instead I set the posts elements to have an overflow-y: scroll to preserve the scrolling behavior, and have the posts + the image as flex siblings so they can figure out the best width for themselves.</figcaption></figure><p>Despite the most ominous sounding warnings I could cook up, we’re supporting some text baked into images here. Full bleed split screens kind of look like garbage as they get more square, especially if you have to be super careful never to clip your image. It’s also way too wide to kick the layout to tablet.</p><p>I wanted to use flexbox for more granular responsive rules, I needed an overflow-y: scroll on the posts div to make it work, it was all fine. Until we needed a second page of posts for the first time and I realized the posts div wasn’t triggering the scroll event it needed to request more items.</p><p>The <strong>InfiniteScroller</strong> code that appends the next page of items at the end of the list ALSO uses <strong>ElementTracker</strong> / <strong>DomMonitor</strong> to check whether we need to load in a new page.</p><p>They decide what element to check for events on by querying this method on the master Screen component, that coordinates all our lesser components, which always tells them to watch document.body.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZxVEayfeX6eVnPoadpoaUQ.png" /><figcaption>base screen returns `document.body` every time without fail unless you override it, something we don’t do anywhere in our current incarnation of our codebase.</figcaption></figure><p>Since I made the overall layout fixed, this is no good. document.body isn’t actually the one scrolling, the element that contains the post is.</p><p>Scroll events don’t bubble for performance reasons, and our event listener for scroll…..is wrapped so deeply in our custom api that changing it to capture would be a bit of a nightmare.</p><p>This is unfortunate since we do find the correct scrolling element, and theoretically set <strong>InfiniteScroller</strong> to watch it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mntx0oib2Z0RWq-G0kbMXg.png" /><figcaption>this piece of code looks for the closest scrolling element to where you initialized the infinite scroller code, and attaches it to our main Screen component which controls the whole page</figcaption></figure><p>However, when it calls this._infiniteScroller.attachToScreen() here, I<strong>nfiniteScroller</strong> ignores its scrollElement and just relies on whatever the Screen’s instance of <strong>DomMonitor</strong> (the service that intercepts all scroll events) is watching, which is always document.body.</p><p>Looking deeper, the scroll element for <strong>InfiniteScroller</strong> really is only used for measuring, and not for grabbing events off of.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NXch97DKJ0PreA6PSON4vQ.png" /><figcaption>aaaaahaha it turns out this method is effectively useless, as diligently documented</figcaption></figure><p>This seems like an obvious bug caused by loosely coupled components bound with a layout that demands behavior that we haven’t had to accommodate before.</p><p>I move things around so that BaseScreen.getScrollingElement returns the post elements container for this screen vs. document.body.</p><p>Paging works and we’re gooood tooo goooo 👍</p><p>PRESENT DAY: BACK ON THE TRAIL OF THE ORIGINAL PROGRESSIVE IMAGE BUG</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lABhKK7OpRjZBBn0XI20hw.png" /><figcaption>……..progressive images are still broken, it’s my fault, and its definitely due to my paging patch</figcaption></figure><p>Alright so I’m pretty sure I caused the eternal blur myself with my quick fix for paging. By setting the scrollingElement to the posts container waaay off to the right, all of the other pieces of code (including ProgressiveImageLoader) that rely on the Screen returning document.body broke.</p><p>Somehow that culminated with apparating my bounds check we use to see if an image is in the viewport way off to the left, I’m not going to question it too much</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AUQqAzjgnuOiQ59-Zhtciw.png" /><figcaption>the current state of the world for recap. I really just wanted that full bleed image to load in, but its not because my progressiveImageLoader doesn’t think it’s in the viewport.</figcaption></figure><p>cool. cooooooool.</p><p>Alright, rather than changing this semi global scrollingElement that a bunch of random code relies on to fix paging, it would have been a much stronger pattern to wrap up koop’s note on the effectively useless method in <strong>InfiniteScroller.</strong></p><p>I want to set a private scroll handler for paging that watches my overflow-y: scroll container vs relying on the same global domMonitor events on document.body as everything else, so I go ahead and do that.</p><p>This allows me to have my overflow-y: scroll element that I needed for the precious layout, but no other service or component has to know.</p><p>A lot of the web client is littered with mostly finished <em>just in case </em>api endpoints. <strong>InfiniteScroller</strong> has one of these that just claims it will attachToElement , passing in a specific element vs the attachToScreen. It’s perfect. I point it to my overflow-y: scroll element.</p><p>Progressive images load in reliably + beautifully + paging works on my element on Hatch. I’m very satisfied, eat a bowl of poke on the beach and go to bed</p><p>THE NEXT DAY</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gK7sITMURfAIxOoacY0WgA.png" /><figcaption>(hatch is our staging environment)</figcaption></figure><p>…..my patch breaks paging on the homepage, so <a href="https://medium.com/u/eecfd5470c4b">Eduardo</a> reverts it.</p><p>THE SAGA CONTINUES</p><p>ok so i check out the homepage</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MTfG-DO1R6LO2LO9MnEc0A.png" /></figure><p>and ….it’s definitely still attaching itself to document.body like it should. So there’s got to be some difference between the private scroll listener + the domMonitor one that’s breaking infinite scroll there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kn3GOAi8Mv1gi9Faa0JZOA.png" /></figure><p>Errr it looks like chrome is cancelling our deferreds we’re shooting off on scroll that checks to see if we need to load more items.</p><p>I check the convenient “just in case” api call I hooked my code up to earlier. It set’s a private scroll handler, but the throttling behavior is kind of wonk. It’s definitely triggering chrome to physically block these this.onScroll calls which would summon the next page of posts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*li-vM2OC8g0PHkuc8miH3w.png" /><figcaption>Our hard coded throttle delay is 200ms and whatever obv.util.throttle is doing is messing with the listener. If i remove the bit of code that does the scroll throttling, paging works fine again.</figcaption></figure><p>I can remove the delay, but then we lose the optimizations we get from throttling, and potentially get choppy scroll animations again. Ooooook. This attachToElement api in <strong>InfiniteScroller</strong> is only used one other place and is probably old/out of date.</p><p><strong>DomMonitor</strong> obviously has an up to date and working version of scroll throttling, that this api call was probably deprecated in favor of.</p><p>It would be annoying to rewrite, and weird to have two places with that logic. I should probably abstract it into a shared throttled scroll handler and then also do a gradual rollout so I don’t inadvertently break a different part of the site…</p><p>I eat another poke.</p><p>I look sagely into the infinite void of stars where they meet the waves. The infinite void that definitely doesn’t scroll and instead just exists in peace.</p><p>Ok at this point there are 3 ways to fix this horrible slew of problems.</p><ol><li>Re-implement domMonitor’s throttled scroll into <strong>InfiniteScroller</strong>. <strong>InfiniteScroller</strong> will be a real component tightly coupled to the div it’s adding posts/streamItems to. It will also work with horizontal scroll (like in a carousel) if we ever want to do that in the future.</li><li>Re-implement the way <strong>ElementTracker</strong> looks at the viewport. It probably should use the actual viewport and not derive it relative to the scrolling element (which caused the broken negative left bounds earlier) when deciding whether a progressiveImage is in view.</li><li>…..re-write my template so it scrolls with goddamn document.body</li></ol><p>The void stares back from behind my eyes and I choose option 3, to restructure my html ☠️ 💀 👻 so the image is fixed and document.body is the one that scrolls like the rest of medium.com. You don’t get nice flexbox image widths but max-width: 45% is roughly what it was doing most of the time and is definitely good enough. I put a horrible placeholder div that lives under my fixed one that keeps the text pushed to the right and somewhat flexed.</p><p>…I’m also going to patch solutions 1. and 2. even though they are no longer relevant to this layout but because hot damn there probably will be a case where I have to make infinite scrolling work in an isolated element, like a future carousel of doom…..a death carousel full of progressive images.</p><p>I re-write my dockable footer…..haaaah remember that feature……….and it’s easier this time since I don’t have to account for apple’s native rubberbanding on the FOOTER’s scroll events when I hit the bottom of my overflow-y: scroll div, since it can just naturally live on the bottom of document.body and I can look for the border between the two.</p><p>I flip the switch to roll out the finished project + my sweeping rampage of bug fixes across all collections to all users.</p><p>I lay down on my own grave.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x8Xu63Zm3-X_jjVPEz5-RA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fR03mh71L0U_2voOLF-_tQ.png" /><figcaption>yes i have charles, yes i have.</figcaption></figure><p><em>if you too would like to brave the eternal fires of our web client, and help it emerge like a phoenix from the ashes, </em><a href="https://medium.com/jobs-at-medium/work-at-medium-959d1a85284e"><em>come work with us</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab350b9653ea" width="1" height="1" alt=""><hr><p><a href="https://medium.engineering/the-case-of-the-eternal-blur-ab350b9653ea">The case of the eternal blur</a> was originally published in <a href="https://medium.engineering/">Medium Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Series for web]]></title>
            <link>https://medium.engineering/building-series-for-web-319925de3665?source=rss-916052e51fa3------2</link>
            <guid isPermaLink="false">https://medium.com/p/319925de3665</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[hack-week]]></category>
            <category><![CDATA[medium]]></category>
            <category><![CDATA[series]]></category>
            <dc:creator><![CDATA[Alex Kimi Wolfe]]></dc:creator>
            <pubDate>Fri, 09 Feb 2018 21:39:38 GMT</pubDate>
            <atom:updated>2018-02-09T21:52:58.046Z</atom:updated>
            <content:encoded><![CDATA[<h4>medium haaaaack week 2018 coming in hot</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GirqHIZkSCFb_1g8TA_Lsg.png" /><figcaption>this is why they don’t let me design things for production</figcaption></figure><p>The first week of January this year Engineering was left to its own devices for the time honored tradition of following your own heart, and developing features for Medium that personally interest you — <strong>hackweek!</strong>.</p><p>This year <a href="https://medium.com/u/d2e2f44df9bf">Emma Zhou</a>, <a href="https://medium.com/u/16232bb4608a">Herzog</a> and I with our powers combined are so excited to present to you</p><blockquote><a href="https://medium.com/series/c5eae0da6604/">Series for Web</a></blockquote><p>We launched <a href="https://blog.medium.com/welcome-to-series-a-new-type-of-story-on-medium-bade380985c4">Series</a> on the Medium mobile apps last year as an immersive experience that that integrated gorgeous transitions, video, and gifs. I love writing them since they feel way more casual, and it’s much easier to control the pacing of a story + develop narratives over time.</p><p>We wanted to maintain that same level of visual polish when porting them over to desktop web. Fortunately our amazing Infrastructure team has been working on a new React stack we got to try out for hackweek that made managing the user states + animations infinitely easier.</p><p>…Unfortunately we did not hack together support for embedding series into the home page of our engineering blog so here we are.</p><p>I’ve written up a riveting <a href="https://medium.com/series/c5eae0da6604/">behind the scenes exclusive peek</a> at this triumph of engineering in series form, please check it out ✨ and let us know what you think!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*4co5ha3Kp5iGzxtZwIgwiA.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=319925de3665" width="1" height="1" alt=""><hr><p><a href="https://medium.engineering/building-series-for-web-319925de3665">Building Series for web</a> was originally published in <a href="https://medium.engineering/">Medium Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[building SERIES for web!]]></title>
            <link>https://medium.com/series/building-series-for-web-c5eae0da6604?source=rss-916052e51fa3------2</link>
            <guid isPermaLink="false">https://medium.com/p/c5eae0da6604</guid>
            <dc:creator><![CDATA[Alex Kimi Wolfe]]></dc:creator>
            <pubDate>Mon, 05 Feb 2018 22:21:22 GMT</pubDate>
            <atom:updated>2018-02-09T21:36:28.819Z</atom:updated>
            <content:encoded><![CDATA[<p>About a year ago, we built out <a href="https://blog.medium.com/welcome-to-series-a-new-type-of-story-on-medium-bade380985c4">SERIES</a> on Medium, a story format designed for mobile with gorgeous full screen images + visual polish.</p><p>Posts on Medium tend to have a lot of gravitas, and we wanted something that felt lighter + more fun.</p><p>You could update series organically in short bursts and develop them over time</p><p>It’s one of my favorite things we’ve built during my time here, but as an entirely native experience, it was also a project I was not needed on as a web client engineer</p><p>I was on the fledgling subscriptions team at the time coming up with less and ….more horrible ways to implement avatar halos that break in the center but also have rounded stroke ends at arbitrary points that don’t scale with avatar sizes</p><p>and forlornly observed the beautiful demos + constant streams of laughter from across the aisle</p><p>to mine (and everyone’s delight), my friend + engineer/design savant <a href="https://medium.com/u/16232bb4608a">Herzog</a></p><p>spun up a prototype of what series could look like on web</p><p>and they were gooooorgeous</p><p>however, it was really was intended to be a native experience, and we really really wanted people to try it out in the app. So rather than pushing back launch to build a web version</p><p>so we tried to send you there 😂</p><p>……which it turns out is virtually impossible from desktop web.</p><p>there was a notorious tweet right after launch actually that was the cause of much internal groaning + lols that went something along the lines of</p><blockquote>“It’s easier to catch the common cold than it is to share a Medium series”</blockquote><p>which was unfortunately true, but in our defense it’s pretty easy to get a cold?</p><p>…we set “as easy as catching a cold” as the new bar for ease + user intuitiveness we should all strive for.</p><p>Shortly after Series launch, we all got pulled pretty deep into making the fledgling subscriptions experience a concrete one</p><p>and herzog’s prototype languished on an internal go/ link, lost to the ages.</p><p>I had thought all hope was lost.</p><p>ONE YEAR LATER</p><p>it’s january at Medium and the eng team is having a hack week.</p><p>pretty much you have free reign to work on whatever you like while product + design shore up plans for the quarter.</p><p>I hit up the brilliant + versatile <a href="https://medium.com/u/d2e2f44df9bf">Emma Zhou</a> to see if she’ll get in on my scheme.</p><p>Emma was on the original series team + the flame of series burns bright within her</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/572/1*dhnOW7dvxfqxTxTzUp4wLg.png" /><figcaption>(ignore that audio part)</figcaption></figure><p>I’m ecstatic. The only thing left to do is to figure out how to do it.</p><p>the original Medium web client was built with a bit of a purist point of view</p><p>It’s more or less plain javascript which is</p><p>…..fine</p><p>and excellent for shoring up your fundamentals. I, much to my horror and chagrin, have a much deeper understanding of rendering, performance, and all of javascript’s murky depths than I did at my last job working mostly in Angular.</p><p>but it makes it hard to move super fast, and coordinating a bunch of flashy animations triggered by user actions is probably one of the more painful things to build in that environment, and a dream in one with any semblance of data binding.</p><p>luckily for us, our infra team has been working on a new react stack to sit on top of our ancient node server for the past few months</p><p>Unfortunately switching back and forth between any route on the new app vs one on the old one triggers a pretty big javascript download so the end user experience isn’t great at the moment.</p><p>However, for a visually intensive stand alone post page that doesn’t crucially need to link anywhere else, it’s perfect.</p><p>just to….not put all our eggs in the untested on prod, but extremely dope basket, we tried to spin up a quick version that could definitely ship on the old stack, just in case.</p><p>It still took us a better part of half the week to spin up a meh view, based on the amazing <a href="https://medium.com/new-series">editor</a> <a href="https://medium.com/u/e3c4b8ef596f">Daryl Koopersmith</a> spun up for series launch last year, laying out all the cards in a row.</p><p>it was workable but not the true</p><blockquote>VISION</blockquote><p>One of our favorite parts of series is the surprise of the next card, that lets you set up jokes and use gifs for hilarious effect without having them horribly animate halfway up the screen as your reader finishes your story</p><p>we flipped it on for staff and baaaaaaailed, ready to dive into the new stack.</p><p><a href="https://medium.com/u/16232bb4608a">Herzog</a> had built the original prototype in a small react app, so the bulk of the work was translating the code so it was production ready, hooking it up to the backend, and integrating the typical Medium ui.</p><p>It was also perfect for me since I hadn’t actually touched react before, so translating between prototype code + our internal component framework was super helpful to get up to speed</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_-SA8NJptqG8h1pQyXzrXg.png" /><figcaption>…don’t worry we sanitize string data further down the stack on prod</figcaption></figure><p>It turns out react is fairly effortless as well as incredibly fun.</p><p>Emma dove deep into running the response from our normal node server through a new GraphQL layer so it was beautifully formatted by the time it got to me</p><p>and a day later we were sitting pretty with this vision of beauty + grace on std.dev</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xBaU5kZY9czR3mdw4L1h5A.png" /></figure><p>kiiiiiilling it</p><p>At my last job I spent a little time at Pivotal, where pairing was mandatory and probably the biggest culture shock for incoming developers when learning their very opinionated style of agile.</p><p>I mostly found it useful if there was a knowledge imbalance on the part of the codebase you were working on, but if there was TOO much imbalance your partnership tends to devolve into pointing out nits as you type and you begin to desperately crave some time alone</p><p>My pair and I separately devised a devious plan to get the other hooked on Neko Atsume so we could have a moment to ourselves while the other checked their cats.</p><p>Unfortunately it backfired for both of us + we became hopelessly accomplished cat parents with full sincerity.</p><p>At Medium there isn’t a culture of pairing at all, and I’ve been doing more tech lead roles lately so I haven’t had the opportunity to really ignore distractions and code for a while</p><p>and</p><p>HOT DAMN</p><p>the last few days we spent building series were amazing</p><p><strong>a lovely teammate:</strong> alex can you help me figure out this weird styling thing with recaptchas</p><p><strong>me (normally a sage infinite pool of wisdom):</strong> you’re gonna have to dig deep and figure it out cause it’s haaaaackweek and i’m busy building seeeeriiiiies woooooo</p><p><strong>a lovely teammate</strong>: …so i’ll ask you on thursday then</p><p><strong>me:</strong> yes, that would be amazing thank you</p><p><a href="https://medium.com/u/d2e2f44df9bf">Emma</a> + I have pretty complementary skill sets and are both decent project managers</p><p>and by having someone to bounce off the cuff questions and cavalierly cut scope/reorganize priorities, we sprinted forward amazingly quickly.</p><p>The PR review process is also one of the most painful parts when you’re trying to move fast, so both of us having full context saved us the back and forth of debating semantics over github comments + ultimately pushed better code rapidly.</p><p>We ended up having time to put in a slew of fancy bells + whistles including <strong>resumability</strong></p><p>(pick up where you left off reading!)</p><p><strong>a fancy loading state</strong></p><p>(to soften that …giant js bundle download you’re waiting for)</p><p>and integrating a much jankier version of the <strong>clap button</strong> that we built together for normal medium</p><p>😂 👏 👏 👏 😭</p><p>let us know what you think!</p><p>cheeeers from medium hq</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c5eae0da6604" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WEAVE]]></title>
            <link>https://medium.com/series/weave-8c121d2efc24?source=rss-916052e51fa3------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c121d2efc24</guid>
            <dc:creator><![CDATA[Alex Kimi Wolfe]]></dc:creator>
            <pubDate>Sat, 27 Jan 2018 02:05:29 GMT</pubDate>
            <atom:updated>2018-02-04T09:46:18.430Z</atom:updated>
            <content:encoded><![CDATA[<p>Since my first encounter with <a href="https://www.instagram.com/ryojiimaizumi/">ryojiimaizumi</a>’s work, a flame has burned in my heart</p><p>he was the hairstylist for aya + bambi, responsible for their sharp ridiculously cool goth crops</p><p>but most of his work are these wildly fantastical updos, sculpted out of colorful kisch+ odds +ends</p><p>he’s also got the most intense collection of amazing hats.</p><p>I’ve never wanted to try to recreate anything as badly.</p><p>After obsessively watching all of the insanely cool stop motion timelapses in his feed, I had some semblance of a plan.</p><p>I’ve got hair, but not ….mountains of it.</p><p>step one was to artifically create some vooooluuuume. i knew there was only one place to begin my search</p><p>the one true trove of treasures</p><p><a href="https://www.aliexpress.com/wholesale?catId=0&amp;initiative_id=SB_20180203222221&amp;SearchText=kanekalon+hair+braid">alibaba express</a></p><p>There’s a huge selection of these kanekalon hair extensions, that come in packs of 6 for ~$5…..with 3 months of shipping.</p><p>I ended up snagging <a href="https://www.aliexpress.com/item/Feilimei-Ombre-Blonde-Colored-Crochet-Hair-Extension-Kanekalon-Hair-Synthetic-Crochet-Braids-Ombre-Jumbo-Braiding-Hair/32830720035.html?spm=2114.search0104.3.287.34aaa8527ZM3tb&amp;ws_ab_test=searchweb0_0,searchweb201602_5_10065_10344_10130_10068_10324_10547_10342_10325_10546_10343_10340_10548_10341_10545_10084_10083_10618_10307_5722315_10313_10059_10534_100031_10103_441_10624_442_10623_10622_10621_10620_10142,searchweb201603_25,ppcSwitch_4&amp;algo_expid=3366fa84-d712-4287-978b-498cab323f25-36&amp;algo_pvid=3366fa84-d712-4287-978b-498cab323f25&amp;transAbTest=ae803_5&amp;priceBeautifyAB=0">these ones</a> since what more could you ask of pastel unicorn hair</p><p>the next obstacle was my complete lack of even the basics in hair coordination</p><p>fortunately my sister <a href="https://medium.com/u/1f05433a3684">Kiera Wolfe</a> was staying with me that summer rent free, and had watched a youtube video about weaves one time</p><p>so with an unlimited supply of someone willing assistance</p><p>we were reaaaaaady</p><p>i’ve got super long brown hair with blue ends, and she somehow managed to get it all in tight braids, swooping the ends back up and firmly attaching them to my head with a small army of pins</p><p></p><p>we then hooked each of the massive jumbo braids into this base kind of like a crochet knot,</p><p>pulling the middle loop through and threading back the rest</p><p></p><p></p><p></p><p></p><p>….this continued</p><p>until we had something that looks kind of like this all the way around</p><p></p><p>At this point we started braiding bits of it at random and piling on praying that some sort of overall structure would be our reward.</p><p>….things started looking kinda shapeless + dire, so we stop taking selfies as we look into each others eyes in increasing desperation, neither one of us willing to admit we had taken mounds of fluffy cotton candy and tortured them into this strange existence.</p><p>kiera paints my eyebrows in purple while i struggle to define some sort of vision</p><p></p><p>this lifts everyone’s spirits</p><p>there’s only one thing that can save a shapeless amorphous mass threatening to overwhelm your entire head</p><p>and that’s a pile of WHIMSICAL ACCESSORIES</p><p></p><p>not quite as whimsical as ryojis, i did not delve greedily enough or as deep into alibaba as I needed to in order to emerge with plushie usagis or plastic syringes but it was gooooooood enough</p><p>I continue pinning while holding a vision of crystal tokyo firmly in my mind, and kiera goes ham with the little stars</p><p></p><p>and we EMERGE FROM THE DARKNESS TOGETHER</p><p>alright the rest of this thing is just me taking a ridiculous number of snaps of the final look</p><p>thank you kiiiiiera the light of my life for making this remotely possible</p><p></p><p></p><p></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*F9iq99W4fbqhLNfdrZNiEQ.gif" /></figure><p></p><p>untiiiiiiiiil next time</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c121d2efc24" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[two girls and a funeral]]></title>
            <link>https://medium.com/series/memorial-f57d249c9138?source=rss-916052e51fa3------2</link>
            <guid isPermaLink="false">https://medium.com/p/f57d249c9138</guid>
            <dc:creator><![CDATA[Alex Kimi Wolfe]]></dc:creator>
            <pubDate>Sun, 18 Dec 2016 10:54:40 GMT</pubDate>
            <atom:updated>2016-12-18T11:46:01.115Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RQvjTvEesrWg0ZsvG5s-Hw.png" /></figure><p>erin buzzed my phone 3 times before i managed to open my eyes</p><p>my hand fumbled around in the dark to silence it. it was 5am and she had woken up panicked in the night</p><p>worried about missing the memorial.</p><p>my uncle jake passed away last weekend.</p><p>we slid into the very edge of the second pew dressed in black velvet and heavy coats, emblems of love from our grandmother, to the dearly departed husband of her sister.</p><p>they roll the slideshow. his life tinted sepia flashes before our eyes.</p><p>I can’t tell my grandmother and auntie setoia apart in the images. they are beautiful with round faces and long limbs and matching bobs.</p><p>eventually i find a mark of distinction. auntie setoia beams, especially when uncle jake is in the frame. My grandmother yoshiko stands next to her and only ever makes the slightest coy smile.</p><p>uncle jake was 19 when they took him</p><p>and incarcerated his family in the desert.</p><p>they called them internment camps. but they were surrounded with barbed wire and the guards watched them from tall towers while clutching semiautomatic weapons.</p><p>my grandmother never talks about her time there. Only recently now that the edges of her mind are slipping away does she refer to it as jail.</p><p>at the time he was a buddhist. and a teenager. and furious.</p><p>his draft notice was delivered by an armed guard to the long wooden barracks his family shared with four others</p><p>light filtered in through the slits in the ceiling, where the raw wood, worn by the elements</p><p>had separated. letting in the dust.</p><p>he was expected to fight for our country</p><p>his country.</p><p>after being locked away.</p><p>what the fuck. what would it be like to fight for a country that hates you.</p><p>a country that</p><p>upheld <em>Korematsu vs. the United States</em>, and in turn, ruled the Japanese internment, constitutional.</p><p>despite evidence that the army had falsified all documentation that any Japanese American had sent radio transmissions to Japan.</p><p>(this was in 19 fucking 83. the original verdict was made in the 40s)</p><p>he went.</p><p>hoping to prove his loyalty.</p><p>all of their loyalty.</p><p>i found out he interrogated japanese prisoners of war, and was sent behind enemy lines to recover the bodies of fighter pilots from their wreckage</p><p>to identify them and send them home.</p><p>risking his live in service of the already dead.</p><p>He was never allowed to talk about it.</p><p>An old and frail uncle jake holds a giant medal.</p><p>Two years ago Obama awarded him, and his entire division, the Congressional Gold Medal</p><p>all the kids from the surrounding neighborhoods came to see it.</p><p>it’s the highest honor a civilian can receive</p><p>As two uniformed officers sharply unfold the american flag over his casket</p><p>and then proceed to slowly, painfully, fold it into tight small triangles.</p><p>I think</p><p>Iamsafeandshelteredandnaive andFURIOUS whyhaveIneverheardaboutanyofthis.</p><p>the last scene in the slideshow uncle jake is blowing out candles on a cake made for him by my auntie vera. surrounded by more family than can fit in the frame.</p><p>they roll the credits.</p><p>The pastor tells us that the difference between a christian memorial and a non christian memorial is hope.</p><p>That knowing that we can see my uncle jake again rejuvenated and eternal, rewarded for his good works, is what should let us leave this room with light hearts.</p><p>It rings hollow for me.</p><p>I don’t believe in anything after death.</p><p>I believe that if you reduce the universe down to its finest particles</p><p>and examine them one by one.</p><p>you won’t find a single shred of naturally occurring hope or justice or mercy anywhere in existence</p><p>that they are lies that humanity created.</p><p>albeit beautiful ones.</p><p>There is no divine presence to uphold and bestow them upon us.</p><p>It is a constant fight to reforge them generation after generation.</p><p>I left with a light heart because my uncle jake was a good man.</p><p>who led a good life.</p><p>and passed that goodness onto his children and his children’s children.</p><p>despite going through some fucked up shit.</p><p>in a world where goodness does not naturally occur.</p><p>we must work to be good.</p><p>Recently the Japanese internment</p><p>has been brought up as precedent.</p><p>to do the same to the Muslim Americans living in our country.</p><p>Overcoming fear.</p><p>To do the right thing.</p><p>Is a human problem.</p><p>Don’t fuck up.</p><p><em>“I would like to see the government admit that they were wrong and do something about it so this will never happen again to any American citizen of any race, creed, or color.”</em></p><p><em>“If anyone should do any pardoning, I should be the one pardoning the government for what they did to the Japanese-American people.”</em></p><p><em>“…full vindication for the Japanese-Americans will arrive only when we learn that, even in times of crisis, we must guard against prejudice and keep uppermost our commitment to law and justice.”</em></p><p>— closing statement by Fred Korematsu</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f57d249c9138" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>