<?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 Avand Amiri on Medium]]></title>
        <description><![CDATA[Stories by Avand Amiri on Medium]]></description>
        <link>https://medium.com/@avand?source=rss-827ac8e4ae00------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*uRf1xD16DZMiCJST8Svcyw.jpeg</url>
            <title>Stories by Avand Amiri on Medium</title>
            <link>https://medium.com/@avand?source=rss-827ac8e4ae00------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:16:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@avand/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[Engineering Interviews: New & Improved for the Era of AI]]></title>
            <link>https://medium.com/@avand/engineering-interviews-new-improved-for-the-era-of-ai-faa11394abcf?source=rss-827ac8e4ae00------2</link>
            <guid isPermaLink="false">https://medium.com/p/faa11394abcf</guid>
            <category><![CDATA[pragmatism]]></category>
            <category><![CDATA[interview-questions]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[candidate-experience]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Avand Amiri]]></dc:creator>
            <pubDate>Thu, 11 Jan 2024 01:48:16 GMT</pubDate>
            <atom:updated>2024-01-11T04:10:00.885Z</atom:updated>
            <content:encoded><![CDATA[<h4>For decades, software engineers have been hired through an anachronistic and highly academic interview process. It’s time to rethink the process to improve the candidate experience, evaluate pragmatic qualities, and assess a developer’s ability to leverage AI to improve efficiency.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zYeI79MdfYk8Ucmf4nSLJg.png" /><figcaption>“Why is it so hard to display the birthday date on the settings page?” — <a href="https://www.youtube.com/watch?v=y8OnoxKotPQ&amp;ab_channel=KRAZAM">Krazam</a></figcaption></figure><p>One of the longest running jokes about software engineers is that we’re professional Googlers, which is funny because there is some truth to it. But, I promise, that’s not all we do.</p><p>Based on the last 20 years of engineering web applications, here’s <a href="https://www.youtube.com/watch?v=StIcRH_e6zQ">what I’d say I do</a>:</p><ol><li>Listen to a problem, ask clarifying questions, and design solutions to fit without over- or under-engineering. There are patterns one can be familiar with but, for the most part, doing this well involves being a great listener, collaborator, a bit of creativity, and the application of prior experience, which obviously improves over time.</li><li>Write code that implements a solution, while minimizing the accumulation of technical debt or bugs. To do this well requires deep familiarity with a specific programming language and/or framework (e.g., Rails, .NET, Java, React, etc.). It also involves knowing where to turn for help, hence the joke about being professional Googlers.</li><li>Test and deploy code. Identify edge cases, debug unanticipated problems, and ensure operability from development through to production.</li><li>Modify an existing system to support new functionality without breaking existing functionality. Without the right stewardship, software can become an unmanageable set of interconnected dependencies, where fixing something, breaks another.</li><li>Propose changes, communicate with a team, constructively avoid “painting into a corner,” advocate for the right balance of quality &amp; speed, and keep underlying technology current. This is another extremely difficult part of the job because everyone expects it to get done but never allocates time for it.</li></ol><p>As I look for a full-time job as a software engineer, I’ve had an opportunity to study the anachronistic interview process that’s still somehow in vogue. It’s remarkable that the interview process for software engineers really hasn’t changed in the two decades I’ve been in the field.</p><p>I find this especially bizarre with the arrival of AI on the scene as a thought partner and collaborative coding assistant.</p><blockquote>The most damaging phrase in the language is “We’ve always done it this way!”</blockquote><blockquote>— <a href="https://quoteinvestigator.com/2014/11/27/always-done/">Grace Murray Hopper</a>, computer programming pioneer (1987)</blockquote><p>In this post, I’ll explore the following:</p><ol><li><strong>What’s broken</strong> in the way engineering interviews have been done?</li><li>How could an engineering interview evaluate a candidate’s ability to <strong>leverage AI</strong> to write code more efficiently?</li><li>How to <strong>rethink the interview process</strong> to evaluate for the pragmatic qualities that make up day-to-day work as an engineer.</li></ol><h3>The Status Quo: “Sport Coding”</h3><p>Most first-round engineering interviews are a <a href="https://leetcode.com/">LeetCode</a>-style coding test. Something like, “given a string, find the longest palindromic substring.” You know, stuff you do every day as an engineer. 🙄</p><p>Candidates have ~45 minutes to solve a question, while someone watches their every keystroke. A question like this is almost always the first Technical Phone Screen/Assessment (TPS/A) a candidate does remotely before a longer, multi-session interview day, which may have 2–3 more questions like this. <a href="https://www.youtube.com/watch?v=MCapEm8Nu7c">Fun!</a></p><p>Sometimes the questions are rooted in something domain-specific. For example, when I interviewed with one networking company, they asked me a question about how to summarize network downtime across many devices. At first it seems obvious and good that the question is rooted in the company’s work but the pitfall is that these problems are too challenging, often solved by multiple engineers over days or weeks.</p><h4><strong>These interviews are stressful</strong></h4><p>Constraint may be the mother of invention but no one does their best work when they’re stressed. I am hard pressed to think of any better way to add stress than to set a timer and watch over someone’s shoulder while they work. Can you?</p><h4><strong>These interviews are only relevant ~5% of the time</strong></h4><p>In the 20 years I’ve been coding, I use low level data-structure/algorithm knowledge less than 5% of the time. There are “leet” engineers for whom this number is much higher. Where I consider myself a “customer’s engineer,” “leet” engineers tend to be more of an “engineer’s engineer.” On software teams need for both types and depending on the nature and stage of the product, teams will bias one way or another.</p><p>In the “pick two” game of price, speed, and quality, product engineers like myself can solve for speed and quality. Which is great, because running software has gotten extremely inexpensive.</p><blockquote>Hardware is cheap, and programmers are expensive.</blockquote><blockquote>— <a href="https://blog.codinghorror.com/hardware-is-cheap-programmers-are-expensive/">Jeff Atwood</a>, creator of StackOverflow (2008)</blockquote><p>It’s almost <em>never</em> the right choice to spend a bunch of engineering time optimizing code to run faster because it’s almost <em>always</em> cheaper to throw more compute at the problem. When (and for many tech startups it’s really a matter of “if”) the time comes (e.g., when usage is high), it’s usually also true that there are resources available to optimize. Experienced engineers should understand this balance and know how to walk the line.</p><h4><strong>AI has made writing code more efficient</strong></h4><p>Interviewers tell candidates they can “Google for reference material” but finding and copying an existing solution is universally considered cheating. Companies safeguard their interview questions and change them occasionally to prevent rote solutions.</p><p>But <a href="https://medium.com/@avand/reflections-in-transition-247a2800ab12">AI can write code that solves a brand new question</a> that’s never been asked. So why are we evaluating human intelligence with work that artificial intelligence can do faster and more accurately?</p><p>Tools like <a href="https://github.com/features/copilot">GitHub Copilot</a> can be trained on existing code bases and make code suggestions, which often account for edge cases an engineer might miss. Leveraging AI to write code more efficiently is more and more relevant each day. For example:</p><pre>class User &lt; ActiveRecord::Base<br>  ARTICLE_LIMIT = 25<br><br>  def article_count<br>    # On the next line, I wrote &quot;Article.&quot; and Copilot suggested the rest<br>    Article.where(author_id: id).count<br>  end<br><br>  def remaining_article_count # I wrote the method definition,<br>    ARTICLE_LIMIT - article_count # Copilot wrote the rest<br>  end<br>end</pre><p>When I mentor junior engineers, I encourage them to master keyboard shortcuts because it increases accuracy and efficiency. In the same way, AI can make programming more efficient. It can’t replace the engineer altogether (at least not yet)—sometimes AI suggestions are irrelevant and distracting—but knowing when and how to use them can really speed things up.</p><h3>A Different Interview: Async, Ambitious, AI</h3><p>Before we zoom out and consider the entire candidate experience, let’s rethink the first TPS interview and see if we can get the best out of candidate by reducing their stress, evaluate relevant and pragmatic skills, while also testing a candidates ability to leverage AI.</p><p>I was recently asked to build a clone of Google Calendar’s day view that allows creating, editing, and deleting events. As I read the spec, panic started to set in. My brain was processing it as, “Google Calendar! This is the most ambitious coding challenge I’ve ever done in 45 minutes—I hope I can do it!” Remember, there’s someone else watching my every move so I’m stressed and with each tick of the clock I’m getting more stressed.</p><h4><strong>Save time &amp; reduce stress by making it a “take home” project</strong></h4><p>Instead of losing 15 minutes to pleasantries that inherently appear when two people sit down for an interview, give the candidate the full hour to code. Enforce the time constraint by asking them to record their screen while they work and submit both their code and the recording. There are a bunch of pros that come along with this approach, which my friend <a href="http://keithschacht.com/">Keith</a> shared with me:</p><ul><li>There’s no scheduling overhead. “Here’s the assignment, please find 1 hour to do it using whatever tools you like and submit within the next week.” That’s it. The candidate and reviewers work asynchronously, which should mean everyone’s working in conditions that are personally optimal.</li><li>Take home projects are notorious for going over time. But the screen recording keeps candidates honest.</li><li>Reduce reviewers’ time commitment. As a reviewer, review solutions in batches. Watch the corresponding screen recordings for only the stand out solutions and increase playback speed to 1.5x or more for even more saved time.</li></ul><p>While most of the take home projects I’ve been given are a assigned digitally, I recommend giving the candidate an optional 15 minute window to talk with an engineer after they’ve had time to review the assignment so they can ask questions and vet their assumptions before getting to work.</p><h4><strong>Set clear expectations &amp; encourage ambition</strong></h4><p>I’ve done a few interviews where I did exactly what was asked but didn’t progress to the next round. As an interviewer it’s good to know specifically how to evaluate a candidate, especially on big teams. It’s even better if the candidate knows how they’re being graded so they’re set up to succeed.</p><p>Setting clear expectations might look like:</p><ol><li>Meets some expectations: “we expect more than this but suspect most solutions to look like this,” the status quo, average.</li><li>Meets expectations: “here’s a great solution that meets our expectations but the bar is still higher and we’re looking for more from the ideal candidate,” passing, above average.</li><li>Exceeds expectations: “here’s a solution that exceeds our expectations and probably would not have been possible in just an hour without AI support,” top candidates, well above average.</li></ol><p>In the case of the Google Calendar example, status quo might be a clunky and barely functional version of the single day view, where some of the requirements are missing. Meeting expectations might build on that—now it’s more useable and fully functional to the requirements. Exceeding expectations extends functionality and expresses the candidates point of view and creativity.</p><p>This rubric is very grounding as a candidate. If I can play a video of an example at each level, especially on my own time, I’ll be a lot more confident and comfortable.</p><h4><strong>Exceed expectations by leveraging AI</strong></h4><p>Today, if I’m asked to <a href="https://chat.openai.com/share/8dbf1f6a-b0f5-4ffc-ba01-fbc43e1c1889">implement a clone of Google Calendar’s day view that allows creating, editing, and deleting events</a>, using AI is a great way to hit the ground running. The full prompt is behind that linked transcript and the <a href="https://codesandbox.io/p/sandbox/broken-dawn-zs97lj?layout=%257B%2522sidebarPanel%2522%253A%2522EXPLORER%2522%252C%2522rootPanelGroup%2522%253A%257B%2522direction%2522%253A%2522horizontal%2522%252C%2522contentType%2522%253A%2522UNKNOWN%2522%252C%2522type%2522%253A%2522PANEL_GROUP%2522%252C%2522id%2522%253A%2522ROOT_LAYOUT%2522%252C%2522panels%2522%253A%255B%257B%2522type%2522%253A%2522PANEL_GROUP%2522%252C%2522contentType%2522%253A%2522UNKNOWN%2522%252C%2522direction%2522%253A%2522vertical%2522%252C%2522id%2522%253A%2522clr8ico7z00663b6h1mfdh54w%2522%252C%2522sizes%2522%253A%255B70%252C30%255D%252C%2522panels%2522%253A%255B%257B%2522type%2522%253A%2522PANEL_GROUP%2522%252C%2522contentType%2522%253A%2522EDITOR%2522%252C%2522direction%2522%253A%2522horizontal%2522%252C%2522id%2522%253A%2522EDITOR%2522%252C%2522panels%2522%253A%255B%257B%2522type%2522%253A%2522PANEL%2522%252C%2522contentType%2522%253A%2522EDITOR%2522%252C%2522id%2522%253A%2522clr8ico7y00633b6hu3byy2bt%2522%257D%255D%257D%252C%257B%2522type%2522%253A%2522PANEL_GROUP%2522%252C%2522contentType%2522%253A%2522SHELLS%2522%252C%2522direction%2522%253A%2522horizontal%2522%252C%2522id%2522%253A%2522SHELLS%2522%252C%2522panels%2522%253A%255B%257B%2522type%2522%253A%2522PANEL%2522%252C%2522contentType%2522%253A%2522SHELLS%2522%252C%2522id%2522%253A%2522clr8ico7y00653b6hywl6s6qh%2522%257D%255D%252C%2522sizes%2522%253A%255B100%255D%257D%255D%257D%252C%257B%2522type%2522%253A%2522PANEL_GROUP%2522%252C%2522contentType%2522%253A%2522DEVTOOLS%2522%252C%2522direction%2522%253A%2522vertical%2522%252C%2522id%2522%253A%2522DEVTOOLS%2522%252C%2522panels%2522%253A%255B%257B%2522type%2522%253A%2522PANEL%2522%252C%2522contentType%2522%253A%2522DEVTOOLS%2522%252C%2522id%2522%253A%2522clr8ico7y00643b6h1d7yt92h%2522%257D%255D%252C%2522sizes%2522%253A%255B100%255D%257D%255D%252C%2522sizes%2522%253A%255B54.36017689%252C45.63982311%255D%257D%252C%2522tabbedPanels%2522%253A%257B%2522clr8ico7y00633b6hu3byy2bt%2522%253A%257B%2522tabs%2522%253A%255B%257B%2522id%2522%253A%2522clqzna1sh00013b6h9qfb2uum%2522%252C%2522mode%2522%253A%2522permanent%2522%252C%2522type%2522%253A%2522FILE%2522%252C%2522filepath%2522%253A%2522%252Fsrc%252Findex.js%2522%252C%2522state%2522%253A%2522IDLE%2522%252C%2522initialSelections%2522%253A%255B%257B%2522startLineNumber%2522%253A1%252C%2522startColumn%2522%253A1%252C%2522endLineNumber%2522%253A14%252C%2522endColumn%2522%253A1%257D%255D%257D%255D%252C%2522id%2522%253A%2522clr8ico7y00633b6hu3byy2bt%2522%252C%2522activeTabId%2522%253A%2522clqzna1sh00013b6h9qfb2uum%2522%257D%252C%2522clr8ico7y00643b6h1d7yt92h%2522%253A%257B%2522tabs%2522%253A%255B%257B%2522id%2522%253A%2522clqzna1sh00043b6hh2sxsavm%2522%252C%2522mode%2522%253A%2522permanent%2522%252C%2522type%2522%253A%2522UNASSIGNED_PORT%2522%252C%2522port%2522%253A0%252C%2522path%2522%253A%2522%252F%2522%257D%252C%257B%2522type%2522%253A%2522SANDBOX_ONBOARDING%2522%252C%2522id%2522%253A%2522sandbox-onboarding%2522%252C%2522mode%2522%253A%2522permanent%2522%257D%255D%252C%2522id%2522%253A%2522clr8ico7y00643b6h1d7yt92h%2522%252C%2522activeTabId%2522%253A%2522clqzna1sh00043b6hh2sxsavm%2522%257D%252C%2522clr8ico7y00653b6hywl6s6qh%2522%253A%257B%2522tabs%2522%253A%255B%255D%252C%2522id%2522%253A%2522clr8ico7y00653b6hywl6s6qh%2522%257D%257D%252C%2522showDevtools%2522%253Atrue%252C%2522showShells%2522%253Atrue%252C%2522showSidebar%2522%253Atrue%252C%2522sidebarPanelSize%2522%253A15%257D">resulting code is hosted on CodeSandbox</a>.</p><p>The solution ChatGPT created in a few minutes is at least 80% of the solution I created in ~45 minutes in the hot seat. From this starting point, a candidate still has a bit of work to do to meet or exceed expectations but they will have demonstrated that they know how to leverage today’s modern resources to be more efficient.</p><p>During one interview with an AI company, I was asked to turn <a href="https://github.com/features/copilot">GitHub Copilot</a> off. On the one hand, I see the purist perspective: can the candidate write code without help from an editor or auto-complete? But on the other hand, isn’t it important to evaluate the candidate’s ability to use tools? After all, I’m writing code on a laptop, not a typewriter.</p><h4>Review work in a relaxed, open-ended, and collaborative way</h4><p>The best part of this interview is the debrief. If a candidate’s solution and screen recording merit a meeting, set up 60–90 minutes to review their work together.</p><p>This gives the candidate a chance to present their work, which is actually a lot of what actual work looks like. Sharing a point of view, defending tradeoffs and shortcuts, are things software engineers <em>actually do every day</em>. Of course, the interviewer can also drive and drill into any area too.</p><p>In my experience, these conversations are always really enjoyable.</p><h4>There are probably other ways too</h4><p>What I’ve described above is certainly not the only way. It’s just one approach to reduce stress, save time, and evaluate more pragmatic attributes of a candidate. Another approach I’ve been recommended is to give example code to a candidate for their first coding assignment, asking them to find known bugs and fix them. I encourage you to try different approaches on your team.</p><h3>Zooming Out: The Interview Process as a Whole</h3><p>Designing an interview pipeline is a huge amount of work. It requires dedication from engineers, recruiters, coordinators, hiring managers, and leadership. And hiring for technical roles (not just engineering) brings in even more complexity. It’s not easy, which is why, for the most part, it’s not a great candidate experience. But there are a few ideas that I think are worth exploring to make the process as delightful as possible.</p><h4>Everyone likes a scavenger hunt</h4><p>Ramp gets the credit for this one. If you head over to one of <a href="https://ramp.com/careers">Ramp’s software engineer roles</a>, you’ll see a prompt like this in their application form: “Please decode the text below. Upon decoding, you will be taken to a URL with further instructions on completing the challenge.” This is followed by an encoded string, which if you can decode takes you to another challenge that’s equally cryptic. The whole challenge took me about an hour and it’s a prerequisite to submitting the application.</p><p>A scavenger hunt style is a low-lift way to get early signal from the most motivated applicants.</p><h4>Ask more specific questions upfront</h4><p>Somewhere along the way, a candidate may face an Experience, Behavior, or Collaboration interview, where they’re asked questions like, “tell us about the most exciting project you’ve worked on,” “what’s the hardest problem you’ve every solved,” or “what was the toughest piece of feedback you’ve ever received.”</p><p>Is there any reason these questions can’t be asked upfront in the application form?</p><h4>Read, edit, and talk about existing code</h4><p>Whether as an asynchronous take home or as a paired-up assignment, asking candidates to look at an existing code sample, find bugs, and fix them is an incredibly valuable yet somewhat rare exercise.</p><p>Reading other people’s code is about 80% of the work of a software engineer. Rewriting systems from scratch is almost never realistic. Building great software isn’t just about writing code, it’s about evolving code. How do you make breaking changes without breaking anything? LeetCode-style interviews do not test for these skills and less than 10% of the coding interviews I’ve done ask me to read or modify existing code.</p><p>Can a candidate find existing bugs? Can they explain what the code is doing articulately and efficiently? Can they identify opportunities to refactor and improve code organization? Can they communicate the shortcomings of an existing system without hurting anyone’s feelings? Do they write effective commit messages? Can they put together organized change requests?</p><h3>An Interview is an Employee’s First Experience with Your Company</h3><p>I think it’s important that the interview process be enjoyable and efficient for everyone involved. When they’re not, interviewers start think of them as a distraction from their work instead of an investment in the company. In turn, recruiters have a harder time getting interviews scheduled. It’s a downward cycle that ultimately results in bad hires.</p><p>An interview should give candidates a sense of what it’s like to work at the company too. It says a lot to a candidate when it’s obvious the interview process was thoughtfully considered and not just “the way it’s always been done.”</p><p>A great candidate experience is fast, responsive, and relaxed—as relaxed as an interview can be, anyway.</p><p>Personally, I also think the interview process should be designed for candidates to succeed, not fail. This seems counterintuitive since, almost universally, companies <em>do not hire</em> way more people than they <em>do hire</em>. But just because a candidate isn’t being offered a job doesn’t mean they need to feel like they failed.</p><p>Take a chance. Technology changes and with it the products we use change too. So too do the ways in which we work and collaborate. Interviewing a candidate can and could be reflective of those innovations.</p><p><em>If you enjoyed this post, please don’t hesitate to </em><a href="/service/mailto:avand@avandamiri.com"><em>reach out</em></a><em>. I’m a full-stack, front-end leaning, customer-obsessed, product-minded, detail-oriented software engineer with </em><a href="http://avandamiri.com/resume"><em>20 years of experience</em></a><em>. I’m currently looking for a full-time hybrid role in SF, so if you’re hiring, I’d love to talk—even if you do ask LeetCode-style questions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=faa11394abcf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Budget to a “Free House”]]></title>
            <link>https://medium.com/@avand/budget-to-a-free-house-7b53eff6ac89?source=rss-827ac8e4ae00------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b53eff6ac89</guid>
            <category><![CDATA[budgeting]]></category>
            <category><![CDATA[financial-independence]]></category>
            <category><![CDATA[real-estate-investments]]></category>
            <category><![CDATA[budget]]></category>
            <category><![CDATA[personal-finance]]></category>
            <dc:creator><![CDATA[Avand Amiri]]></dc:creator>
            <pubDate>Fri, 26 May 2023 17:24:03 GMT</pubDate>
            <atom:updated>2023-06-01T23:02:49.786Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="View of San Francisco over the Bay Bridge at sunset" src="https://cdn-images-1.medium.com/max/1024/1*kfPkjIhlNhq7KFL8aOR_-g.jpeg" /></figure><h4>The story of purchasing my first home and how budgeting made it possible.</h4><p>As I drove over the Bay Bridge, returning to San Francisco from the Sierra foothills, I stared admiringly at the shimmering windows of the homes on the East side of Twin Peaks.</p><p>“How could anyone ever afford to live in one of these homes?!” I wondered, while simultaneously imagining what the people living in these homes must be wondering themselves as they look out over the Bay.</p><p>Owning a home—let alone a single-family home with a view of one of the world’s most iconic cities—is a daunting endeavor and one to which almost every person aspires, despite it often seeming impossible.</p><p>This is the story of my first home: how I came to afford it, how I found it, financed it, and ultimately how I turned it into a cash-flow positive investment—what I like to call my “free house.”</p><p>This is also a story about the <strong>power of budgeting</strong>—how diligently tracking our income and expenses empowers us to make seemingly impossible dreams a reality. I’m so convinced of budgeting’s efficacy that, at the end of this post, I’ll share with you the budgeting tool I’m building (<a href="https://lopery.com/?utm_source=avands-story&amp;utm_medium=medium&amp;utm_campaign=announcement&amp;utm_content=&amp;utm_term=">Lopery</a>) to help others obtain their own “free houses.”</p><h3>“This is going to be impossible”</h3><p>While I was working at Airbnb in 2017, I knew I was making enough money to incrementally save up for <em>something</em>. A house seemed liked the worthiest of investments but housing in the Bay Area was untouchable — even with a software engineer’s salary.</p><p>I started doing analysis of the broader CA market and, rather than finding a primary residence, I searched for investment properties instead. I compared average nightly rates of vacation rentals to housing prices, and discovered Mariposa County, at the foothills of the Sierras and the gateway to Yosemite (pop. 17,000). Average annual Yosemite visitation is north of 3m, demand for lodging is high, and housing prices were approachable.</p><p>This wasn’t exactly the shimmery SF home dream I had fantasized about but it was a real possibility. The question then became…</p><h3>“Can I afford it?”</h3><p>Queue the spreadsheet. For years, I had been evolving a personal finance spreadsheet. Each year, I’d duplicate last year’s and make improvements. To answer the question, “how much could I afford?” I needed to know two things:</p><ul><li>How much do I make?</li><li>How much do I spend?</li></ul><p>Answering the first question was simple. But figuring out how much I spend was a bit more tricky.</p><p>I broke down my spending into two buckets: living &amp; lifestyle. Living expenses were fixed, recurring, essential things like my gym membership, car payment, rent, cell phone, and internet. I made rows for each of these and summed them.</p><p>Everything else was discretionary. I could make choices about the groceries I purchased, shows I went to, how many drinks I ordered at the bar. Each month, I exported the transactions from my banks and imported them into a spreadsheet. Eventually, I even built a Plaid app that did this automatically. I used one credit card for all these “lifestyle” charges so I didn’t have to categorize anything. Then, I looked at the totals for the last three months and averaged them. This number was what my lifestyle cost every month and since I wasn’t willing to change my lifestyle this was the number I needed to complete the equation:</p><blockquote>Savings = income - living expenses - lifestyle expenses</blockquote><p>For me at that time, it turned out to be $2,000/mo. Knowing this, I configured my direct deposit to automatically contribute that amount into a separate account each month and in five months I had saved $10,000.</p><p>I also started looking at homes in Mariposa and the types of loans for which I would qualify. It was critical to find a purchase price, where the monthly mortgage payment would end up being less than or equal to my monthly savings rate. Otherwise, I’d buy a home I couldn’t afford without <em>making more</em> or <em>spending less </em>money.</p><p>I found a property with two dwellings on it for $299,000. I applied for a FHA loan that required 3% down and purchased this property with the $10,000 I had saved. The amount I had been saving each month now went towards covering the monthly mortgage payment. Bingo!</p><p>I also ran through the “worst case scenario” case of losing my job and income and decided I could be content living in Mariposa and reducing my overhead if it came to that.</p><h3>“Free house?”</h3><p>I began working on turning the property into a vacation rental. The $2,000 I had been saving each month, now went to the bank to pay off the loan. So it didn’t <em>feel</em> like it was costing me anything—my lifestyle didn’t have to change. But I knew that if I could get Yosemite tourists to pay the mortgage for me, I’d get that $2,000 each month back to save up for something else.</p><p>Any bonus income I made, I shoveled into permits and improvements to get the dwellings ready. Mariposa County has 30-pages worth of requirements to legally list a vacation rental so I went to work ticking off each requirement one-by-one.</p><p>It took a little over two years, but finally I did it! I created the listing and started hosting my first guests.</p><p>This income started to offset my monthly expenses so I was able to start saving again. This property has two separate dwellings on it, which created a lot of possibilities. I could live there, while renting out one, which I did during most of COVID. Or I could rent out both. Now that I was saving again, I put every extra dollar towards getting the second dwelling permitted to rent.</p><p>After another year and half of diligent saving and permit rigmarole, the economics completely changed. With the 2nd house bringing in vacation rental income, I didn’t have to put <em>in</em> cash each year to cover the mortgage, cleaning, landscaping, and maintenance costs. Instead, I started <em>making</em> money. Every dollar earned (net) started working against the initial set up cost such that, in time, it will have cost me nothing to own this property.</p><h3>Budgeting at the cornerstone</h3><p>This entire story was powered by my budget. Without knowing what my lifestyle cost me, I couldn’t determine what I could afford. Knowing what I could afford, forced me to focus my search and ultimately find the property I own today.</p><p>In fact, I’m so enamored with budgeting that I’m now building a budgeting app that actualizes the exact same principles into a nearly effortless experience. People know they should be budgeting but they don’t because it’s hard. But it doesn’t have to be.</p><p>Lopery is the combined result of 20 years of budget mastery between myself and my co-founder, Morgan Engel. Lopery boils down all your income and recurring expenses to a single Safe to Spend number—all in about 5 minutes of set up. You can track that number on a weekly basis to stay on track. If you consistently spend less than your weekly Safe to Spend, you can set up new automatic recurring savings, just like I did by adjusting my direct deposit. If you’re consistently spending more than your weekly Safe to Spend, Lopery will show you how that’s impacting your savings over time.</p><p>Lopery isn’t just for buying a home. Lopery is for anyone. If you already own a home, use Lopery to determine how much additional money you can move into investments now (<em>vs.</em> months from now). “All the benefits in life come from compound interest — relationship, money, habits — anything of importance” — <a href="https://twitter.com/NavalBot/status/1371551927822118915">Naval Ravikant</a>. Get that compound interest working for you now!</p><p>Lopery also isn’t just for high-earning people either. Use Lopery to build your safety net. If you lose your job, make sure you’ve got 3 months of income set aside to cover your living expenses. Adjust your Safe to Spend to get there and Lopery will help you stay on track.</p><p>Other apps either require you to do a bunch of manual work each month for them to be helpful. Lopery integrates with your banks so it’s always based on real, up-to-date data. Other apps focus on your net worth, but Lopery helps you make day-to-day decisions to grow it. Other apps are free, because they sell your data to offer you financial products you don’t need. Lopery is a paid subscription service to ensure your data belongs to you.</p><p>Morgan and I decided to build Lopery because we’ve tried everything else and were woefully unsatisfied.</p><p>I wrote this blog post to hopefully inspire you to try it and see how simple and powerful budgeting can be. Turn your impossible dreams into realistic possibilities.</p><p><a href="https://lopery.com/?utm_source=avands-story&amp;utm_medium=medium&amp;utm_campaign=announcement&amp;utm_content=&amp;utm_term=">Sign up</a> today for free access to Lopery through the end of 2023.</p><figure><a href="https://lopery.com/?utm_source=avands-story&amp;utm_medium=medium&amp;utm_campaign=announcement&amp;utm_content=&amp;utm_term="><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6KGnw07OMRc8FqVl8RVRkQ.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b53eff6ac89" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hacking Human Connection: The Story of Awedience]]></title>
            <link>https://medium.com/airbnb-engineering/hacking-human-connection-the-story-of-awedience-ebf66ee6af0e?source=rss-827ac8e4ae00------2</link>
            <guid isPermaLink="false">https://medium.com/p/ebf66ee6af0e</guid>
            <category><![CDATA[connection]]></category>
            <category><![CDATA[meetings]]></category>
            <category><![CDATA[pandemic]]></category>
            <category><![CDATA[virtual-events]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Avand Amiri]]></dc:creator>
            <pubDate>Tue, 05 Apr 2022 17:29:35 GMT</pubDate>
            <atom:updated>2022-04-11T22:22:11.531Z</atom:updated>
            <content:encoded><![CDATA[<h4>How a home-grown product helps Airbnb employees feel more connected during solitary times</h4><figure><img alt="A screenshot of Awedience during an all-company meeting. Brian Chesky, CEO, is in the center and is surrounded by thousands of employees represented by tiny squares. Each square is either a picture of the employee, a color, or a letter that people have arranged to spell words or draw shapes. Emojis are captured emerging from some of the seats." src="https://cdn-images-1.medium.com/max/1024/1*u9pnag1uWfgwnT8tv42I1g.jpeg" /></figure><h3>Introduction</h3><p>This is the story of how Airbnb employees stayed connected during a time they had never felt more apart. In this post, you’ll learn how an idea turned into an internal product that is now a core part of how Airbnb operates.</p><p>When you walk through the doors of an Airbnb office, you feel an energy that’s both inspiring and intimidating. After more than five years with the company, I explain this duality as Airbnb being both incredibly entrepreneurial and aspirational.</p><p>Airbnb company meetings are no different. Brian Chesky and his team keep our all-hands meetings exciting. I know what you’re thinking: “exciting meetings?!” But in all seriousness our all-hands are not just informative, they’re spectacular. Whether it’s drinking a smoothie of dehydrated bugs in solidarity with Engineering or eating spicy chicken wings in a Hot Ones-style Q&amp;A, our meetings are informative, energizing, and engaging. In somber moments, they’re human and heartfelt.</p><p>The pandemic changed that. Feeling connected to the presenter, feeling connected to our peers, or feeling the presenter’s connection to the audience all vanished. Instead, we each separately watched the presenter streaming through a 16:9 rectangle on our laptops. Other people were watching concurrently (one could assume based on the invite) but it couldn’t be <em>felt</em>. Inspired, I set out to solve this, wondering,“<a href="https://en.wikipedia.org/wiki/The_Six_Million_Dollar_Man">we have the technology</a>, why can’t we see and interact with everyone watching live?”</p><h3>Inspiration</h3><p>It’s impossible to know under which circumstances inspiration will find us, and in hindsight it seems perfectly planned.</p><p>Airbnb is a community based on connection and belonging, which is the reason so many of us came to work here. However, in March of 2020, as the spread of COVID-19 forced us to shelter in place, we struggled to find ways to preserve those traits within our company culture. What it meant to feel connected to the world and to each other was being redefined by emojis over video. Video chat helps us stay in communication, but it’s <a href="https://www.youtube.com/watch?v=DYu_bGbZiiQ">comically clunky</a>, dry, and lifeless. If these technologies feel contrived it’s because they are. We all know what an authentic human connection actually feels like, and it’s not that.</p><p>For almost two years before the pandemic hit, I volunteered to help produce Airbnb’s quarterly engineering all-hands. Unbeknownst to me, I was actually studying the question, “how does one make people feel more connected?” Whether it meant hosting an orca-themed relay race across our Portland, Seattle, and San Francisco offices, or projecting live chat in auditoriums to make the audience more engaged, I had been finding ways to foster human connection.</p><figure><img alt="Engineers dressed up in costumes working in pairs at laptops. Ping pong balls are being throw at them from the crowd, while they try to focus on solving engineering problems on the computers." src="https://cdn-images-1.medium.com/max/1024/1*SIXAHtcfgeFICxZ6B11UwA.gif" /><figcaption>Pairs of engineers complete programming challenges, while being pelted with ping pong balls by the audience. This was just one of the many ridiculous segments of Nerds@, the engineering all-hands meeting I voluntarily produced for two years.</figcaption></figure><p>Isolated at home with all these insights into event production, it’s not surprising that, while I watched our CEO, Brian Chesky, address thousands of employees via live stream, my attention drifted to the little number in the top right corner that showed how many other people were watching. These were my colleagues, my friends — some of the most talented people in the world. In our isolation, the only affordance that existed to capture our experience of watching this live stream together was an aggregate count. Instagram and YouTube allowed people to express themselves with emojis and comments during live broadcasts. Internally, we could not.</p><figure><img alt="Photos of various employees at-home workstations. Some photos are laptops on a desk or coffee table. Others are projected onto a TV in a living room. Two of the photos feature pets in the background." src="https://cdn-images-1.medium.com/max/1024/1*t-XAOqp7jvfTDsFhQpSejQ.png" /><figcaption>A look at life before Awedience: everyone watching the same stream at home alone, with the exception of some furry pals.</figcaption></figure><p>An idea started to emerge: supplement the live stream with small, thumbnail-sized videos of all the viewers’ webcams and capture audience sentiment with emojis. It seemed simple enough.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rat4XcYbupe-pho3KM1wqw.jpeg" /><figcaption>The original sketch. Simple, right?</figcaption></figure><p>Yet even this concept proved untenable. I had never built a fully real-time web application and would likely need months to figure out the webcam piece. I didn’t have months. I was only willing to dedicate a few days to see if this idea had merit.</p><p><a href="https://entrepreneurshandbook.co/how-airbnb-founders-sold-cereal-to-keep-their-dream-alive-d44223a9bdab">Cereal Entrepreneurs</a> will attest that ideas are cheap — nobody copies ideas. Only <em>proven</em> ideas get copied, and this idea was definitely not proven. So I started to collaborate with some of my peers and <a href="https://www.linkedin.com/in/stepan-parunashvili-65698932">Stepan Parunashvili</a>, helped us get the ball rolling. “Punt on video for now,” he said, “start with profile pictures from our company directory. Firebase can handle all the real-time stuff, and we already have an internal authentication service. Boom!”</p><p>Stepan continued to offer his support with the initial infrastructure. We needed a name and thought about it for all of a minute. This product was all about the “audience” and “aww” is one sound an audience makes when they’re experiencing something together. Inspiring “awe” was also part of the motivation of this work so we decided on “Awedience.”</p><p>Within a few hours, Stepan had the scaffolding complete. People could sign in and <a href="https://en.wikipedia.org/wiki/%22Hello,_World!%22_program">“hello world”</a> with other users. Our authentication service played gatekeeper, guaranteeing that the application would have access to an employee’s LDAP username after they signed in. That username enabled me to load a profile picture from our company directory. <a href="https://firebase.google.com/docs/database/">Firebase</a> served as the realtime database, and React sat right on top of it, bound (almost directly) to Firebase events. I could finally focus on my specialty, UI and UX. With an iframe embedded front and center, the UI naturally formed a U-shaped auditorium with virtual seats. When you clicked a seat, your picture would appear, and as you reacted, emojis would float out of your seat for everyone to see. You could also write short messages and they would pop out of your seat too, simulating shouts to the crowd.</p><p>We had built something. Now, would anyone care?</p><h3>Growth</h3><p>Attention is an incredibly valuable resource and there are lots of ways to get it. Attention is commonly bought. Attention can be diverted from other channels. It can even be stolen.</p><p>But attention can also be <em>earned</em>. When people <em>love</em> a product, it not only has true staying power but will grow organically. Therefore, one way to see if people love something new is to say nothing and observe.</p><p>I invited close colleagues to try Awedience for an all-hands to see what would happen. Intuitively, they took a seat, started reacting, and used it throughout the meeting. The feedback was <a href="https://sive.rs/hellyeah">overwhelmingly positive</a>. Awedience didn’t do much but what it did do, it did well enough.</p><figure><img alt="A screenshot of Airbnb’s Slack while Audience was being used for the first time. Some messages say “we’re sitting together,” “love this feature it’s so cute,” “this is the coolest,” and “I noticed you sat next to me.”" src="https://cdn-images-1.medium.com/max/1024/1*DPnN31xW0LgGXbbysUO_fw.png" /><figcaption>A glimpse into our company Slack: first reactions to Awedience at Airbnb.</figcaption></figure><p>At the time, Brian hosted all-company Q&amp;As weekly. I created a calendar event alongside the all-company one with an alternative URL and only invited people that had previously used Awedience. Within a few months, Awedience was so popular that it was offered as a secondary option in the official calendar invites.</p><p>With the increased popularity, it was hard to support Awedience on nights and weekends. I asked my team for time to redirect my focus to Awedience for a few months, and they were supportive. The only request was that I figure out the product’s future by the end of that time and not leave things open-ended. Would it become a part of <a href="https://www.airbnb.com/s/experiences/online">Online Experiences</a>? Would it become a part of another team’s roadmap? We even speculated that it could be a completely new line of business.</p><p>While it was tempting to keep adding functionality, resourcefulness was now the name of the game. Awedience was crashing during peak moments so performance was and still is the most important feature. Before we implemented throttling, we were binding reactions directly to our app state, which triggered a deluge of re-renders:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9cc2af478f93a52dbd1e74dfafeb2e11/href">https://medium.com/media/9cc2af478f93a52dbd1e74dfafeb2e11/href</a></iframe><p>A crude <em>batchedThrottle</em> function reduced renders when users mashed an emoji button:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e7477b5316cc110ea5df6409c5d86694/href">https://medium.com/media/e7477b5316cc110ea5df6409c5d86694/href</a></iframe><p>Later, additional performance gains were found by detaching the React UI from Firebase real-time callbacks. Eventually, reactions would be managed natively without React at all:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/de71ca2d02402ba3df6f5db2228c4141/href">https://medium.com/media/de71ca2d02402ba3df6f5db2228c4141/href</a></iframe><p>There were more affordances I wanted to explore. At sporting events, attendees often hold up signs, flags, or even paint things on their bodies to spell out a message. Replicating this in Awedience was a huge hit. Rather than a profile picture, attendees could now pick a color, letter, or a portion of a graphic to display from their seat. People show up early and coordinate amongst themselves to spell out messages to represent their team, city, or the company. The result is magical. Awedience didn’t make it easy to tell your neighbor to change their seat picture. People were going out of their way to coordinate with one another. Connection between colleagues was happening organically and it was thrilling to see.</p><figure><img alt="A screenshot of Awedience during an all-company meeting. Brian Chesky, CEO, is in the center and is surrounded by thousands of employees represented by tiny squares. The squares spell out words like “insurance,” “human,” or “trust.” There are also a few Airbnb logos being drawn out in 5x5 tiles." src="https://cdn-images-1.medium.com/max/1024/1*DsAVOD_cZgUwAP39X6qQZQ.jpeg" /><figcaption>An earlier version of Awedience where people were spelling words, representing their teams, cities, and the company. Or the CEO’s face.</figcaption></figure><p>Making sure there were enough seats for everyone was also a challenge. Too few seats and some people can’t participate; too many and the auditorium feels empty. To handle this, Awedience does something its skeuomorphic counterpart can’t do: adding seats as needed. This feature felt vital for a product built at a company so focused on belonging. Later, we would improve on this feature by increasing seating density such that almost 1,000 people are visible “above the fold.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kwLwo5MNpcT8HLk8xq3L7g.gif" /><figcaption>Adding rows of seats to the bottom worked for a long time but limited users from seeing everyone at once. It took the addition of virtual aisles to afford seats being added horizontally without compromising user-generated seat art.</figcaption></figure><p>Self-service features were also prioritized. Brian’s staff immediately wanted to know what content was spurring engagement — a question they hadn’t been able to answer since going remote. Cumulative data from each event was piped into a graphing library for quick and dirty analytics. Similarly, our video production team wanted to be able to create and edit auditoriums without relying on me so that self-service tooling came as well.</p><figure><img alt="A stacked line graph of emojis over time. One line, applause, for example goes up to over 300 reactions for a moment. Later, hearts, spike to nearly 150. Each emoji has its own usage graphed on the chart." src="https://cdn-images-1.medium.com/max/1024/1*ceUehJwN6__G7Q_OIQoZrA.png" /><figcaption>Awedience helps presenters understand exactly which parts of their presentation landed for their audience.</figcaption></figure><p>Later, during a hackathon, we even created applause sound effects that naturally scale up from the sound of a few hands clapping to an uproar based on audience engagement.</p><figure><a href="https://video.airbnb.com/media/t/1_o3egj5jk"><img alt="A video demo of Awedio, in which you can see Brian Chesky being interviewed on CBS while members of the audience applause around him. In addition to seeing the applause emojis rise from the audience, you can also hear the applause generated by the software." src="https://cdn-images-1.medium.com/max/1024/1*N_NlPojNdwUIK83bev6Rug.jpeg" /></a><figcaption>Awedio allows you to hear the audience’s applause reactions.</figcaption></figure><h3>Moments</h3><p>Awedience made Airbnb feel like Airbnb again. There’s now a place where you can see everyone and feel connected to them. It’s become home to celebratory moments and a place where we can sit alongside one another during somber ones.</p><p>When Airbnb announced a cut back to our workforce, there was an all-hands scheduled to honor and appreciate the employees who were leaving. However, with VPN access cut to roughly 2,000 soon-to-be alumni, Awedience was suddenly only accessible to the spared employees. Resident security guru, <a href="https://www.linkedin.com/in/keeleysam">Sam Keeley</a>, and I committed to making Awedience accessible outside of VPN and almost overnight switched authentication to Google IAP. When the founders addressed the company, they invited a standing ovation for our departing peers and Awedience obliged. It’s hard to imagine what kind of impersonal and solitary send-off we would have had without Awedience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*znVI-1UvXbpPEn9WClZzJw.gif" /><figcaption>Hundreds of employees joined our founders in a virtual standing ovation for the members of our team that were let go as a result of the pandemic cut backs.</figcaption></figure><p>In May, in the wake of social action around George Floyd’s murder, the company met to address the Black Lives Matter movement. At the end of this meeting, Brian invited the company to take an 8 minute and 46 second moment of silence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-7x_Yi1B3DiKxQTq6yv_aA.gif" /><figcaption>Employees join in a somber yet moving virtual moment of silence for George Floyd.</figcaption></figure><h3>Conclusion</h3><p>At Airbnb, Awedience is here to stay and now receives ongoing support and maintenance. In collaboration with our Employee Experience team, we found a home where it would make sense long term. In fact, if this is the kind of work you find interesting, you may even consider joining our team to help us build internal tools to foster connection — <a href="https://careers.airbnb.com/positions/">we’re hiring</a>!</p><p>I feel fortunate to work for a company that creates space to bring these types of projects to life. Airbnb is an inspiring place — the combination and culmination of a rigorous entrepreneurial spirit and an ongoing commitment to outdo the status quo. That’s the type of environment you need for ideas like Awedience to flourish.</p><p>Awedience is more than just a triumph of passion and creativity. The spark of the idea was just that: a spark. In the words of <a href="https://twitter.com/richardbranson/status/264067714266587136">Richard Branson</a>, “opportunities are like the buses — there’s always one coming.” Without the help and support of many amazingly talented colleagues, there would literally be nothing to write about.</p><p>What makes Awedience awesome is the people. Big ideas are rarely the consequence of one person’s ideas or effort. It takes a lot of people to do incredible things.</p><h3>Acknowledgements</h3><p>To Stepan Parunashvili for fueling the fire and bootstrapping the infrastructure that got Awedience going. Without you, it would not have been possible. Thank you.</p><p>To Sam Keeley for enabling and evolving Awedience access for the entire company.</p><p>To Joe Gebbia for creating some air space for Awedience to grow and evolve.</p><p>To Byoung Bae, Allison Frelinger, Darrick Brown, and Judd Antin of my former team for taking a gamble on Awedience with me.</p><p>To Liz Kleinman and Beth Axelrod for creating a role for me to continue this work.</p><p>To Shawdi Ilbagian Hahn, Dave O’Neill, Kylie McQuain, Kelly Bechtel, Kate Walsh, Benny Etienne, Carrie Kissell, Alyce Thompson, John Lawrence, and Samantha Eaton for your collaboration and partnership in keeping the company engaged and connected.</p><p>To Cory Boldt, Steven McNellie, Garrett McGrath, Alex Lacayo, John Espey, and Scott Ethersmith for your help and creativity on the technical productions.</p><p>To Jenna Cushner, Ortal Yahdav, Lucille Hua, Christian Williams, Shawn Terasaki, Brian Wallerstein, Ben Muschol, Mike Fowler, Jason Goodman, Caty Kobe, Joe Lencioni, Nicolas Haunold, Christian Baker, Alan Sun, and Jacqui Watts for your early contributions and feedback.</p><p>To Kevin Swint, Danielle Zloto, Christine Berry, Federica Petruccio, and Consuelo Hernandez for going above and beyond to try Awedience with Online Experiences and the powerful insights that were created as a result.</p><p>To Nicholas Roth, Izzy Rattner, Jonathan Lieberman, Stephen Gikow, Steve Flanders, Lonya Breitel, Alan Shum, Brian Savage, Veronica Mariano, Allie Hastings, Alica Del Valle, Rajiv Patel, and Emily Bullis for your legal support in protecting Awedience’s intellectual property and making external partnerships possible.</p><p>To Sarah Baker for always rallying people together to create seat artwork.</p><p>To Gaurav Mathur, Hope Eckert, Sean Abraham, Jessie Li, Vaithiyanathan Sundaram, Andy Yasutake, Virginia Vickery, Jonathan Rahmani, Andrew Pariser, Sunakshi Kapoor, Diane Ko, Biki Berry, Francisco Diaz, Erik Ritter, Tony Gamboa, Mohsen Azimi, Bruce Paul, Omari Dixon, Sonia Anderson, CJ Cipriano, Chihwei Yeh, Arie Van Antwerp, Victor De Souza, Sam Shadwell, Deanna Bjorkquist, Jenna Cushner, Richard Kirk, Jake Silver, Alex Rosenblatt, David He, LA Logan, Ryan Booth, Pistachio Matt, Melanie Cebula, Brian Morearty, and Victor Caruso for your participation and support!</p><p>To Stephanie Wei, Micah Roumasset, Ryland Harris, Waylon Janowiak, and Ben Arnon for your willingness to try Awedience outside of Airbnb.</p><p>To Jerry Chabolla, Nicholas Schell, Ryan Jespersen, Sergio Garcia Murillo, Wes Dagget, and the entire team at Millicast for enabling real-time streaming.</p><p>To Brett Bukowski, Cara Moyer, Nicki Williams, Dylan Hurd, and Lauren Mackevich for encouragement and support in writing this blog post.</p><p>And lastly to Danee Chavez for powering the light bulb. 💡</p><p><strong>Interested in working at Airbnb? Check out these open roles:</strong></p><p><a href="https://careers.airbnb.com/positions/3714489/">Senior Software Engineer, Airfam Products</a></p><p><a href="https://careers.airbnb.com/positions/3955056/">Staff Technical Program Manager, Insurance Platform</a></p><p><a href="https://careers.airbnb.com/positions/3988445/">Staff Automation Engineer, BizTech Global Ops</a></p><p><a href="https://careers.airbnb.com/positions/4003012/">Operations Engineer</a></p><p><em>All product names, logos, and brands are property of their respective owners. All company, product and service names used in this website are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ebf66ee6af0e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/airbnb-engineering/hacking-human-connection-the-story-of-awedience-ebf66ee6af0e">Hacking Human Connection: The Story of Awedience</a> was originally published in <a href="https://medium.com/airbnb-engineering">The Airbnb Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The stories you tell define you]]></title>
            <link>https://medium.com/@avand/the-stories-you-tell-define-you-785dc1ff5702?source=rss-827ac8e4ae00------2</link>
            <guid isPermaLink="false">https://medium.com/p/785dc1ff5702</guid>
            <category><![CDATA[musings]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[short]]></category>
            <category><![CDATA[storytelling]]></category>
            <dc:creator><![CDATA[Avand Amiri]]></dc:creator>
            <pubDate>Tue, 08 May 2018 05:02:37 GMT</pubDate>
            <atom:updated>2018-05-08T05:02:37.990Z</atom:updated>
            <content:encoded><![CDATA[<p>As you go through your day, you have so many various possibilities available to you. Think about all the things you could do with your next moment.</p><p>These imaginations are not real — they’re just ideas. But they can become stories when you choose an outcome and achieve it.</p><p>It takes integrity, commitment, and sustained effort to turn an idea into an awesome story.</p><p>So go on: tell better stories.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=785dc1ff5702" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Brief: Cooler Calculator]]></title>
            <link>https://medium.com/hover-state/design-brief-cooler-calculator-e22fc497cc47?source=rss-827ac8e4ae00------2</link>
            <guid isPermaLink="false">https://medium.com/p/e22fc497cc47</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Avand Amiri]]></dc:creator>
            <pubDate>Mon, 26 Sep 2016 19:55:01 GMT</pubDate>
            <atom:updated>2016-09-26T23:02:39.207Z</atom:updated>
            <content:encoded><![CDATA[<h4>What’s cooler than bein’ cool? Dry ice!</h4><p><em>I built a Cooler Calculator for a small dry ice business in the Bay Area. This is the story of why and how it came to be. I’ll start with the backstory, then unpack my design process, and finally share the end result.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/824/1*zcQTB2RQGHpzlKurAYeqtg.png" /></figure><h4>Backstory</h4><p>Every year, me and 70,000 of my closest friends get together and head out to the remote deserts of Nevada for a week or so. It’s like a camping trip but bigger, and with more LEDs. I’ve been a couple times and decided to go again this year.</p><p>Well, if you’re going to the desert for a week, you should come prepared. Water comes to mind. Food is also critical. Personally, I like to cook, especially in unexpected places. No peanut butter jelly for me, thanks. On the menu: stir fry with steak and vegetables, pasta with smoked pheasant, and bacon—lots of bacon. And all of that needs to stay frosty. Ice is OK but dry ice is better. It doesn’t melt, it sublimates, which means your cooler doesn’t turn into a swimming pool. It’s also <em>very</em> cold so your victuals can stay fresh longer.</p><p>The first time I needed dry ice, I did some Googling and a little site came up: Ben’s Dry Ice. It wasn’t much to look at—just a form basically. Fill it out and get dry ice. Simple enough. But this year, when I went back, holy upgrade! Ben had been busy. Now, his site was powered by Shopify and it looked great. So I went about my shopping.</p><p>One of the first questions you have when buying dry ice is “how much will I need?” In the past, I had answered that question with an email, “hey, Ben, I’ve got a 50 quart cooler and I’m trying to keep food cold for about a week, how much dry ice do I need?” Ben’s always been helpful but as his business grew he realized he couldn’t respond to every email so he figured out a better solution. He built a spreadsheet, locked some cells, and boom he had a very basic Dry Ice Cooler Calculator.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NXXS42qrqwdWuDsBzRL1MQ.png" /><figcaption>The original spreadsheet-based version of the Dry Ice Cooler Calculator</figcaption></figure><p>Well, this spreadsheet calculator had some problems:</p><ol><li><strong>Only one person could use it at a time.</strong> Google Sheets actually shows you who else is editing the document at the same time. So you kind of play this weird waiting game of chicken. Not good.</li><li><strong>It required a lot of instructions.</strong> Just look at the screenshot above. Where do you type? Where is the output? It’s not very clear. There are instructions outside of the spreadsheet and even more within.</li><li><strong>It assumed all your coolers were the same size.</strong> Not a deal-breaker but definitely not ideal.</li><li><strong>It undermined the professionalism of the site.</strong> The rest of the site looked great! But this page just felt cobbled together.</li></ol><p>I started thinking: I bet if I built Ben a legit calculator that solved these problems that a) his customers would really appreciate it and b) I’d get free dry ice. 😉</p><p>So I got to work.</p><h4>The Pitch</h4><p>I’ve been doing this type of work long enough to know: don’t ask, show. I knew that taking a first crack at a mockup wouldn’t take long and would give Ben and I something real to talk about.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*rLZsds_ajGIoscDoCdz-mQ.png" /></figure><p>After spending a little time in Sketch, I had a mockup.</p><p>Here’s how it works:</p><ol><li>Pick your cooler type: “freezer” if you’re trying to keep things frozen or “fridge” if you want to keep things cold but not frozen solid. I chose icons that really reinforced that. No matter who you are, you want your steak frozen and beers cold.</li><li>Indicate your total cooler size. If you have two 50 quart coolers, just drag the slider to 100 quarts.</li><li>Choose the duration of your trip.</li><li>See the total number of pounds of dry ice necessary.</li></ol><p>It was simple. <em>Too</em> simple in fact. Because I hadn’t fully unpacked the problem yet, I ended up over simplifying things. When I’m just getting started with something, I actually like to over simplify because you end up challenging more assumptions and, if you’re successful, you’ll have to do less work in the long run.</p><blockquote>I actually like to over simplify because you end up challenging more assumptions and, if you’re successful, you’ll have to do less work in the long run.</blockquote><p>But this mockup had some problems:</p><ul><li>The visual design didn’t match Ben’s brand. That’s fine—I had absolutely no attachment to any of it. I just picked something that looked decent. In fact, I think I ended up with pink because the icons I liked were pink, when I found them and I didn’t want to bother to change them.</li><li>You have to do the math of adding up the total quart size of all your coolers. It’s not terrible but if we’re setting out to replace an incomplete tool let’s not replace it with another incomplete tool, right?</li></ul><h4>Round 2</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*gSTV3nPMYKgPi-voOY4oAg.png" /></figure><p>I set to work to fix these problems. I used the typeface used throughout his website and matched the colors as well as I could without sacrificing readability. I also made it possible to add a cooler.</p><p>Sadly, I didn’t consider that you may want one cooler dedicated to frozen items and another used as a fridge. Now, <em>all</em> the coolers were of the same type. I was disappointed that in this iteration the spreadsheet actually was more useful.</p><h4>Round 3</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/347/1*HoR2jxfcIoI9M00aA4MAbA.png" /></figure><p>Finally, we were getting somewhere. It had all the features we needed and I was starting to ask questions like “what happens when you click the +” or “should you be able to remove the first cooler?”</p><p>Whenever I start to ask myself interaction-related questions, I need to start coding. I like design tools like Sketch but I start to get antsy if I’ve been there for too long. There are questions that a design tool can’t answer like “how does it behave as I resize my browser?” Or, “will these controls even be possible to build?” I had some doubts as to whether sliders were the best choice and I also wanted more clarity about mobile vs. desktop experiences. There were also design queues I wanted to imitate from his website that I didn’t want to spend time replicating in Sketch.</p><blockquote>Whenever I start to ask myself interaction-related questions, I need to start coding.</blockquote><h4>Round 4</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DOcutj0q52oQWBX9ZlaM0A.png" /></figure><p>In high school, my sculpture teacher gave me a really good piece of advice: get material on every piece of the armature first. Only after the entire form has taken shape can you focus on polish. I set out to reproduce my static mockups quickly so I could focus next on getting the interactions right.</p><p>I wasn’t at all concerned about the calculation. I left that until the very end because I knew I would be changing things that would affect how the result was determined.</p><p>At this stage of a project, I want to address the technology stack. I try to avoid dependencies wherever possible and I felt like HTML, CSS, and JavaScript with jQuery would probably be all I needed here. But I wanted to be sure that the layout and the sliders wouldn’t give me a hard time.</p><p>I wanted to have a grid system that made laying out content into columns easy. I didn’t want a framework like Bootstrap determine what and when content should stack. My goal was to design for a medium size desktop browser (~600px wide) and use percentages for everything so it just did the right thing at smaller widths. I’d drop in a few optimizations for mobile with media queries later. I decided to go with <a href="http://daneden.github.io/Toast/">Toast</a> by <a href="https://daneden.me/">Daniel Eden</a>. The class names are a little verbose for my tastes, but it let me nest grids and didn’t really have any functionality I didn’t want. It was a grid, plain and simple.</p><blockquote>Allowing someone to specify a specific value sets an expectation of a very accurate result.</blockquote><p>I had to make sure the sliders would suite my needs. If they were unweildy I would have to redo the design with text-based inputs. I wasn’t too worried about browser support but the sliders were a critical part of the design. They also had to be easy to use on mobile. I wanted the sliders to work in increments—I never wanted you to be able to pick a 43 quart cooler size. That may be your actual cooler’s size but allowing someone to specify a specific value sets an expectation of a very accurate result. But this whole tool can only give you an estimate that’s reinforced by the fact that you can only buy dry ice in 10 lb blocks. The good news was that browser support for the <a href="http://caniuse.com/#feat=input-range">range input</a> is very good. I only ended up using <a href="http://danielstern.ca/range.css/#/">range.css</a> by <a href="http://danielstern.ca/#/">Daniel Stern</a> to customize their appearance.</p><p>Once I had a working prototype, I was able to quickly spot improvements:</p><ol><li>There was no need for an add cooler control on every cooler. It only needed to appear once, at the bottom.</li><li>The days slider was getting in the way. It disconnected the add cooler control and the coolers themselves. So I moved it to the top.</li></ol><h4>Polish</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*omdhciprKM6e-ig50IPN8A.png" /><figcaption>Final</figcaption></figure><p>Now came the fine-tuning. This was the point at which Ben and I actually went back and forth the most. We made a lot of improvements:</p><ul><li>Some leading instructions and labels. I was hoping to avoid having any instructions but after putting it in the hands of someone who had never seen it before we realized that “Freezer” and “Fridge” made no sense without some explanation.</li><li>The freezer and fridge toggles were taking up too much vertical space. Horizontally aligning the label and icon made room for additional coolers.</li><li>The sliders worked well but were too small for mobile users.</li><li>We moved the “add cooler” control closer to the coolers, which helps reinforce it’s role. Also font-size, casing, and stroke helped address low contrast and readability.</li></ul><h4>Instrumentation</h4><p>With any project I work on nowadays, I provide instrumentation to go along with it. I wanted to track basic actions like adding a cooler, changing a slider, or clicking buy.</p><p>I already use Google Analytics for most projects so I simply used their event tracking. I wrote a helper function that let me send events to Google by simply specifying the element, the event, and optionally a value:</p><ul><li>cooler added</li><li>cooler removed</li><li>cooler type changed (with type)</li><li>days changed (with number of days)</li><li>cooler qts changed (with qt size)</li><li>buy clicked</li></ul><p>So far I haven’t needed to dig into any usage data but it should help answer questions, when I do have them. Better to have the usage data (and not use it) than to not have it when you do end up having questions.</p><p>Instrumentation can be a bit like testing. It’s always hard to write your first test because you have to set pick tools and set everything up. But once the framework is in place writing your second test is much easier. Just having a simple event logging helper may take a few minutes to set up, but allows you really quickly add instrumentation as you continue to evolve the project.</p><h4>In Conclusion</h4><p>We launched this a few weeks before my trip. I was happy to haul a complimentary 300 lbs of dry ice out and share it with my campmates and friends. You can see the finished product here:</p><p><a href="http://bensdryice.com/pages/cooler-calculator-1"><strong>http://bensdryice.com/pages/cooler-calculator-1</strong></a></p><p>Ben says customers have loved it. I haven’t talked to any of them myself but I’d like to! If you have any feedback, <a href="/service/mailto:avand@avandamiri.com">I’d love to hear it</a>.</p><p>I set out to do this project mostly out of good will. It’s been great working with Ben and the cycle of good will has definitely started. Now, Ben has commissioned me to build another calculator for determining the amount of dry ice needed to build a fog machine. I’m excited to take on this next project just in time for Halloween. 🎃</p><h4>Stats</h4><ul><li>Libraries: <a href="http://daneden.github.io/Toast/">Toast</a>, <a href="http://danielstern.ca/range.css/#/">range.css</a>, <a href="https://github.com/avand/sprinkles/tree/v2.0.0">Sprinkles</a>, <a href="http://jquery.com/">jQuery</a></li><li>Lines of code: 124 HTML, 151 CSS, 123 JS</li><li>GitHub: <a href="https://github.com/avand/calcoolator">avand/calcoolator</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e22fc497cc47" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hover-state/design-brief-cooler-calculator-e22fc497cc47">Design Brief: Cooler Calculator</a> was originally published in <a href="https://medium.com/hover-state">Hover State</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Humble Pie]]></title>
            <link>https://medium.com/@avand/humble-pie-8a69a59547e8?source=rss-827ac8e4ae00------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a69a59547e8</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[humility]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Avand Amiri]]></dc:creator>
            <pubDate>Thu, 04 Aug 2016 20:41:38 GMT</pubDate>
            <atom:updated>2016-08-09T01:16:00.415Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*28-nOYteMj_nSBZX2kiJ8A.jpeg" /></figure><h4>Healthy reminders from a disappointing job interview.</h4><p>It’s not everyday that you get rejected.</p><p>I’ve applied to a lot of jobs in the last few months. With some of these applications, I’ve just been going through the motions and I haven’t expected anything to materialize. Other applications have been really concerted efforts with companies I truly admire. I’ve put many hours into writing cover letters and tweaking my resume only to hear nothing back. It’s annoying to sit in the dark but I get it — these companies garner lots of interest. Still nothing compares to an outright “no.”</p><p>One morning last week, I woke up and, still in bed, started flipping through Twitter. One of my followers had posted that they were looking for a full-stack engineer. I’m a full-stack engineer! Although the product was a bit of a mystery, I saw the makings of something great in the details and in the team. I reached out and just a few hours later I was on the phone.</p><p>I spoke to the founder and CEO for almost two hours. We talked about everything: how the product came to be, where it was at now, shared anecdotes from our careers, and mused about the fundamentals of great product design. I hung up the phone with a sense of hope. I was excited! This was clearly a team that wanted to take their time and get it right.</p><p>Without missing a beat, I was on another call with an engineer just a few hours later. Momentum in hiring is such a strong indicator and up until this point I had been cruising with full sails. It didn’t take long for us to start talking about their “stack,” the technologies they’re using on the project. I had to admit that I actually hadn’t used any of them. They were using a language I know well but in a totally different and unfamiliar way. As the sails started to luff, I knew that this journey was probably over.</p><p>I don’t think it has ever been harder to write software than it is right now. It used to be that you wrote some code, bought a server and, bam, you had a website up and running. Then it actually got easier! The clouds rolled in and soon you didn’t have to worry about servers at all. Services like Heroku would deploy your application at the push of a button and web frameworks like Ruby on Rails almost made web application development as simple as painting by numbers. The <a href="https://www.youtube.com/watch?v=Gzj723LkRJY">prototypical Rails demo</a> is building a blog in 15 minutes. 15 minutes!</p><blockquote>“The world went and got itself in a big damn hurry.” — Brooks Hatlen, The Shawshank Redemption</blockquote><p>Nowadays, building software is hard work. Companies like Google and Facebook continue to raise the bar in terms of what people expect applications to do. Apps need to be super fast, available everywhere, and interact with users intelligently. When people start typing into a text box, for example, they half expect it to finish their thought. And pretty soon conversational interfaces will be ubiquitous too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*mBacrnQz8d3MLPqqPW2k_w.png" /><figcaption>Distribution of screen resolutions of popular Android devices as reported by <a href="https://opensignal.com/reports/fragmentation.php">OpenSignal</a>.</figcaption></figure><p>Today, we expect software to meet us wherever we are. That means developers have to write code for at least three major web browsers and two mobile platforms, all the while considering almost every screen size you could imagine. To do it well, you have to commit to building your product two or three times over. Or you can attempt to share code between platforms, a problem that has yet to be solved well.</p><p>But developers have risen to these challenges. They’re forging ahead, breaking new ground, and solving these really complicated problems. They’re inventing new ways to share code between platforms, to create incredibly rich, interactive user interfaces, and giving the tools back to the community.</p><blockquote>“We choose to go to the moon in this decade and do the other things, not because they are easy, but because they are hard.” — John F. Kennedy</blockquote><p>When I was in high school, I spent my Saturdays at the Museum of Fine Arts learning how to make sculptures. My teacher, Ralph Rosenthal, had a profound impact on my life. He quite literally told me to shoot for the moon. “There’s a star <em>way</em> out there,” he said, “and the only way you’ll reach it is to set your sights even higher.”</p><p>Before that interview, I felt like I was cruising down the highway, satisfied — perhaps even a little impressed — with my cruising speed. Just a wide open road with no one around me for miles. And then out of nowhere, this shiny red motorcycle blew right past me. How could it be?!</p><p>In that moment, I was reminded that no matter how much work we’ve done, there’s still more to do. That the key to continued success is a relentless dedication to improvement and that humility is the antidote for your ego, which if left unchecked will happily rob you of opportunity.</p><p><em>Thanks for reading. As you probably gathered by now, I’m a full-stack software engineer and product designer and I’m searching for the </em><a href="https://medium.com/@avand/one-mans-search-for-the-perfect-job-90caad5d5b9f"><em>perfect company</em></a><em>. Please don’t hesitate to </em><a href="/service/mailto:avand@avandamiri.com"><em>reach out</em></a><em> to me with opportunities or just to say “hi.”</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a69a59547e8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One Man’s Search for the Perfect Job]]></title>
            <link>https://medium.com/@avand/one-mans-search-for-the-perfect-job-90caad5d5b9f?source=rss-827ac8e4ae00------2</link>
            <guid isPermaLink="false">https://medium.com/p/90caad5d5b9f</guid>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[hr]]></category>
            <dc:creator><![CDATA[Avand Amiri]]></dc:creator>
            <pubDate>Thu, 09 Jun 2016 19:17:56 GMT</pubDate>
            <atom:updated>2016-09-18T17:14:06.299Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i7rYUq5Fvzw3yffBj1lE9A.jpeg" /><figcaption>Image courtesy of <a href="https://www.etsy.com/shop/PrintLand?campaign_label=convo_notifications&amp;utm_source=transactional&amp;utm_campaign=convo_notifications_010170_10683759063_0_0&amp;utm_medium=email&amp;utm_content=&amp;email_sent=1465540841&amp;euid=TEoGdyKlFt-C0zbv0Ha2Xn0_3wuD&amp;eaid=44893927896&amp;x_eaid=a81b0e2bf0&amp;link_clicked=4">PrintLand</a></figcaption></figure><h4>Turning hard-learned lessons into a laser-focused job search.</h4><p>As we wrapped up Sunday night dinner at my apartment, my neighbor remembered, “hey, it’s Pi Day tomorrow, we should head down to Pi Bar for a few slices to celebrate.” <a href="http://www.pibarsf.com/">Pi Bar</a>, which by the way opens at 3:14pm, does great New York style pizza. They’ve also got an amazing beer selection. “I’d love to go, but…” I trailed off despondently, “I have to work.”</p><p>It was a busy time at work. For several weeks I had been sacrificing nights and weekends to do the things I couldn’t get to during the day. And yet, despite the fact that I was managing all my responsibilities, it still didn’t feel right to leave my co-workers during the “work day,” this arbitrary window of time dictated mostly by the schedules of my toddler-toting colleagues.</p><p>That next morning I quit. And although it had nothing to do with pizza, it had everything to do with feeling like I had lost control. I wasn’t working anymore, I was <em>being worked</em>. I had lost control of my schedule, my productivity, and my focus.</p><p>I decided to take a step back and re-evaluate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*RQRASdxYedPcnv-uYS2WZQ.jpeg" /><figcaption>Chris Sharma’s cover shot for <a href="http://www.bigupproductions.com/films/king-lines/">King Lines</a></figcaption></figure><p>The first thing I did was reclaim my health. I had already joined a climbing gym but I wasn’t going because I could really only go after work and, no surprise, that’s when everyone else goes. Climbing is all about being in control and you can’t be in control when you’re in somebody else’s way. So now, with my schedule wide open, I started going during the day, when it’s calm and quiet — like a library. I’m able to focus and the results have been fantastic. I’ve lost weight, built muscle, and found new mentors. Climbing flexes a specific mental muscle that grows by pushing your boundaries to achieve something beyond you.</p><p><strong><em>The perfect job should promote your productivity.</em></strong></p><p>My next job would have to allow me to continue my climbing practice. And that means <strong>remote work</strong>. When companies embrace remote work, “work hours” go out the window. You work when you’re productive, whenever that might be—like an adult. There’s no office and no office hours so the only expectations your colleagues have are only the ones <em>you’ve</em> set. Things are calm and considered—productive and provoking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P1SNEJsSDo6HFw0oTzvVwQ.jpeg" /><figcaption>“It’s a shortcut, you see, D-A-N-G-E-R, shortcut!” — Bing Bong in <a href="http://www.imdb.com/title/tt2096673/">Inside Out</a></figcaption></figure><p>I started thinking about why I had sacrificed so many nights and weekends. Why did I constantly feel like there wasn’t enough time to do my job? We all need downtime to recuperate and recharge. Even one of the climbers I admire urged, “when you’re here, go hard, but don’t come everyday — you need time off to recover.” I started to realize that I worked overtime because we were always running out of time. One of the consequences of working for an unprofitable startup is that as the clock ticks the lights get a little bit dimmer too. Money, and therefore time, is always running out. Doing things correctly takes too long so we overlook the consequences of taking shortcuts. Time is so much of the essence that startups sometimes prioritize weekly or even daily. Some call it “agile” but I just think it’s shortsighted.</p><blockquote>“Odds are far better than good that high performers are achieving what appears to be high levels of productivity by building technical debt by taking shortcuts whether intentionally or unintentionally.” — <a href="https://medium.com/@billjordan1/the-quiet-crisis-unfolding-in-software-development-cffbdafbf450#.ra70wfgdb">Bill Jordan</a></blockquote><p><strong><em>The perfect job should pay you fairly.</em></strong></p><p>Making money is a problem just like all the other problems a business has to solve. If it goes unsolved, the whole dynamic of the company and its employees is stressed. So the next company I work for will have to be <strong>profitable, ideally from the beginning. </strong>Some companies, especially startups, treat profitability as an inevitability. Like, “once we’ve scaled, the money will come.” Sorry, but that kind of thinking puts most businesses in the ground. Stop and <a href="https://signalvnoise.com/posts/3972-reconsider">RECONSIDER</a>. Though Uber, Facebook, and a handful of others buck this trend most companies follow this remarkably simple model: “you have customers, they pay you money for the product or service, and you get profits” (<a href="https://signalvnoise.com/posts/1366-a-radical-idea-charge-people-for-your-product">David Heinemeier Hansson</a>).</p><p>Remote work for a profitable company. That does sound pretty perfect. But, just this once, let’s be indulgent…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/494/1*yAtWALsKI0ZQpQ-Ph0qa3w.jpeg" /><figcaption><a href="http://theicecreambarsf.com/">Ice Cream Bar</a> in Cole Valley, San Francisco</figcaption></figure><p><em>Ice cream!</em> One day at my last job the whole team—six of us at the time—went out for ice cream. It was weeks overdue because of scheduling conflicts (cone-flicts?). After we all ordered, I was surprised that we all were expected to pay for ourselves. We were celebrating a birthday and never really went out for anything anyway. It threw me off and I guess my brain froze because I never ended up bringing it up. Finally, after letting this fester for months (that’s healthy, right?) I brought it up to my boss. He explained, “we have a finite balance and we have to watch all of it.” OK, touché, that’s actually a good reason. You can’t spend what you don’t have.</p><p><strong><em>The perfect job should take great care of you.</em></strong></p><p>But still—it’s just ice cream! I couldn’t get over the sour taste it left in my mouth. What has better ROI than ice cream?! I’d like to work for a company that will <strong>find ways to give back to the people that do the work</strong>. Ice cream aside, I just don’t understand how anything could come before the people that make it that it all possible. What is a company without its people?</p><p><strong><em>Go for it.</em></strong></p><p>It’s a tall order to find a company that respects your time, makes money, and takes care of its employees. I’m not sure why but it just is. I think a lot of employees just settle for less. In fact, companies settle for less too. That truth is that we always have the option to settle. Whatever it is we’re doing, we basically have two options: to go for it or to accept the status quo.</p><blockquote>“Two roads diverged in a yellow wood, and I—I took the one less traveled by, and that has made all the difference” (<a href="https://en.wikipedia.org/wiki/The_Road_Not_Taken">Robert Frost</a>)</blockquote><p>I don’t think we should settle. Let’s create more companies that promote productivity, make money, and take care of their employees. Jobs like this <em>do</em> exist and I intend to find one and give them everything I’ve got.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/255/1*Za09TrhGXY7bild0jtCeHw.gif" /><figcaption><a href="http://www.geocities.ws/delightfulantagonists/cheshirecat.html">The Cheshire Cat</a></figcaption></figure><p><em>My name is </em><a href="http://avandamiri.com/"><em>Avand</em></a><em>. I’m a product designer, full-stack software engineer, and teacher. If you enjoyed this post, please click the green heart and follow me.</em></p><p><em>I’m looking for a company into which I can pour my everything. But I’m also looking to strict the right balance. If that makes sense to you, </em><a href="/service/mailto:avand@avandamiri.com"><em>we should talk</em></a><em>.</em></p><p><em>Thank you </em><a href="https://medium.com/u/7e3ada30885b"><em>Wendy</em></a><em>, </em><a href="https://medium.com/u/fc0af1fe5f"><em>Steve</em></a><em>, </em><a href="https://medium.com/u/2ec52691dafa"><em>Jessica</em></a><em>, </em><a href="https://medium.com/u/f863321a98d8"><em>Brandon</em></a><em>, and Eric Berson for your help!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90caad5d5b9f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your Bookshelf, Where Books Go to Die]]></title>
            <link>https://medium.com/@avand/your-bookshelf-where-books-go-to-die-caa361163656?source=rss-827ac8e4ae00------2</link>
            <guid isPermaLink="false">https://medium.com/p/caa361163656</guid>
            <category><![CDATA[reading]]></category>
            <category><![CDATA[books]]></category>
            <dc:creator><![CDATA[Avand Amiri]]></dc:creator>
            <pubDate>Wed, 25 May 2016 23:31:12 GMT</pubDate>
            <atom:updated>2016-08-04T20:25:06.603Z</atom:updated>
            <content:encoded><![CDATA[<h4>The next time you read a book, give the gift of knowledge and pass it on to someone else.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xSgmk7exPzy7HPBS6udA-w.jpeg" /><figcaption>The bookshelf from <a href="http://www.imdb.com/title/tt0816692">Interstellar</a>, one of my all-time favorite films.</figcaption></figure><p>I admire bookshelves stocked with books. They’re so inspiring. I stand in awe of this literal wall of knowledge. “Imagine if I knew all the information stored in all these books,” I wonder. “Wouldn’t that be amazing?”</p><p>A wall of bookshelves conjures a fantasy of sitting by a roaring fire, while I sip hot tea and devour every page.</p><p>But beyond that fantasy, a stacked bookshelf really just makes wonder, “did someone <em>actually</em> read all these books?” I don’t know about you but I have not read most of the books on my bookshelf. I have a hard time reading books. I get distracted, I space out, and I often catch my eyes scanning words, while my brain is off in la-la-land.</p><p>Even if I did read more (and I am working on that), I still think bookshelves are a pretty sad place for books to end up.</p><blockquote>“Even if I only get one thing out of a book, it was worth reading.” — my friend, John Cruise</blockquote><p>I recently finished <a href="http://rosenfeldmedia.com/books/storymapping/"><em>The User’s Journey</em></a> by Donna Lichaw. It wasn’t game-changing but I definitely gained a few insights. I wouldn’t recommend the entire book to someone because I bet I could hit the highlights. And, for the most part, I think that kind of summary works out better for everyone.</p><p>Obviously summarizing a book’s key points saves the listener a ton of time. It’s just like, “you absolutely <em>have </em>to watch <em>Breaking Bad</em>.” Great! Awesome. I’ll do that. Just as soon as I find a spare <a href="http://tiii.me/">46 hours and 30 minutes</a>.</p><p>More importantly, summarizing a book’s main points forces <em>you</em> to deeply understand the book’s content. You’ll notice that it isn’t easy to provide a tight summary of new content. And that’s because you just don’t yet understand it well enough. Once you really <em>get something,</em> the ability to <em>teach it</em> comes for free. Like Einstein said, “if you can’t explain it simply, you don’t understand it well enough.” That’s when transfer is complete; the book’s job is done.</p><p>Now, don’t put the book back on your shelf!</p><blockquote>“What is this obsession people have with books? They put them in their houses — like they’re trophies. What do you need it for after you read it?” — <a href="http://www.seinfeldscripts.com/TheExGirlfriend.htm">Jerry Seinfeld</a></blockquote><p>As I read <em>The User’s Journey</em>, I found myself thinking of my friend Eric. I remembered a project we had worked on together, where the information from the book could have been helpful. So, when I finished the book, I handed it to him. And, when he’s done with it, I hope he passes it along too.</p><p>Pass your finished books on to someone else to read, because a book isn’t a badge of honor, knowledge is. And there’s no better gift than that.</p><p><em>My name is Avand. I live in San Francisco. And even though I’m not a voracious reader, I love to learn new things. Lately, I’ve been trying to write more. If you enjoyed this post, or didn’t, or just want to say “hi,” please don’t hesitate to </em><a href="/service/mailto:avand@avandamiri.com"><em>reach out</em></a><em>. I’d love to hear from you!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=caa361163656" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nobody Cares About Your Software Updates]]></title>
            <link>https://medium.com/hover-state/nobody-cares-about-your-software-updates-7867a798faee?source=rss-827ac8e4ae00------2</link>
            <guid isPermaLink="false">https://medium.com/p/7867a798faee</guid>
            <category><![CDATA[rant]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Avand Amiri]]></dc:creator>
            <pubDate>Mon, 16 May 2016 19:43:06 GMT</pubDate>
            <atom:updated>2016-08-04T20:25:33.119Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*tq1Bq-e79E2EQ4ecRRQ6ag.gif" /></figure><h4>A plea to developers to improve the experience of releasing new software updates.</h4><p>Look, I get it. You practice agile development, iterate weekly, run tests automatically, and deploy continuously. You pride yourself on shipping changes quickly and how could that be a bad thing, right? You ship new features whenever they’re ready. The bugs you find today are squashed tomorrow. You and your software team are an optimized, streamlined, value-creating machine.</p><p>But guess what? <em>Nobody cares.</em></p><p>You and your team are the only ones celebrating new releases. For your customers, new releases are just a nuisance and an interruption. Updates actually interfere with whatever it is that they’re trying to do. Minor bug fixes are a nag. And major versions, while beneficial in the long run, are initially disruptive.</p><p>Non-technical people don’t even understand why software would even <em>need</em> to be updated—just as you don’t think about how the asphalt you walk on daily needs to be maintained. Your customers are thinking, “I found this app to do <em>x</em>; it does <em>x</em>; so why would anything ever need to change?”</p><p>Here’s a quick sanity check. How frequently do your customers use your product? And how frequently do you release updates? If you’re shipping updates more frequently than someone uses your product, there’s a good chance that you’ve pissed them off. For example, I use Adobe Photoshop CC about once every 2–3 weeks and Adobe pushes updates 1–2 times per week. It’s pretty frustrating to boot up my machine after taking a few days off only to be punched in the face with a litany of updates.</p><p>But let’s be realistic. You <em>have</em> to fix bugs and you <em>have</em> to ship new features. And while I don’t claim to have all the answers, I think it’s worth being mindful of a few things…</p><p><strong>Release fewer updates.</strong> Seriously, just being mindful of the changes you’re shipping can make all the difference. If something isn’t working the way it’s intended to, of course, fix it. But avoid frivolous changes. Don’t change colors, icons, or design patterns unless you <em>absolutely have to</em>. Those areas can always be improved. So unless your customer thinks like you do just leave them be. That ugly green icon in the lower left that you and your team have come to despise is what your customers have become accustomed to and there’s value in that. In other words, don’t fix what ain’t broke.</p><p><strong>Do updates automatically.</strong> On the web, this happens by default. Even the iOS App Store now automatically updates your apps to the latest and greatest versions. That could still be jarring if the whole product gets a face lift but for all those small bug fixes and incremental improvements it’s great! Remember, nobody cares that you were up all night finding and squashing a bug (aka doing your job). Take pride in being the unsung hero.</p><p><strong>Never interrupt your customers.</strong> Figure out a way to get your latest and greatest build into their hands without ever stopping their workflow. Where possible, provide both versions simultaneously and allow customers to opt-in or out of whichever version they like. Of course supporting two versions concurrently is expensive so you’ll have to weigh the cost and benefit.</p><p><strong>Create a smooth upgrade path.</strong> It’s hard enough to build software that accounts for all the edges cases that exist just in the “happy path.” But you should consider all the in-between states too. Hopefully this level of obsession with every aspect of your customer’s experience inspires you to downsize your ambitions. Fight within your weight class—minimize your overall product footprint to reduce the number of special cases.</p><p><strong>Sell the value to your customers.</strong> Communicate in advance of big releases and outline major improvements. Get out of your own head and focus on how it makes <em>their</em> life better, not yours. It’s very hard to turn a feature-story into a succinct message that your customers appreciate. I actually find it very helpful to <em>start</em> here. Forcing yourself to communicate the value of a feature can sometimes make you realize there actually isn’t any. It helps to figure that out before doing any work. Find a voice that you, your team, and your customers enjoy — keep it light, succinct, and heartfelt. Slack does an amazing job and their release notes are always an inspiration for me.</p><p>Internalize the fact that software updates are a nuisance for your customers. Minimize the downside by releasing mindfully, considering all the implications of a release, communicating well, and never interrupting your customer’s workflow.</p><p><em>For me building software is just a means to an end. So my perspective is always of that of the end-user, regardless of how agonizing it may be to achieve from a process, engineering, or design perspective. So take this article with a few grains of salt. At the end of the day, we have to move forward and it may simply not be worth the effort to accommodate everyone all the time. But I think it’s worth trying. If you have any criticism, </em><a href="/service/mailto:avand@avandamiri.com"><em>email me</em></a><em>. I’m all ears.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7867a798faee" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hover-state/nobody-cares-about-your-software-updates-7867a798faee">Nobody Cares About Your Software Updates</a> was originally published in <a href="https://medium.com/hover-state">Hover State</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thirty]]></title>
            <link>https://medium.com/@avand/thirty-4a007b1e9332?source=rss-827ac8e4ae00------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a007b1e9332</guid>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[personal-development]]></category>
            <dc:creator><![CDATA[Avand Amiri]]></dc:creator>
            <pubDate>Tue, 10 May 2016 09:35:32 GMT</pubDate>
            <atom:updated>2016-06-09T17:49:13.764Z</atom:updated>
            <content:encoded><![CDATA[<h4>When I turned 30, I asked myself “what are the most important life principles?” Here’s what I came up with.</h4><p>Ever since I was 15, I wanted to be 30. Nobody listens to you when you’re a kid. You have no means and no experience so you’re doing everything for the first time. And unless you’re incredibly gifted that also means that nothing you’re doing is very good. As a kid, you’re just at the mercy of some guardians and, as you’ll later find out, they aren’t always right.</p><p>My life has been far from ordinary. By the time I was eight I had lived in Boston, Salt Lake City, and Chicago. I was kicked out of elementary school and high school. Even after getting my GED I dropped out of college. With the help of some wonderful mentors, I taught myself how to build and design software and now I teach people to do the same — go figure!</p><p>Instead of college, I went to work. It was terrible work at first but I learned, got better, and weaseled my way into better jobs as quickly I could. Eventually, I cut out on my own. I tried to build a company and learned a lot about what <em>not</em> to do. Now, I’m living in San Francisco putting to good use over a decade of web development and three decades of life experience.</p><p>So, what have I learned?</p><p><strong>First, take care of yourself.</strong> You <em>have</em> to take responsibility for <em>everything</em> in your life. How you feel is entirely up to you and happiness is an inside job. Life passes through us like light through a prism and we control what comes out the other side.</p><p><strong>Take care of others. </strong>Once you’ve found your center, dedicate your life to the service of others. Build rapport through transparency and vulnerability. We like to think our problems are special and unique but they’re not and that makes them relatable. Use common ground to build trust and then carefully explore differences. Allow yourself to see someone else’s perspective and challenge them to take yours.</p><p><strong>Know what you want and understand the sacrifice it takes to have it. </strong>Everything is delicately interconnected and what you want is often diametrically opposed to something else you also want. We can waste a lot of energy trying to have both and getting frustrated. Instead, accept the tradeoffs and obsess over what it is that you want. Figure out exactly what it looks like in as much detail as you can. Then, rather delightfully, you may see that it’s right in front of you for the taking.</p><p><strong>Take it for granted that anything you can imagine can be real.</strong> The sooner you eliminate “can’t” from your vocabulary, the faster your dreams will become reality. Science has already proven the efficacy of the placebo: if you’re convinced something will make you feel better, you will start feeling better. And in just the same way if you’re convinced something can be done, it will be done. In the words of Henry Ford, “whether you think you can, or whether you think you can’t, you’re right.”</p><p><strong>The journey of a thousand miles starts with the first step.</strong> Everyone starts at zero. Zero sucks, I know. It’s that awkward, clumsy, sloppy period when you know just enough to know that you’re doing it wrong and everyone can tell. Spend as little time at zero as you can. Move faster than your self-doubt. Remind yourself that it doesn’t take much to be competent and competence will often give you just enough momentum to become good. Keep an eye out for shortcuts — focus on where you’re trying to go and don’t let your work ethic get in your way.</p><p><strong>Produce more light than heat.</strong> Use your energy to create more energy. Doing the opposite is easy. It takes a vision backed by ingenuity and lots of hard work to create something bigger than yourself. Put care, attention, and love into what you do and the rest will follow.</p><p><em>I wrote this back in January, when I turned 30. I was feeling particularly inspired and wanted to take some time to reflect on the life principles that are most important to me. I hope they speak to you.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a007b1e9332" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>