<?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 xarissa on Medium]]></title>
        <description><![CDATA[Stories by xarissa on Medium]]></description>
        <link>https://medium.com/@xarissaa?source=rss-a52a379799a9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*BLaY5uojHU1b4e-0.jpg</url>
            <title>Stories by xarissa on Medium</title>
            <link>https://medium.com/@xarissaa?source=rss-a52a379799a9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 17:39:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@xarissaa/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[Remote But Not Forgotten]]></title>
            <link>https://medium.com/@xarissaa/remote-but-not-forgotten-47e1278c922f?source=rss-a52a379799a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/47e1278c922f</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[features]]></category>
            <category><![CDATA[remote]]></category>
            <dc:creator><![CDATA[xarissa]]></dc:creator>
            <pubDate>Thu, 12 Apr 2018 14:29:48 GMT</pubDate>
            <atom:updated>2018-04-12T17:42:45.637Z</atom:updated>
            <content:encoded><![CDATA[<p><em>We have offices on two continents and we’re growing fast. How do we keep everyone on the same page, whichever time zone they’re in?</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GGFqomc5VVXUvaUec1GVuA.png" /><figcaption>Illustration by Stephen Carlson</figcaption></figure><p>Last week, we introduced <a href="https://trackchanges.postlight.com/meet-postlight-lebanon-fbfe8a110a17">Postlight Lebanon</a>, our outpost in Beirut. We were able to get it up and running pretty fast, but first we had to have a lot of conversations with ourselves about, well, HOW we were going to do this.</p><p>This is probably obvious, but managing teams across oceans and time zones, on fast shipping cycles, can be really, really hard. Ultimately, we needed this expansion to be a great experience not just for us and our clients, but for the people we would be hiring. As Rich said in our last piece, we were determined to keep the quality of our work high and the culture intact, so we approached this growth with as much intention as we could.</p><p>We might never have a perfect solution, but here are a few things that are working for us, in the words of some of our remotes.</p><h3>Time Zones Are a Gift</h3><p>Usually I arrive at the office at 8 am Beirut time, and while drinking my Turkish coffee, I start reading whatever my colleagues in the U.S. were discussing on Slack while I was sleeping. I go through all of the channels: social discussions, #music and #watchables, #random, administrative announcements, and, finally my project-related channels. This is where I find everything that was implemented while I was asleep, what problems have cropped up, and what still needs doing. (I also have a good sense of how my New York colleagues are feeling, best represented by the heated debates in #music about whatever’s playing on the Sonos.)</p><p>Next, I make the same rounds through our issue tracking applications, primarily Jira and GitHub. By the time I’ve updated myself on everything, I have a meaningful list of what I need to work on and how to organize my time.</p><p>Now that I’m caught up, I can start with implementation. Because everybody in the U.S. is sleeping, my day is wonderfully free of interruptions or last-minute meetings. I can experiment or make big changes and migrations without guilt, because I know no one is dependent on my work at that exact moment. Asynch communication can really work in a developer’s favor!</p><p>At around 4–5 pm my time, the U.S. is awake, drinking vastly inferior non-Turkish coffee, and I overlap for a few hours with my fellow Postlighters. The first thing I do (after saying hi!) is pass my questions to colleagues that are working on the same projects. If there’s a question or a blocker that’s been in my way during the day, someone will investigate, leaving an explanation on Jira, Slack or GitHub for me to see tomorrow.</p><p>Finally, I take calls and do stand-ups, all scheduled between 5pm and 6:30pm so I don’t have to do overtime. If there’s a meeting I can’t make, I always receive highlights and notes of the meeting afterwards.</p><p>For me, it’s a great situation. I can have discussions and mix ideas and views within our open culture. I can brag about Lebanese food, wine and sunny beaches while my American colleagues are dealing with snow. And I get to walk the astonishing streets of New York few times a year, listening to ‘Empire State Of Mind’.</p><p><em>-</em><a href="https://medium.com/@alexiakl"><em>Alexi Akl</em></a><em>, Senior Engineer, based in Beirut, Lebanon</em></p><h3>Make It About You</h3><p>Postlight is a remote-friendly company, but it’s not all on them to make things work. There are habits that any far-flung developer needs to build, even if they’re only armed with Slack and a webcam. If I were advising someone about to take on their first remote assignment, here’s what I would recommend:</p><ul><li><strong>Ask questions early and often</strong>, and ask them in public channels. If you’re hung up on a tricky part of the codebase and ask a coworker for help IRL, someone in earshot might be able to interject a quick fix. Slack DMs and emails don’t allow for ambient knowledge— if you keep your questions public, you can get help from unexpected places. (And the public answer might save the next person to run into the bug).</li><li><strong>Give status updates often. </strong>It’s easy — and tempting — to hole up with an assignment and go quiet for a week until it’s complete. In the office, your coworkers would know you’re busy, but if you’re just silent in Slack or Github, it’s hard for them to tell if you’re stuck, working on a different project, or went for a walk and never came back. Save them some worry. Give a short daily update, even if it’s “still working on this PR, and the timeline looks the same.”</li><li><strong>Show and tell.</strong> Did you read a good post about API design over lunch? Have you seen a good screencast lately? Share the link and write a summary. The best discussions in our #engineering channel are often prompted by a pasted link.</li><li><strong>Let #random go</strong>. One benefit of tools like Slack is that they provide a digital water cooler, a place where everyone on a team can chat about what’s going on outside work. This can be great for remotes — but don’t feel like you need to be part of every conversation! Give yourself permission to miss out on some of it. Decide which channels (or email lists, or forums, or threads) you want to treat as ephemeral, mute them, and drop in when you have the time or energy.</li><li><strong>Find equivalents</strong> for body language and gestures. We say things with our faces and posture in the office: “I’m trying to concentrate.” “This is going really well!” “Mind if I interject?” When you’re at home projecting these same vibes to a laptop screen, it can feel like you’re sending bizarre signals to your coworkers. Remember that you’re just a Slack avatar most of the time. It can be hard to give subtle micro-updates, but a Slackmoji here and a short status ping there can go a long way. Your co-workers can’t read your mind through WiFi. (Yet.)</li></ul><p><em>-</em><a href="https://medium.com/@droob"><em>Drew Bell</em></a><em>, Engineer, based in Missouri</em></p><h3>Save Your Sociality for When It Matters</h3><p>Remote work has, for me, always been a pact between two Kevins. There is part of me — a large part of me — that enjoys a murmuring office, group lunches, kitchen beers when the clock strikes 5:02. That’s the first Kevin, who breaks silences. But there is another: one who often turns from his monitor to rest his forehead on the window of the home office, who closes Slack to go on walks, who keeps ASMR on in a background tab. I work remotely to keep that Kevin alive. The fact that Postlight helps me do this seems, every time I look out the window, like a small miracle.</p><p>It only works because the company fosters a loose, forgiving, and asynchronous style of work. It’s okay to not immediately reply to stuff in Slack. Even mentions. Recently a coworker observed that we’ve adopted a habit of skewing names to avoid pinging people: if Drew’s on vacation that day, I might talk about d.rew. ‘Do Not Disturb’ mode is encouraged. And our New-York based coworkers are always willing to hop in a Hangout.</p><p>Fundamentally, Postlight understands that when we’re forced to be in one place we may not be bringing our best selves. This let us leap easily to Lebanon, and it means that we carry the company with us to client visits. And, for the few times a year when the entire company does gather in New York, it means that the first Kevin gets to grab lunches, and chat, and break a few silences.</p><p><em>-</em><a href="https://medium.com/@kevboh"><em>Kevin Barrett</em></a><em>, Lead Engineer, based in Maryland</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fe923b9%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fe923b9%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/ce41bc8c9c07c5043cf1b38b9db2dbb0/href">https://medium.com/media/ce41bc8c9c07c5043cf1b38b9db2dbb0/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47e1278c922f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Research, Free to a Good Home]]></title>
            <link>https://medium.com/@xarissaa/ux-research-free-to-a-good-home-e2f1d5d7c008?source=rss-a52a379799a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2f1d5d7c008</guid>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[features]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[bugs]]></category>
            <category><![CDATA[please-fix]]></category>
            <dc:creator><![CDATA[xarissa]]></dc:creator>
            <pubDate>Thu, 08 Mar 2018 16:18:35 GMT</pubDate>
            <atom:updated>2018-03-08T19:34:21.857Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EayZggWq88L1-fV0DTGhDA.jpeg" /></figure><p>Everyone at Postlight is a product snob. Whenever we find a bug, anywhere, we yell about it. Sometimes loudly, or into our Slack #general channel, so everyone else gets to complain about it too. “This software is garbage!”</p><p>It doesn’t even have to be a big bug. Did someone find a small interaction flaw in a beta version of a feature? It’s trash. Burn it down. We hate everything.</p><p>I’m kidding, of course. We exaggerate because we care. But it’s startling how many bugs — or just missed opportunities!— are lurking in the platforms that millions of people use every day.</p><p>We’ve compiled some of our (least) favorites here, and we invite you to add your own in the comments.</p><h3><strong>Google Lives in the Past</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y6mn481_l0V5GhbCBXyyng.png" /></figure><p>Pretty much every calendar I’ve used suffers from a major UX gripe of mine: If you have set your calendar to a monthly view, it displays the entirety of the current month regardless of how many days are left in it. That’s fine at the beginning of a month, but once you’re in the home stretch, a massive part of the interface — you know, that part of the calendar you look at the most — is taken up by meetings that happened in the past. Release yourselves from your Gregorian chains, calendar designers! I would love an option in Google Calendar to have a rolling view of my monthly appointments so that the most recent week stays at the top of my view. This is the default view of the calendar I keep in my mental file entitled How To Fix All Of Google Calendar’s Problems.sketch, in case anyone wants to borrow it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/226/1*EteeVaT-LeGe8fcS5S_Vxw.gif" /></figure><p>That said: In a fit of angry googling — “how is calendar formed,” etc — I found a hidden solution to this: click and drag a <em>date range </em>in the mini calendar in your sidebar to create a custom view that replicates what I’m looking for. I showed some other self-professed power users of the G Suite and all were amazed. Why Google hasn’t made that view the default, I still don’t know.</p><p><em>-Matt Quintanilla, Director of Product Design</em></p><h3><strong>Where Did I Go, Slack?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NWkPZVlKp3Fvbjq0QB6BnQ.png" /></figure><p>The Slack app for iPad has a bug in the design of the channel navigation that drives me up a wall. When I’m using the app (which, lets be honest, is pretty much anytime I’m not asleep), my previously visited channel names appear a blackish grey instead of their standard channel colors, for no apparent reason.</p><p>Even worse, the current channel name disappears — it goes white on a white background. It’s not the end of the world, as I can just glance to the right and see what channel I’m in, but I SHOULDN’T HAVE TO. Presumably this is a UIKit bug of some kind, and I imagine it would be easy to fix, but this shouldn’t have ever made it out of internal testing.</p><p><em>-Cody Cowan, Director of Growth &amp; Partnerships</em></p><h3><strong>A Good Idea That Doesn’t Work</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l_0Ef-yUr0KgejGleHY5ZA.png" /></figure><p>I’ve long needed the ability to generate and test prototypes directly within my preferred design tool, so I was elated when Sketch announced built-in prototyping last month. Unfortunately, unless all of your artboards are the same size, and none of them exceed the height of your window, it falls short. There is currently no way to set the zoom of the artboard inside of the preview window, which makes it effectively unusable for any web pages or long mobile screens.</p><p><em>-Matthew Famularo, Product Designer</em></p><h3><strong>Feedly’s Bad Feeds</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*vLxDdWlDM4inr0pzO3XQ3A.png" /><figcaption>This post won’t go away. It’s haunting me.</figcaption></figure><p>After the tragic death of Google Reader, I migrated all my RSS feeds to Feedly. But it’s so bad! There are three different bugs on this screencap alone.</p><p>First, I don’t know how stuff gets added to the Read Later queue. I must be doing something with my finger when I scroll through the feeds, because every now and then I get a notification that something has been added. But I cannot tell you how I made that happen or, more importantly, how to make it stop. So I have to periodically go to that section to empty out all the stuff that’s landed there.</p><p>Then, of course, I can’t empty it. I’ve tried dozens of times to mark everything as read, using the top navigation menu, but nothing happens. This particular post is from 706 days ago.</p><p>Finally, there’s that huge white space, which I see in posts all over the app. There’s supposed to be an image there, but this article from Nieman didn’t have an image embedded. Why not just collapse the empty space? Why give me a white box (or a gray one on desktop) when there’s literally NOTHING to see?</p><p><em>-Xarissa Holdaway, Marketing Communications Manager</em></p><h3><strong>Sketch, But Too Much</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*0-aR-jpMrKoo9nD-Vs0oKA.gif" /></figure><p>I have a love-hate relationship with Sketch. The software is powerful, intuitive and it enables me to turn quickly turn ideas into designs. But I’ve been struggling with a bug for the past year. Sometimes when I copy and paste a symbol from one art board to another, sketch duplicates that symbol. Unbeknownst to me, my symbols page is littered with <em>Nav/Basic Copy 1, Nav/Basic Copy 2, Nav/Basic Copy 3, Nav/Basic Copy 4, Nav/Basic Copy 5</em>, etc. etc. It doesn’t cripple my workflow, but it adds a level of friction by forcing me to manually resolve duplicate symbols.</p><p><em>-Will Denton, Product Designer</em></p><h3><strong>Just, Why?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nNVMbe3Gc7bZ3ZaPxv6cVw.png" /><figcaption>New Tab, New Tab, New Tab…..</figcaption></figure><p>About once a week, Slack decides that I am no longer eligible to click a link in a channel and open it in Chrome. Instead, every click opens another new tab with Google’s search homepage. It takes half a dozen clicks before I realize I’ve lost the ability to link out of Slack. Staring at my stack of new tabs, all I can do is sigh, defeated. The only fix is to restart everything.</p><p>In Slack’s defense, I am a compulsive tab hoarder. At any given time, I probably have twenty or so pages open that I swear I’ll come back and read. So it’s entirely possibly this bug is actually an intervention from Slack and Chrome–a friendly way of telling me “you do not need any more open tabs on your computer, Meredith.” But Slack shouldn’t be telling me how to live!</p><p><em>-Meredith Franzese, Managing Partner</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fe923b9%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fe923b9%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/ce41bc8c9c07c5043cf1b38b9db2dbb0/href">https://medium.com/media/ce41bc8c9c07c5043cf1b38b9db2dbb0/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2f1d5d7c008" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>