<?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 Christine Cha on Medium]]></title>
        <description><![CDATA[Stories by Christine Cha on Medium]]></description>
        <link>https://medium.com/@madebycha?source=rss-345052cfe535------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*tnAllBpjwNSEkVseySvV7g.png</url>
            <title>Stories by Christine Cha on Medium</title>
            <link>https://medium.com/@madebycha?source=rss-345052cfe535------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:20:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@madebycha/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[How to apologize remotely]]></title>
            <link>https://madebycha.medium.com/how-to-apologize-remotely-5f6bb08c0be0?source=rss-345052cfe535------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f6bb08c0be0</guid>
            <category><![CDATA[apologizing]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[remote-team]]></category>
            <category><![CDATA[communication-skills]]></category>
            <category><![CDATA[remote]]></category>
            <dc:creator><![CDATA[Christine Cha]]></dc:creator>
            <pubDate>Sat, 30 Jan 2021 20:06:10 GMT</pubDate>
            <atom:updated>2021-02-08T17:39:22.187Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to Apologize Remotely</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_DXhhsm9Jdz7vVR53xqzqg.png" /><figcaption>Original photo by <a href="https://unsplash.com/@claybanks">https://unsplash.com/@claybanks</a>.</figcaption></figure><p>After a year and a half of working remotely, a lot of things have assumed normalcy. Sharing screens. Cooking lunch. Finding headset-friendly hairdos.</p><p>Early on, one of my colleagues reached out for a quick but sincere apology (for interrupting me, even though I hadn’t even noticed!). I was initially surprised, then impressed, then moved. Since then, through personal attempts and observations, I’ve noted a pattern of factors that can make a remote apology more or less effective.</p><p>—</p><p><strong>1. Apologize early.</strong> If an apology feels absolutely necessary, it’s already very late. Offering a moment of vulnerability and compassion early on can prevent larger conflicts from ever growing. If you realize someone could have been negatively affected by your words or actions, it doesn’t hurt to check in. A preemptive apology might feel a bit silly at worst, but at best, it can be the turning point of a relationship.</p><p><strong>2. Be conscious of your method.</strong> Each case is unique, and there’s no right setting for an apology. Scheduling a video call might be critical when discussing larger conflicts with more nuance, but might feel overly formal for smaller issues. A chat message might have the quickest turnaround for a mild mistake, but could cause further misunderstanding when tone of voice is important. Scheduling a meeting ahead of time might give you both a week of anxiety, but preparation time might be necessary for heavier topics. Again, there won’t be a right answer, but try to be as considerate as possible with your strategy.</p><p><strong>3. Offer options. </strong>“Can you speak now?” Regardless of intention, this type of question presents a lot of pressure to say yes. Some other similarly leading phrases include “If you’re open to it” or “If you don’t mind”. These types of phrases are hard to reject, and that becomes the other person’s burden to carry. Instead, offer multiple unweighted options.</p><blockquote>“Can we talk now, if you’re free?” → <strong>“There’s no rush. I have time this afternoon or later in the week.”</strong><br>“Can you jump on a call?” → <strong>“I’m happy to just talk over chat or schedule a call.”</strong></blockquote><p><strong>4. Prepare. </strong>Think about what you’re going to say. What do you want to communicate? What are you actually apologizing for? Unlike more fluid in-person conversations, people tend to take turns speaking when remote. Prepare to be clear and concise, so that you leave as much room as possible for listening.</p><p><strong>5. Apologize without justification or defense. </strong>This is unrelated to being remote, but it’s too important to forget. For me, this is one of the hardest steps. It feels natural to want to explain yourself. “I’m sorry I raised my voice and insulted you, but it’s because I was made upset earlier by X.” This statement may be true, but regardless of the justification, this is *not* an apology. This is an explanation. As a rule of thumb, if you feel the urge to say “but” or any of its synonyms — stop talking right there!</p><blockquote>“I’m sorry I said those things, but I’ve been very stressed out lately due to personal issues.” → <strong>“I’m sorry I said those things.”<br></strong>“I’m sorry I kept interrupting you, but you speak very quietly and it’s hard to hear.” → <strong>“I’m sorry I kept interrupting you.”</strong></blockquote><p>If you still feel an urge to offer explanation, at least hold it until after their response. Explaining your behavior sounds very similar to justification, and can cancel the sincerity of your apology.</p><p>Finally, apologize for what you did, not how they felt. “I’m sorry you feel this way” is not an apology. In fact, it’s more like an accusation, implying that <strong>they</strong> are in fact the cause of the problem.</p><p><strong>6.</strong> <strong>Leave space. </strong>One of the most difficult parts of communicating remotely is dealing with empty space. Awkward silence. But it’s critical to leave room once you’ve finished your apology. It can be just as difficult to accept an apology as to offer one (and their preparation time was likely much shorter!). Wait and listen to their full response.</p><p><strong>7. Take action and accept feedback. </strong>What concrete steps can you take to learn from this in the future? “I’ll bring this up in the next 1:1 with my manager to see how I can improve my communication tone.” “Can you think of any other messages I’ve posted that felt condescending?” It’s difficult to maintain transparency and trust in remote relationships. Steps toward change need to be extremely clear and specific to be recognized.</p><p><strong>8. Leave the door open. </strong>When communicating remotely, there are fewer chances to reconvene spontaneously. To reduce any lingering tension, be clear that you welcome future conversation. A simple lighthearted follow-up can be the difference between not chatting again for months and rebuilding a friendship.</p><p>—</p><p>Don’t be too hard on yourself if things don’t go well. Apologies are difficult. And weird. Some conflicts take much longer than others to resolve. We’ve all been stuck inside for a year.</p><p>Besides, the only true apology is a change in behavior. 🌸</p><p>—</p><p><em>Live code &amp; more on Twitch: </em><a href="http://www.twitch.tv/madebycha"><em>twitch.tv/madebycha</em></a><em><br>Join my Discord: </em><a href="https://discord.gg/phpkY4NaY7"><em>discord.gg/phpkY4NaY7</em></a><em><br>Everything else: </em><a href="http://www.christinecha.com/"><em>christinecha.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f6bb08c0be0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Recurse Center: Three months of life-changing, super-powered learning and coding]]></title>
            <link>https://madebycha.medium.com/recurse-center-three-months-of-life-changing-super-powered-learning-and-coding-72b25321b76e?source=rss-345052cfe535------2</link>
            <guid isPermaLink="false">https://medium.com/p/72b25321b76e</guid>
            <category><![CDATA[recurse-center]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Christine Cha]]></dc:creator>
            <pubDate>Sun, 13 Mar 2016 21:26:04 GMT</pubDate>
            <atom:updated>2016-03-13T22:08:53.021Z</atom:updated>
            <content:encoded><![CDATA[<p>TL;DR: I’m finishing up my three months at the <a href="https://www.facebook.com/recursecenter/">Recurse Center</a> (previously known as Hacker School) and had the time of my life. Please feel free to ask me any questions if you’re even remotely interested!</p><p>Long version. Here we go.</p><p>—</p><p>I accidentally began my programming journey by doing some CSS and JQuery tutorials. I just wanted to have something change color on click.</p><p>Less than a year later, I’m learning about functors and monads in Haskell at three in the morning (shout out to Sean Lee), unable to sleep because it’s SO EXCITING. Crap. This was not the plan.</p><blockquote><strong>The past three months, I’ve been at the </strong><a href="http://recurse.com/"><strong>Recurse Center</strong></a><strong> — a short-term intensive programming retreat in SoHo. </strong>It’s not a bootcamp — there are no teachers, no classes, and no curriculum. It’s simply a curated learning environment packed with some of the most brilliant &amp;&amp; (not and/or!) generous people I’ve ever met.</blockquote><p>Each day has been a freeform mix of reading/learning/coding on my own, learning from others, helping others learn, and building cool stuff. I learned and was exposed to more new things during this time than I probably would have in years by myself (if ever).</p><p>Tech-wise, I worked mostly on <a href="http://christinecha.com/">web-based projects</a>, but also spent time experimenting with less-related stuff, like 3D modeling and functional programming (<a href="http://elm-lang.org/">Elm</a> + <a href="https://www.haskell.org/">Haskell</a>). Other people were building quadcopters from scratch, training neural networks, and math topics I don’t even understand enough to label.</p><p>A fun highlight that really encapsulates the amazingness of RC was when I <strong>paired with the creator of </strong><a href="http://elm-lang.org/"><strong>Elm</strong></a><strong> to learn Elm.</strong> For five hours straight. (whaaaaattt????!!?)</p><p>In a nutshell, <a href="http://recurse.com/">Recurse Center</a> helps you become a better programmer and also helps massively with job placement after your batch, if you want. Again, it’s TOTALLY FREE. Which is already amazing.</p><p>In a more fluid food-container — a grape shell? a dumpling? — it is a life-changing community of truly incredible thinkers and creators who then become your friends and colleagues forever. (… who also happen to debug (and respond) faster than Stack Overflow.)</p><p>Plus, I’m starting to feel pretty OK about calling myself a software developer now. <em>(Impostor syndrome is never over, but I’m working through it.)</em></p><p>—</p><p>If you made it to the bottom of this post, you’re either already at RC or at least somewhat interested in applying. <strong>WHAT ARE YOU WAITING FOR?!?</strong></p><p>Program details + application: <a href="http://l.facebook.com/l.php?u=http%3A%2F%2Fwww.recurse.com%2F&amp;h=RAQF5WL4yAQExc6KBKHM6hvVoo-sjpDjC7rw1x_2009Y6VA&amp;enc=AZP6zM2dNW2hCSSCFeL0oYfnsGimun8jS04iGbQu4-Gt9KPVrkFWXr-nerF2ixBWediTogU0briNUUUMGOdf9iH1t12YvQdMyy2-eR2435f_P_93v7BGq5z9c2BMQS8tGvb6HOMk4NH64MnJr2zL6XE8WePE3KjLHKckEa21mZ3wtooFIUfF2BDvejahCoial0c&amp;s=1">www.recurse.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72b25321b76e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>