<?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 Jey Yoo on Medium]]></title>
        <description><![CDATA[Stories by Jey Yoo on Medium]]></description>
        <link>https://medium.com/@jeyoo?source=rss-4ef54ef29e49------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jGZJLGeTUo_7kAzst5fulQ.jpeg</url>
            <title>Stories by Jey Yoo on Medium</title>
            <link>https://medium.com/@jeyoo?source=rss-4ef54ef29e49------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 01:08:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jeyoo/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[Why AI Companies Are Hiring Philosophers]]></title>
            <link>https://medium.com/@jeyoo/why-ai-companies-are-hiring-philosophers-90de0aee2bac?source=rss-4ef54ef29e49------2</link>
            <guid isPermaLink="false">https://medium.com/p/90de0aee2bac</guid>
            <category><![CDATA[policy]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[ai-ethics]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[philosphy]]></category>
            <dc:creator><![CDATA[Jey Yoo]]></dc:creator>
            <pubDate>Sun, 11 Jan 2026 05:54:37 GMT</pubDate>
            <atom:updated>2026-01-11T05:57:33.100Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R1-xSrJ2I1wkAeREg6D4NQ.png" /></figure><p><strong>AI companies are hiring philosophers. Not as a PR move. As a necessity.</strong></p><p>One thing I regularly do is scroll through LinkedIn, looking at job posts and their descriptions. It helps me understand what the market expects and how company priorities are shifting.</p><p>One role kept appearing at major AI companies: philosophy specialists hired for LLM alignment and model governance.</p><p>Philosophy.</p><p>The irony of calling upon ancient thought for the newest technology made me laugh, but it also made me curious. Why philosophy? Why circle back to our very foundation of being at this moment?</p><h3>Hypothesis #1: Philosophy activates when our self-understanding is threatened.</h3><p>LLMs felt like a breakthrough because they could do what we thought was uniquely ours: creative work, logical reasoning, even philosophical argumentation. This raised unsettling questions. What does it mean to be human? What traits remain uniquely ours?</p><p>When something challenges an organism’s integrity, its sense of self, its boundaries, the immune system activates. Philosophy functions this way for collective human identity.</p><p>Perhaps human uniqueness isn’t fixed but ever-changing, something we continually create rather than discover. <strong>Nietzsche warned of the “last man” who seeks only comfort and avoids all risk.</strong> <strong>Perhaps AI’s disruption, by forcing us to ask who we are, is precisely what prevents that complacency.</strong></p><h3>Hypothesis #2: AI replicates the output but not the meaning.</h3><p>When DeepMind’s AlphaGo defeated Lee Sedol in 2016, the world saw a machine play Go at superhuman levels. <strong>But did AlphaGo actually <em>play</em> Go?</strong></p><p>Jean Baudrillard wrote about <a href="https://www.gradesaver.com/simulacra-and-simulation/study-guide/summary">simulacra</a>: copies without originals, representations with nothing real underneath. AlphaGo fits this explanation. It produces outputs indistinguishable from human play, but <em>there’s no playing happening</em>. No strategy felt, no opponent considered, no panics sinking. The moves are signs referring to other signs (training data, reward functions, probability distributions) not to an underlying act of playing.</p><p>The unsettling question: Does the distinction matter? If simulation is indistinguishable from the real, can we still claim one is authentic?</p><p>And yet something in us resists. We feel that Lee Sedol’s Game 4 victory meant something beyond the move itself. The creativity, desperation, and courage behind it cannot be simulated. The meaning came from a human being choosing under pressure. Simulation replicates form but not meaning.</p><h3>Hypothesis #3: AI extends what Marx called alienation — the separation of humans from the process and meaning of their own activity.</h3><p>Karl Marx observed that industrial capitalism alienated workers from their labor. A craftsman who once made a chair from start to finish became a factory worker performing one repetitive motion, disconnected from the product and from himself.</p><p>AI extends this alienation into new domains: cognitive labor, creative work, even emotional care. When AI generates the output, the blank page disappears. So does the struggle of creating something from nothing.</p><p>Of course, using AI is still a process: prompting, iterating, refining. But it’s a different process. You’re no longer the creator. You’re the curator.</p><p>When the struggle shifts from making to selecting, what changes in the experience? I don’t know. But the question matters.</p><h3>Final Thought: What makes us human isn’t capability. It’s the quality of being here.</h3><p>Philosophy becomes a way to move through AI advancement rather than be swept away by it. Questions like where the boundary lies between human and machine, or where humans end and tools begin, cannot be answered by engineering alone. They require reflection on what we assume about intelligence, agency, and being. Philosophy is where that slower work happens</p><p>The difference between humans and AI isn’t just about output. It’s about what’s behind it.</p><blockquote>I believe what makes us human is the <strong><em>capacity to be in process</em></strong>, to experience becoming rather than merely produce results. Waking up tired. The small joy of morning coffee. Conversations that leave you feeling something you can’t name. The despair of losing, the return to try again, the unexpected move that surprises even yourself.</blockquote><p>This echoes Buddhist teachings on mindfulness:<strong> being aware of one’s current state and acting from awareness rather than automatic reaction.</strong></p><p>Maybe the real question isn’t what AI will take from us. <strong>It’s what we’ll finally be forced to claim as our own.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90de0aee2bac" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tips & Lessons Learned: Navigating the Grad School Application to UW’s MHCI+D Program]]></title>
            <link>https://medium.com/@jeyoo/tips-lessons-learned-navigating-the-grad-school-application-to-uws-mhci-d-program-a86a4e91511c?source=rss-4ef54ef29e49------2</link>
            <guid isPermaLink="false">https://medium.com/p/a86a4e91511c</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[graduate-school]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[mhcid]]></category>
            <category><![CDATA[hci]]></category>
            <dc:creator><![CDATA[Jey Yoo]]></dc:creator>
            <pubDate>Mon, 30 Sep 2024 05:26:18 GMT</pubDate>
            <atom:updated>2024-09-30T05:27:56.241Z</atom:updated>
            <content:encoded><![CDATA[<p>In the Fall of 2024, I was fortunate to be accepted into the University of Washington’s Masters of Human-Computer Interaction + Design (MHCI+D) program. This had been my dream school for a long time, so receiving the acceptance letter felt surreal.</p><p>Although I had been eyeing the program for quite some time, the preparation was more challenging than expected. I remember searching for references or resources from past alumni who had graduated from the program to guide my preparation.</p><p>In the hope that this might be useful to others interested in applying to MHCI+D, and as a way to document this phase of my life, here’s a brief overview of my application journey.</p><p><em>**Disclaimer: This was my personal journey to MHCI+D and does not represent the program’s recommended process.</em></p><p><em>**Every application journey is unique, and there is no right or wrong approach. My journey was one of many, and I hope my story can serve as a helpful reference.</em></p><pre>1. Overall Timeline<br>2. Recommendation Letters<br>3. Personal Statement<br>4. Resume(CV)<br>5. Portfolio<br>6. Final Thoughts</pre><h3>1. Overall Timeline</h3><p><strong><em>Tip #1 — Plan Early &amp; Reflect on Yourself Early</em></strong></p><p>This was my general timeline for applying to the program.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x_PqCDW4KTTCe2gMvHCoZg.png" /><figcaption>Note: I skipped August-September as no new actions were taken during those months.</figcaption></figure><p>Although I began working on different aspects of my application at specific points, I started planning and reflecting on what personal stories and themes I wanted to highlight in my portfolio and Personal Statement early on. This advance planning helped me gather materials, refine my thoughts, and ensure I had enough time to polish my final submission.</p><h3>2. Recommendation Letters</h3><p><strong><em>Tip#2 — Be Strategic About Who You Ask &amp; Ask Early with Preparation</em></strong></p><p>The UW MHCI+D program requires three recommendation letters. I sought letters from my university professor, a mentor who was a Head of Product Design, and an ex-colleague at work.</p><h4><strong>Why</strong></h4><p>I wanted to present a well-rounded view of myself, with insights from academic, design, and professional collaboration perspectives.</p><h4><strong>How I Asked</strong></h4><p>When requesting recommendation letters, remember that your recommenders are taking time out of their schedules to support you. Help them help you by preparing thorough materials outlining what areas you hope they’ll address in their letters. I prepared documents containing information about deadlines, the program itself, my past experiences, and my CV.</p><h3>3. Personal Statement</h3><p><strong><em>Tip#3 — Is Your Story Answering the Question?</em></strong></p><p>To be honest, the Personal Statement was the hardest part for me, and I rewrote the entire thing twice.</p><p>What helped me were two things: (1) watching the <a href="https://mhcid.washington.edu/how-to-learn-more/index.html">Information Session webinar</a> hosted by the MHCI+D program and (2) explaining my Personal Statement to my mom in <em>Korean</em>. Yes, it sounds a bit odd, but let me explain.</p><h4><strong>(1) Pick up hints from the Admins from the Information Session — trust me, the Admins want you to succeed as well.</strong></h4><p>What you want to remember is that the Admins want to get to know you and want you to prepare well. So they drop a lot of hints as to what they want to learn from you, especially in the program Information Session webinar. There is an uploaded online version, or you could attend the live session and ask questions if you have any. As for me, I watched the recorded webinar 3–4 times. Once you watch that many times, you start to recognize certain keywords and areas that the Admins emphasize.</p><h4><strong>(2) Does your Personal Statement answer the question? — explaining my paper to my mom in Korean</strong></h4><p>Explaining my Personal Statement to my mom in Korean was a breakthrough for me. Initially, I had a lot of stories I wanted to tell, hoping they would make me stand out. However, this led to a jumble of words that didn’t answer the prompt.</p><p>When I explained each paragraph to my mom, she’d occasionally ask, “What’s the purpose of that info?” Taking that process of translating each paragraph out loud made me realize I was rambling about myself with irrelevant information. This process helped me filter out unnecessary details and stay focused on answering the question.</p><p>So go back to the Personal Statement topic, check if your story connects the dots, and answer the questions — if that means reviewing and processing your paper in a different language and processing it as I did.</p><p>Here’s the actual Personal Statement prompt:</p><blockquote>In 500–800 words, please describe your unique interest in HCI and design, and explain what specific elements of the UW MHCI+D Program are aligned with your needs as an emerging HCI+D leader. Why this year? How have your prior experiences (professional or volunteer experience, life experience, and/or previous studies) prepared you for this program and this field? How do you plan to incorporate your personal ethics in your current or future work? How will this program assist you in your longer-term goals?</blockquote><p>My Simplified Version (*please note that this was my approach to the prompt — the analysis of the prompt can always vary depending on the person):</p><ul><li>What are you bringing to the table (MHCI+D) — your past journey</li><li>Why UW MHCI+D and what do you want to do at the program (research the program and explain why you’re a good fit) — your future plan</li><li>Why now?</li></ul><h3>4. Resume(CV)</h3><p><strong><em>Tip#4— Keep It Simple &amp; Get It Reviewed</em></strong></p><p>For my CV, I included:</p><ul><li>Short introductory paragraph about myself</li><li>Experience</li><li>Education</li><li>Activities/Certifications</li><li>Skills</li><li>Languages</li></ul><p>My initial CV was 2–3 pages long. After my mentor reviewed it, I condensed everything to one page using Figma. Make sure each section is readable and concise.</p><h3>5. Portfolio</h3><p><strong><em>Tip #5 — Are the points you have mentioned in your Personal Statement reflected in your portfolio?</em></strong></p><h4>Format &amp; Platform</h4><p>I used Wix to create my portfolio. As a beginner, I found it to be a good starting platform. My portfolio included: About Me, Resume (downloadable), Projects.</p><h4><strong>Case study topics</strong></h4><p>One key takeaway from the MHCI+D information session webinar I got was “make sure what you wrote can be seen in your portfolio.” I chose topics that aligned with my Statement of Purpose, mainly focusing on my work with Microsoft SaaS products.</p><p>I included six projects: three UI/UX design case studies and three tech/data-related passion projects. Looking back, I probably didn’t need to include that many. The admins usually have time to review just 1–2 projects, so three strong case studies would have been sufficient.</p><h4>Portfolio Reviews</h4><p>I was fortunate to have a mentor (shoutout to Annalisa!) review my portfolio and provide feedback. Additionally, I had my mom review it to get a more intuitive, third-party perspective on readability and tone. I recommend getting as many portfolio reviews as possible.</p><h4>After you submit</h4><p>One of the great things about having an online portfolio is that you can continue refining it even after submission. I kept going back to fix small details (formatting, colors, typos) that I missed earlier.</p><p>Also, I was able to track the real-time data on the location in Wix where my portfolio was getting reviewed — so my heart beat fast whenever I spotted “Seattle.”</p><h3>6. Final Thoughts</h3><p>My process for the MHCI+D was hectic, exciting, and collective work. It was hectic because there were a lot of things to do and I was crunching on time; it was exciting because I was given time to reflect on myself in-depth and put my thoughts into tangible form through my application, and collective work because I received so much help and support from so many people along the way.</p><p>The thought that helped me during my process is to not think too much about the results ahead, but just focus on giving everything you have into this process and leave the rest/result as it is.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a86a4e91511c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>