<?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 clice on Medium]]></title>
        <description><![CDATA[Stories by clice on Medium]]></description>
        <link>https://medium.com/@cliceleee?source=rss-27691f55523b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ak_isJETkxjFtwILZeIxxw.png</url>
            <title>Stories by clice on Medium</title>
            <link>https://medium.com/@cliceleee?source=rss-27691f55523b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 23:36:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cliceleee/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[Google Solution Challenge Top 3 Winning Strategies, Praised by the Country Director of Google Korea]]></title>
            <link>https://medium.com/@cliceleee/google-solution-challenge-top-3-winning-strategies-praised-by-the-country-director-of-google-korea-f5496f70e910?source=rss-27691f55523b------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5496f70e910</guid>
            <category><![CDATA[google-solution-challenge]]></category>
            <category><![CDATA[google-technolo]]></category>
            <category><![CDATA[medical]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[gemini]]></category>
            <dc:creator><![CDATA[clice]]></dc:creator>
            <pubDate>Sat, 02 Aug 2025 17:33:11 GMT</pubDate>
            <atom:updated>2025-08-03T04:15:13.902Z</atom:updated>
            <content:encoded><![CDATA[<p>Top 3 Most Societal Impact Award (Medicall by team Atempo)</p><p>This article is based on the talk I gave at <a href="https://www.ticketa.co/events/7">Google I/O Extended Incheon.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ha_GDnplGlx_grJ34wkYxA.png" /></figure><p>Hello,<br>I’m clice(Jimin Lee), and I recently gave a talk on the strategies that took me from being an ordinary student to becoming a global award recipient in just six weeks with the help of AI.</p><p>I was just an ordinary-university-student.<br>Yet in only six weeks, I achieved the milestone of being selected as one of the Top 3 teams in Asia for the <strong>Google APAC Solution Challenge 2025</strong>.</p><p>What made this possible was my strategic use of AI, guided by four key approaches.<br>In this post, I’ll share how I was able to reach such results in such a short time and the challenges I faced along the way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P1PIzkE8wXQn6J2Lw6EpfQ.png" /></figure><p>First, a brief introduction. I’m currently a third-year university student, known online as the “clice.”<br> I founded and now lead a startup called <strong>Dyce Lab</strong>, where I serve as Founder &amp; CEO.<br> Previously, I worked as a front-end developer at an SI company, and I have also taken part in various extracurricular and community activities.</p><p>However, what truly drives me is not just “development” itself, but the collaboration, challenges, and pursuit of solving meaningful problems.<br> My first real step in that direction came two years ago, when I joined a university tech community called <strong>GDG on Campus Konkuk</strong>.</p><h3>GDG on Campus</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D4BmfhIpof8nMZKQsfn1lA.png" /></figure><p><strong>GDG on Campus</strong> is not just another university club. It’s an official Google developer community active in 1,863 campuses across 111 countries, with 37 chapters in South Korea alone.<br> Membership is based on passion rather than skill level, and activities center around projects, study groups, and hackathons.</p><p>Joining this community became a turning point in my life.<br> It was here that I first learned about the <strong>Solution Challenge</strong> — a competition open exclusively to GDG on Campus members.</p><h3>Google APAC Solution Challenge</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*exqx0tk5vXeB0EwaShXVwg.png" /></figure><p>The <strong>Solution Challenge</strong> is Google’s flagship competition for student developers, launched in 2020. Each year, it attracts participants from over 2,000 GDG on Campus universities across more than 110 countries, making it a truly global event.</p><p>While the theme changes annually, it consistently centers on building solutions to address social challenges aligned with the <strong>UN Sustainable Development Goals (SDGs)</strong>. South Korea is one of the countries that sends the largest number of teams to the global Top 100 each year.</p><p>Until last year, the competition was held on a single global stage. Starting this year, however, it has been divided into regional events. As part of Asia, South Korea now competes in the <strong>Asia-Pacific (APAC) Solution Challenge</strong>.</p><p>In this year’s APAC competition, <strong>3,370 students</strong> applied. After multiple rounds of evaluation, the <strong>Top 10 teams</strong> were selected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uINfDGMoAiM10wH4U_bs8A.png" /></figure><p>Among this year’s selected teams, South Korea stood out with <strong>three teams</strong> in the Top 10 — the most of any country. <em>Applause!</em></p><h3>Final Stage</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nZkPX4x8xePjG2Rfuluhcw.png" /></figure><p>The final stage took place over two days at the <strong>Asian Development Bank (ADB) headquarters</strong> in Manila, Philippines. The global Top 10 teams were invited to present their solutions in front of Google engineers, government officials, investors, and CTOs.</p><p>Students from <strong>10 teams across 6 countries</strong> showcased their projects live on stage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eyzRr78lFWApnHJ9rxtZvA.png" /></figure><p>Instead of giving an on-stage presentation, our team introduced our solution from a dedicated booth inside the ADB headquarters. There, we engaged directly with attendees and judges, presenting in English about our team, the problem we set out to solve, and demonstrating our solution live.</p><p>We received questions from investors about the development costs, had our business model scrutinized, and fielded in-depth technical inquiries from professional developers regarding our system architecture — providing us with a genuine opportunity for technical validation.</p><p>This demo booth was more than a simple feature showcase; it was proof that our solution could be applied in real-world contexts.</p><p>After two days of demonstrations, the judging panel selected the final <strong>Top 3</strong> teams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hfQJ0Rv-Tg1uwG_5nBuZSQ.png" /></figure><p>There was no ranking within the Top 3 — all three teams were recognized as co-winners. The awards were presented in three categories: <strong>Best AI Use Case</strong>, <strong>Social Impact</strong>, and <strong>People’s Choice</strong>.</p><h3>Top 3 (Most Societal Impact Award)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-5NHWiqvq1Fd9FD2" /></figure><p>We competed under the name <strong>Team Atempo</strong>, developing <em>Medicall</em> — a mobile application for emergency medical responders. Our project placed in the <strong>Top 3</strong> and received the <strong>Social Impact Award</strong> for its potential to create meaningful societal change.</p><h3>Core message I want to convey</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tged2gmAbCF9Gmmde5iy4A.png" /></figure><p>The message I want to share today is simple, and it comes down to four points: anyone can take on the world stage if they know how to use the right tools effectively.</p><p>I had neither a privileged background nor exceptional technical expertise. But I clearly identified the problem, collaborated closely with AI, and pushed through to the end with a reliable team.</p><h3>1. Devote over 80% of your effort to choosing the right problem to solve</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eZsuYwfqrH6qBBpOapIzTg.png" /></figure><blockquote>Please, please, please, I BEG YOU!! STOP MAKING ‘AI EMOTION DIARIES’ or ‘Psychological analysis app’</blockquote><p>In competitions like this, the <strong>topic</strong> is everything. Even with advanced technology, a weak topic will fail to gain attention. If you can’t capture the judges’ interest, you won’t even get the chance to showcase the technology you’ve built.</p><p>Your topic must have real impact — it should address a clear social need and have the potential to drive tangible change. As the name <em>Solution Challenge</em> implies, the focus must be on solving a meaningful problem.</p><p>Avoid overused and generic ideas such as simple mood diaries or basic mental health counseling apps. These concepts are already saturated with similar solutions and rarely deliver new or distinctive impact.</p><blockquote>Honestly, it’s hard to imagine a “psychological counseling AI” beating 3,370 other participants to take first place in Asia at a Google competition.</blockquote><p>If your true goal is to win, you must choose a problem that is absolutely essential to solve and approach it in a way that hasn’t been done before. One common mistake is building a service that doesn’t align with the nature of the competition. The type of product the competition is looking for is clearly and explicitly stated in the judging criteria.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4JWXWindBwulHYff1wAJ0w.png" /></figure><p>This year’s judging criteria highlight keywords such as <strong>community impact</strong>, <strong>originality</strong>, <strong>novel approach</strong>, and <strong>improvement</strong>.</p><h3>Medicall이 발견한 문제</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m-VCt6BYnE5iclei08DUVA.png" /></figure><p>Let me illustrate this with the problem we chose. In South Korea’s emergency medical system, there has long been a structural issue known as the <strong>“ER ping-pong”</strong> problem. When paramedics transport a patient, they must call hospitals one by one to manually confirm whether the patient can be admitted.</p><p>This process can take anywhere from several minutes to, in severe cases, tens of minutes. During that time, patients lose their golden hour, and their chances of survival drop sharply.</p><h3>Medicall 솔루션</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d96Nbey-OVvL6fmUsnMqdQ.png" /></figure><p>To address this problem, we developed <strong>Medicall</strong>, a medical application designed to streamline and optimize the emergency admission process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*2p5TsNJMSbIRSMXj2EUtiA.gif" /></figure><p>The paramedic first sets the patient’s current location and the desired search radius, then inputs the patient’s condition.<br> Upon pressing the <strong>Find Hospital</strong> button, the AI automatically searches for nearby hospitals that meet the criteria. It then simultaneously calls these hospitals to request confirmation of admission availability.</p><p>Hospitals respond directly through a keypad input: pressing <strong>1</strong> indicates “Available,” while pressing <strong>2</strong> indicates “Not Available.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*QDktHFAjO3-Z_oSgx4rTbg.gif" /></figure><p>Based on these responses, Medicall compiles the results in real time and displays the hospitals in order of proximity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*7MPW4Z-YsYkZJuSLteF4Lg.gif" /></figure><p>Then, it also provides real-time navigation to the selected hospital.</p><h3>Architecture</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sJWyT-nT7gtlYUYZXbbvyQ.png" /></figure><p>Let me explain the architecture in more detail.</p><p>First, the paramedic uses our <strong>Flutter-based mobile app</strong> to enter the patient’s condition and current location. This information is sent to the <strong>backend server</strong>, which handles authentication, hospital candidate filtering, caching, and data storage.</p><p>Based on the patient information, the <strong>AI server</strong> uses <strong>Gemini</strong> to generate an automated voice message for hospitals. It also determines which hospitals to contact by matching the patient’s condition with the relevant medical departments listed on Google Maps.</p><p>Next, the system uses the <strong>Twilio API</strong> to place simultaneous automated calls to multiple hospitals. Upon receiving the call, the hospital staff respond via keypad input — <strong>1</strong> for “Accept” or <strong>2</strong> for “Decline.” This response is then sent back to the server.</p><p>Once the server receives a hospital’s response, it immediately sends the hospital’s name and location to the mobile app. The final decision on which hospital to go to remains with the paramedic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E6oUAWmGftx4WP-w4tJIdw.png" /></figure><p>The idea for Medicall didn’t come from some distant inspiration — it originated from a very real and personal experience within our team. One teammate’s mother was once a patient in an ambulance, and he rode along as her guardian. It took an unreasonably long time to find a hospital that could accept her. The ambulance had to circle around multiple hospitals before finally finding one with an available bed.</p><p>Hearing this story, our team became convinced that solving this problem could create a profound social impact. We immediately began planning Medicall and designing the MVP.</p><p>To verify that this wasn’t just an isolated incident, we reached out to a practicing physician and conducted an interview. The feedback confirmed that this was indeed a serious, systemic issue in emergency care — one that urgently needs resolution.</p><p>Technology, on its own, can be impressive. But without starting from an actual user need, it will never become a truly valuable service. We began with that user need and built our solution from there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uHPGm3IOByH6rI7yFi0_1A.png" /></figure><p>Medicall was designed to fit seamlessly into a paramedic’s real-world workflow, ensuring it can be used immediately in the field. It is not just a conceptual prototype — it is a fully developed MVP with AI integration, automated hospital calling, and real-time navigation.</p><p>Due to time constraints, I’ll skip the technical deep dive here, but those interested can find detailed information on the official Medicall website.</p><h4>Six weeks left…</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tU-C8UilF-2BaNkvQCYZTA.png" /></figure><p>With the planning complete, we had just six weeks left. From design to development, it was nowhere near enough time to build a fully functional MVP.</p><h3>2. Building from a single step forward</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-r5UwU1e4z3VSQUK-pCTJQ.png" /></figure><p>The second key point I want to share is this: <strong>start from one</strong>.<br> Our team didn’t start from zero. I had prior experience as a front‑end developer, but this was my first time building a mobile application. There simply wasn’t enough time to learn Flutter from scratch through lectures or tutorials.</p><p>Instead of building everything from the ground up, I focused on analyzing well‑designed, existing applications. I studied map‑based apps like <em>Baemin</em> (Korea’s top food delivery service) to understand how users navigate the app and what makes a UI feel intuitive.</p><p>One particular feature in <em>Baemin</em> caught my attention: <strong>automatic location detection</strong>. This introduced me to the concept of reverse geocoding. In emergency scenarios, skipping manual address entry and auto‑filling it instead could save crucial seconds.</p><p>Since I had never implemented reverse geocoding before, I turned to AI for assistance. I provided examples from <em>Baemin</em>, explained the reverse geocoding concept, and asked the AI to design the required architecture and code. The result was a ready‑to‑implement solution that allowed us to integrate the feature quickly and effectively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*Q2dPNCFa5hoAvJYAhnb50g.gif" /></figure><p>We applied reverse geocoding to <em>Medicall</em>, enabling a much faster address‑input process during emergencies.</p><p>The lesson was clear: when working under tight deadlines, the key is not to reinvent the wheel but to quickly adopt proven solutions and evolve them into your own with the help of AI.</p><h3>3. Build at Least the Fundamentals Before Using AI</h3><blockquote>So, can you build an MVP entirely with AI and no coding skills?<br> <strong>No.</strong></blockquote><p>To achieve meaningful results in a short time, you must combine the power of AI with a solid foundation in core skills. AI is an incredibly powerful generative tool, but without fundamental technical knowledge, you’ll hit a ceiling fast. You might be able to create something simple like a landing page, but you won’t be able to debug issues, expand features, or fully understand the intent behind the AI‑generated code.</p><p>Without those fundamentals, the output from AI becomes nothing more than a copy‑and‑paste exercise — fast to produce, but limited in speed, quality, and long‑term viability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IiOFKKEYmA0vAG61fd4zWw.png" /></figure><p>This actually happened to me during development. When I asked AI to fix a login issue, it suggested deleting the entire project and cloning it again from the repository. Its intent seemed to be to discard all local modifications and restart from the remote repository version. However, if that was the goal, a more appropriate approach would have been to use git restore . or git reset --hard instead of removing the entire project directory. The takeaway: AI’s suggestions are not always optimal or safe. Without foundational knowledge, blindly following them can lead to data loss and wasted time. AI is a tool—the developer must choose the right approach.</p><h3>Extended from my JavaScript experience into Flutter</h3><p>Beyond handling issues, I want to share how I was able to understand the code.<br> As a frontend developer with experience building UI components in React, I could quickly compare my usual approach with the Flutter/Dart code generated by AI, understand it, modify it, and refine it to match exactly what I wanted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x6VMeJ8ZCRwNz-H0-uN41Q.png" /></figure><p>On the left is JavaScript with styled‑components, and on the right is Dart.<br> I compared them side by side to understand Dart more easily.<br> In JS+CSS, styled‑components let you declaratively define styles such as font-size, font-weight, font-family, and color. In Flutter, you use a TextStyle object to set the same properties.<br> In JS, spacing between elements can be handled by giving a div a specific height, whereas in Flutter, you achieve the same with SizedBox(height).<br> Structurally, React and Flutter felt very similar. Both are component‑based and define UI declaratively in code, so I could quickly understand Dart without having to deeply study the language first.</p><h3>Rapid MVP Validation with AI</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yvOlpJx-y4QQCGbDkLaHnQ.png" /></figure><p>To build our MVP within such a short timeframe, we leveraged AI to accelerate development and rapidly iterate based on feedback. This fast iteration cycle significantly improved our product’s completeness. After creating the initial prototype, we immediately refined it using feedback from both our team members and practicing physicians. For example, instead of having the patient condition input form share the same screen as the map, we split it into a separate screen so that paramedics could enter patient information on a larger, more readable interface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*O5CugwSMTBgCyI8bsl13cw.png" /></figure><p>We then introduced a <strong>Quick Symptoms</strong> feature — essentially hashtag-style preset buttons for frequently encountered patient conditions — allowing paramedics to input symptoms with a single tap. AI rapidly generated and refined the necessary code, accelerating user-centered improvements. In short, achieving results in a short timeframe requires starting with proven solutions, quickly adapting them with AI to fit your own approach, and continuously refining the product based on real user feedback.</p><h3>4. If You’re Serious, Obsess Over Every Detail</h3><p>Lastly, I want to talk about details.<br> When we made it to the Top 10 and were preparing for the finals, we didn’t receive the exact format of the event until very late. We only found out five days before the finals — including the weekend — that the finals would be held as a booth exhibition. That gave us very little time to prepare.</p><p>With a limited space shared among all Top 10 teams, we didn’t expect every judge to visit every booth.<br> So let me ask you: <em>If you had only one week to prepare your booth, what would your strategy be?</em> Some might say product refinement, others might focus on improving the UI/UX. But our team decided to create a banner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vgqoNDRVM-Y_zJe6JpTGhA.png" /></figure><p>Earlier, I mentioned that if you fail to catch the judges’ attention with your topic, you won’t even get the chance to showcase your product.<br> The same rule applies on-site. If you don’t draw attention at the venue, you won’t get the opportunity to present your service.</p><p>So I quickly designed a banner.<br> I found a printing service that could produce it the same day, placed the order, and picked it up on Monday.<br> The next morning, I boarded a flight to Manila with the banner in hand.<br> This allowed us to successfully set it up at our booth for the finals.</p><h3>Preparing for the English Presentation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/658/0*ygm5akeSHdpG4JPG" /></figure><p>And because the entire event was conducted in English, we poured the rest of our energy into preparing our English presentation.<br> While English is often considered an essential skill for developers, delivering a presentation and answering questions in English as a Korean in an international setting is no easy task.<br> We prepared a one‑minute English pitch introducing our solution and crafted answers for anticipated questions. Even on the flight to Manila, I pushed my teammates to memorize their scripts.</p><p>Our competitive edge came from these kinds of <em>details</em>. We stood out to global judges through a striking red banner, a memorable team name — <em>Atempo</em> — and a confident English presentation.<br> The red banner, in particular, was a deliberate strategy to combine visual impact with explanation efficiency. We were the only team to bring a banner to the finals, which visually set us apart. The printed app screens on the banner also made it easier to explain our service during booth interactions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E-OmC0Yq6vASRz5miHKvBg.png" /></figure><p>Lastly, here’s a practical tip I’ve never shared anywhere else — choose a team name that starts with the letter <strong>A</strong>.<br> Last year, I was selected for the Top 100 in the Google Solution Challenge. However, our team name back then was <em>Glow Alarm</em>, which started with a “G,” placing us somewhere in the middle of the winner list and making it less visually noticeable.</p><p>While Google does not officially rank teams, they often sort lists and presentation orders alphabetically. I assumed the same would apply this time, and I knew that the first teams introduced — whether in presentations or booth tours — naturally draw more attention.</p><p>So we intentionally chose a name starting with “A,” and as a result, we appeared at the very top of the winners list. It’s a small detail, but this kind of strategic choice can significantly boost visibility..</p><blockquote>Focus 80% on Choosing the Right Problem<br> Start from 1, Not 0<br> Build at Least the Fundamentals Before Using AI<br> If You’re Desperate, Obsess Over Every Detail</blockquote><blockquote>Thanks to these four strengths, we secured a spot in the Top 3 of the Solution Challenge.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HaMoDh7I0_vgIaszS0yp0w.png" /></figure><p>After the award, my life changed far more than I had imagined. It was just one prize, but it brought an unexpected wave of events.<br> At the Manila finals, simply being “an award recipient” led to constant photo requests from locals right after my presentation. Back in Korea, it naturally turned into interview requests, hackathon mentoring invitations, and new connections with a wide range of people.<br> From Google Korea’s Country Director, Harrison Kim, personally posting a congratulatory message on LinkedIn, to multiple media interviews, and even hackathon mentoring requests — it all started from this one competition.<br> This event was not just a place to receive a prize. For me, it became a shortcut to meeting new people and unlocking new opportunities. My initial goal may have been the award, but in reality, the award was just the beginning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q4B8tjXzRST1rJEf-E4ARg.png" /></figure><p>And in fact, there’s one important story I haven’t shared until now.<br> While developing Medicall, I genuinely fell in love with the service itself. This wasn’t just a project for a competition — I saw its real potential to save lives.<br> Even during the competition period, I applied to a startup pitch competition and was accepted, securing a spacious office as part of the support package.<br> That’s how Dyce Lab, the startup I now lead as CEO, was born.<br> It became the launchpad for my startup journey.</p><h3>The Launchpad for Our Startup</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JQV0F89uqfzxxDJmcXdEmQ.png" /></figure><p>The National Emergency Medical Center reached out to us first. As an agency under the Ministry of Health and Welfare, it is the central administrative body responsible for shaping Korea’s emergency medical policies and managing its systems.</p><p>When we were designing Medicall, we had analyzed the national system operated by the center — where staff manually call hospitals to match patients to available emergency rooms — and started with the question, <em>“How can we replace this?”</em> Ironically, it was the very institution behind that system that contacted us after seeing a news article about our work.</p><p>The center invited us to officially present Medicall at an emergency medical seminar and expressed interest in discussing how the technology could be integrated into real-world medical operations and connected with existing policies and systems.</p><p>Hearing this, our team felt deeply moved. This was no longer just a competition project. We now had the opportunity to work directly with the institution that drives national emergency medical policy, with the potential to contribute to tangible policy and system changes.</p><p>From this point forward, we resolved to prepare even more rigorously and to collaborate with humility to turn Medicall into technology that can truly change the world.</p><p>Achieving Top 3 in the Google Solution Challenge not only gave us visible recognition but also became a powerful trust signal for hospitals, investors, and society at large.<br> But this change didn’t happen overnight.</p><h3>The Secret Behind How an Ordinary Student Made a Big Impact</h3><p>I wasn’t someone special from the start.<br> Before joining GDG on Campus, I had only completed my first semester as a freshman. I was just an ordinary computer science student who didn’t even know the difference between frontend and backend.</p><p>But GDG on Campus welcomed me, believing in my passion and potential rather than my skills. Thanks to that, I was able to broaden my perspective and truly begin exploring various fields.</p><p>There, I met diverse people, gained opportunities to take on challenges, and was constantly inspired. All of those experiences accumulated and eventually led to our achievement of placing in the Top 3 at the Google Solution Challenge.</p><p>For me, GDG on Campus was more than just a community — it was the starting point that changed my life.</p><h3>GDG on Campus, Google Developer Group</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gz6vGWYBSazOQC6RJF5gxw.png" /></figure><p>If you’re a university student, there’s a good chance your school already has a GDG on Campus chapter. Recruitment will open soon, so I strongly encourage you to apply.<br> And if your school doesn’t have one yet, that might be an even better opportunity — you could become the very first GDG on Campus lead and start it yourself.</p><p>If you’re not a student, you can still join your local Google Developer Group. You can find more details on the official website.</p><p>clicelee@dycelab.xyz<br><a href="http://threads.com/@clicelee"> @clicelee</a></p><p>If you have any questions about the Solution Challenge or this article, feel free to reach out anytime. Thank you:)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5496f70e910" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[구글 코리아 사장님이 칭찬하신 Google Solution Challenge Top3 수상 전략 정리]]></title>
            <link>https://medium.com/@cliceleee/google-solution-challenge-top-3-winning-strategies-praised-by-the-country-director-of-google-korea-50fde03e5c36?source=rss-27691f55523b------2</link>
            <guid isPermaLink="false">https://medium.com/p/50fde03e5c36</guid>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[google-solution-challenge]]></category>
            <category><![CDATA[flutter]]></category>
            <dc:creator><![CDATA[clice]]></dc:creator>
            <pubDate>Sat, 02 Aug 2025 17:04:00 GMT</pubDate>
            <atom:updated>2025-08-02T17:37:41.300Z</atom:updated>
            <content:encoded><![CDATA[<p>Top 3 사회적 영향력 부분 최고상(Medicall by team Atempo)</p><p>본 아티클은 <a href="https://www.ticketa.co/events/7">Google I/O extended Incheon</a>에서 연사한 내용을 바탕으로 작성되었습니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e7qYIPaHfQBi3_9yWUUztQ.png" /></figure><p>안녕하세요</p><p>평범한 학생인 내가 AI로 6주 만에 글로벌 수상자가 된 전략에 대해 발표했던 <a href="https://medium.com/u/27691f55523b">clice</a>입니다.<br>저는 평범한 대학생이었습니다.<br>그러나 단 6주 만에, Google APAC 솔루션 챌린지 2025에서 아시아 중 Top 3에 선정되는 성과를 거뒀습니다.</p><p>이 과정에서 결정적인 역할을 한 것은 바로 AI활용과 4가지 전략이었기 떄문이었습니다.<br>오늘 이 글에서 단기간에 어떻게 그 결과를 만들 수 있었는지, 그리고 그 여정에서 제가 어떤 도전을 했는지 공유드리려 합니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P1PIzkE8wXQn6J2Lw6EpfQ.png" /></figure><p>먼저 제 소개를 간단히 하겠습니다. 저는 대학 3학년에 재학 중이며, 온라인에서는 주사위 개발자 라는 이름으로 활동하고 있습니다 .</p><p>현재 ‘<a href="https://dycelab.xyz/">다이스랩</a>’이라는 스타트업을 설립해 대표로 운영중이며. <br>과거에는 SI 회사에서 프론트엔드 개발자로 일했습니다 그 외에도 다양한 대외활동도 경험했습니다.</p><p>하지만 저에게 더 큰 동기를 주는 것은 ‘개발’ 자체보다는 사람들과의 협업, 도전, 의미 있는 문제 해결이었습니다.<br>2년전 제가 한 첫 도전은 ‘GDG on Campus 건국’이라는 대학 동아리에 가입한 것이었습니다.</p><h3>GDG on Campus</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D4BmfhIpof8nMZKQsfn1lA.png" /></figure><p>GDG on Campus는 단순한 대학 동아리가 아닙니다. 전 세계 111개국, 1,863개 캠퍼스에서 운영되는 Google 공식 개발자 커뮤니티로, 한국에만 37개 대학에 챕터가 있습니다.<br>실력에 상관 없이 열정으로 선발하며, 다양한 프로젝트와 스터디, 해커톤을 중심으로 활동합니다. <br>바로 이 동아리에 들어간 것이 제 인생의 전환점이 되었습니다. <br>그리고 이곳에서 저는 GDG on Campus 멤버만 참여 가능한 솔루션 챌린지를 처음 알게 되었습니다.</p><h3>구글 APAC 솔루션 챌린지</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*exqx0tk5vXeB0EwaShXVwg.png" /></figure><p>솔루션 챌린지는 2020년부터 시작된 Google의 대표적인 학생 개발자 대회입니다. 매년 전 세계 110여 개국, 2,000여 개 GDG on Campus 대학의 학생들이 참여하는 글로벌 규모의 대회입니다.</p><p>주제는 매년 변경 되지만 주로 UN이 정한 SDG 사회 문제를 해결하는 솔루션을 만드는 것에서 크게 벗어나지 않습니다. 한국은 매년 Top 100에 가장 많은 팀을 진출시키는 국가중 하나입니다.<br>작년까지는 글로벌 단위로 대회가 진행 되었다면, 올해부터는 대륙별로 나뉘어서 진행 되었습니다.<br>아시아에 위치한 대한민국은 아시아 태평양, 솔루션 챌린지 Apac에 참가하였습니다.</p><p>올해 에이팩에 참가를 신청한 학생 수는 3370명에 다했고, 이중에서 심사를 거처 Top 10이 선정되었습니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uINfDGMoAiM10wH4U_bs8A.png" /></figure><p>올해 선정된 팀을 보시면 한국이 무려 3팀으로 가장 많습니다. (짝짝짝~~)</p><h3>본선 현장</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nZkPX4x8xePjG2Rfuluhcw.png" /></figure><p>본선은 필리핀 마닐라에 위치한 아시아개발은행(ADB) 본사에서 2일간 진행됐으며, 전 세계 Top 10 팀이 초청되어 각국의 구글 엔지니어, 정부 관계자, 투자자, CTO 앞에서 직접 개발한 서비스를 선보였습니다.<br>10개의 팀, 6개국에서 온 학생들이 직접 현장에서 서비스를 소개했습니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eyzRr78lFWApnHJ9rxtZvA.png" /></figure><p>저희는 무대 발표 대신 ADB 본사 내부에 마련된 부스 공간에서 참가자들과 심사위원을 대상으로 서비스를 소개했습니다. 영어로 저희의 팀의 소개, 어떤 문제를 해결하였는지 설명하고 솔루션을 직접 시연하였습니다. 투자자들로부터 개발하는데 들어간 비용에 대해 질문을 받았고, 비즈니스 모델에 대해 검증을 받았으며 실제 현업 개발자로부터 기술 구조에 대한 구체적인 질문도 받는 등 실질적인 기술 검증의 기회가 주어졌습니다.<br>이 데모 부스는 단순한 기능 소개가 아닌, 솔루션이 실제 현장에 적용 가능하다는 점을 증명하는 자리였습니다.</p><p>이렇게 2일간 데모데이를 마치고, 심사를 거쳐 Top 3를 최종 선정하게 됩니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hfQJ0Rv-Tg1uwG_5nBuZSQ.png" /></figure><p>순위는 없이 Top 3 모두 공동 수상입니다. Best AI Use Case, Social Impact, People’s choice 이렇게 세개의 상이 있습니다.</p><h3>Top 3 (Most Societal Impact Award)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-5NHWiqvq1Fd9FD2" /></figure><p>저희는 팀 ‘Atempo’라는 이름으로 참가했습니다. 응급 구조사를 위한 모바일 어플리케이션 ‘메디콜’을 개발해 이 대회에서 Top 3 안에 들었고 사회적 임팩트 최고상을 수상했습니다.</p><h3>전하고 싶은 것의 가장 중요 주제</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tged2gmAbCF9Gmmde5iy4A.png" /></figure><p>오늘 제가 전하고 싶은 메시지는 이렇게 네가지로 단순합니다.. 누구나, 도구를 잘 활용하면 전 세계를 무대로 도전할 수 있다는 것입니다.<br>저는 특별한 배경도, 뛰어난 기술력도 없었습니다. 하지만 문제를 정확히 파악했고, AI와 협업했고, 그리고 믿을 수 있는 팀과 함께 끝까지 밀어붙였습니다.</p><h3>1. 주제 선정에 80%이상 신경쓰기</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eZsuYwfqrH6qBBpOapIzTg.png" /></figure><blockquote>제발 제발 제발 감정 일기 AI 만들지 좀 마세요</blockquote><p>대회에서 가장 중요한 것은 ‘주제’입니다. 기술이 뛰어나도 주제가 약하면 주목받지 못합니다. 심사위원의 눈을 끌지 못한다면 그 안에 구현된 기술을 보여줄 기회 조차 없습니다.</p><p>주제가 임팩트 있어야 합니다. 사회적 필요성 분명하고, 실질적 변화를 이끌어 낼 수 있어야 합니다.<br>솔루션 챌린지라는 이름에서도 알 수 있듯이 문제를 해결하는데 집중해야 합니다.<br>단순한 감정일기 어플, 심리상담 앱처럼 반복되고 흔한 아이디어는 절대 권장하지 않습니다. 유사한 솔루션은 이미 많고, 새로운 임팩트를 만들지 못하기 때문입니다.</p><blockquote>객관적으로 생각해도, 구글 대회에서 ‘심리 상담 AI&#39;가 3370명을 누르고 아시아1등 할 수 있을것 같진 않잖아요</blockquote><p>여러분이 정말 상을 목표로 한다면, 반드시 필요한 문제를 선택하고, 기존에 없던 방식으로 접근해야 합니다. 많은 분들이 놓치는 것이 대회 성격과 맞지 않은 서비스를 만든다는 점입니다. 대회에서 원하는 프로덕트는 명확하게, 명시적으로 심사 기준에 나와있습니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4JWXWindBwulHYff1wAJ0w.png" /></figure><p>이번 심사기준을 보시면 지역사회, 참신한 아이디어, 새로운 접근 방식, 개선과 같은 키워드가 눈에 보입니다.</p><h3>Medicall이 발견한 문제</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m-VCt6BYnE5iclei08DUVA.png" /></figure><p>저희가 선택한 문제 상황을 예시로 들어보게습니다. 한국의 응급의료 체계에는 오랫동안 ‘응급실 뺑뺑이’라는 구조적 문제가 존재합니다. 응급구조사들은 환자를 이송할 때, 병원에 일일이 전화를 걸어 “수용 가능 여부”를 직접 확인해야 합니다. 이 과정은 평균 수 분에서 길게는 수십 분까지 걸립니다. 그 사이 환자는 골든타임을 잃고, 생존 가능성도 급격히 낮아집니다.</p><h3>Medicall 솔루션</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d96Nbey-OVvL6fmUsnMqdQ.png" /></figure><p>저희는 이 문제를 해결하기 위해 의료 어플리케이션 메디콜(Medicall)을 만들었습니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*2p5TsNJMSbIRSMXj2EUtiA.gif" /></figure><p>응급 구조사가 환자 현재 위치와 검색 반경을 설정합니다.<br>그 다음 환자의 상태를 입력합니다.</p><p>그리고 병원찾기 버튼을 누르면, AI가 조건에 맞는 인근 병원을 자동으로 탐색합니다. 탐색한 병원들에 동시에 전화를 걸어 수용 가능 여부를 물어봅니다. <br>이에 대해, 병원이 직접 캐피드로 응답을 합니다. 1번을 누르면 “수용 가능” 또는 2번을 누르면 수용 “불가”입니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*QDktHFAjO3-Z_oSgx4rTbg.gif" /></figure><p>이렇게 받은 응답을 바탕으로 메디콜이 실시간으로 그 결과를 모아 가장 가까운 순서로 병원으로 보여줍니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*7MPW4Z-YsYkZJuSLteF4Lg.gif" /></figure><p>그리고 선택된 병원까지의 네비게이션도 실시간으로 제공합니다.</p><h3>아키텍처</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sJWyT-nT7gtlYUYZXbbvyQ.png" /></figure><p>아키텍쳐에 대해 더 자세히 설명을 드려보겠습니다.<br>먼저, 구급대원이 Flutter 기반 모바일 앱을 통해 환자의 상태와 위치를 입력합니다. 이 정보는 백엔드 서버로 전송되며, 백엔드에서는 인증 처리와 병원 후보군 필터링, 캐싱 및 데이터 저장을 담당합니다.<br>입력된 환자 정보를 바탕으로, AI 서버에서는 Gemini를 활용해 병원에 보낼 음성 메시지를 생성하고, 환자 상태와 구글 맵스에 나오는 진료과를 바탕으로 어떤 병원에 연락을 시도할지 판단합니다.<br>그 다음 단계에서, Twilio API 를 통해 여러 병원에 동시에 자동 전화를 발신합니다. 병원 측에서는 전화를 받고 키패드 1번(수락) 또는 2번(거절)로 응답하게 되고, 이 응답은 다시 서버로 전달됩니다.<br>병원이 서버로 응답을 주면 서버는 곧바로 병원 이름과 위치를 모바일 앱에 전송합니다. 어느 병원으로 갈지 최종 선택하는것은 구급대원이 직접 결정합니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E6oUAWmGftx4WP-w4tJIdw.png" /></figure><p>메디콜의 아이디어는 멀리서 온 것이 아닙니다. 저희 팀원의 어머님께서 실제로 겪으신 불편함에서 출발했습니다.<br>어머님이 환자로 구급차에 타 계셨고, 팀원은 보호자로 함께 타고 있었습니다. 그런데 수용 가능한 병원을 찾는데까지 너무 오랜 시간이 걸렸습니다. 결국 구급차가 여러 병원을 계속 돌아다니고 나서야 겨우 빈 병상이 있는 병원을 찾으실 수 있었습니다</p><p>이 이야기를 들은 저희 팀은 이 문제가 잘만 해결 되면 사회적으로 큰 임팩트를 불러올 것이라는 확신이 들었습니다.. 그리고 곧바로 솔루션 메디콜을 기획하고 MVP를 설계했습니다.</p><p>저희는 이 사례가 단순한 개인적인 일이 아닐까 싶어 현직 의사에게 연락을 해 직접 인터뷰를 진행했습니다. 그 결과, 이 문제가 실제 의료 현장에서도 시급하게 해결이 필요한 심각한 구조적 문제임을 확인할 수 있었습니다.<br>기술은 그 자체로 의미가 있지만, 실제 사용자의 니즈에서 출발하지 않는 기술은 결코 가치 있는 서비스가 될 수 없습니다. 저희는 바로 그 니즈를 찾고 그 안에서 해결책을 만들어 나갔습니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uHPGm3IOByH6rI7yFi0_1A.png" /></figure><p>메디콜은 실제 구급 현장에서 바로 사용할 수 있도록 응급구조사의 사용 흐름에 맞춰 설계되었으며, 단순한 콘셉트가 아닌, AI, 자동 병원 호출, 경로 안내까지 구현된 완성형 MVP입니다.<br>기술적인 세부사항은 시간 관계상 생략하겠지만 관심 있으신 분은 메디콜 공식 홈페이지를 통해 더 자세히 보실 수 있습니다.</p><h4>남은 기간 6주…</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tU-C8UilF-2BaNkvQCYZTA.png" /></figure><p>이렇게 기획을 마치고 남은 시간은 단 6주 밖에 없습니다. 디자인부터 개발까지, 동작하는 MVP를 만들기에는 턱없이 부족한 시간이었습니다.</p><h3>2. 1에서부터 시작하기</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-r5UwU1e4z3VSQUK-pCTJQ.png" /></figure><p>제가 하고 싶은 말 두번째가 여기서 나옵니다. 바로 1에서부터 시작하기입니다<br>그래서 저희 팀은 0에서 시작하지 않았습니다. 저는 프론트엔드 개발 경험은 있었지만, 모바일 앱 개발은 이번이 처음이었습니다. 플러터 강의를 새로 듣거나 배우기에는 시간이 부족했습니다.</p><p>그래서 새로 만들기보다, 이미 잘 만들어진 앱을 먼저 분석하는 데 집중했습니다.<br>‘배달의민족’,과 같은 지도 기반 앱을 사용해보며 사람들이 어떤 흐름으로 앱을 사용하는지, 어떤 UI가 직관적인지 직접 경험했습니다.</p><p>특히, 배달의민족 앱에서 사용되는 ‘내 위치 자동 입력’ 기능에서 역지오코딩 개념을 발견했습니다. 기존처럼 사용자가 직접 주소를 타이핑하지 않아도 자동으로 주소가 입력되게 하면 구급상황에서 더 빠르게 동작할것이라 생각했습니다.</p><p>역지오코딩 기능은 제가 구현해본적이 없었기에 AI의 도움을 받아 구현했습니다. 배달의 민족, 역지오코딩, 그리고 이미지를 넣고 해당 기능을 구현하기 위한 기술과 코드 구조를 설계해주고, 손쉽게 구현해주었습니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*Q2dPNCFa5hoAvJYAhnb50g.gif" /></figure><p>이렇게 역지오코딩을 메디콜에 적용했고, 덕분에 응급상황에서 주소입력을 빠르게 할 수 있는 인터페이스를 갖추게 됐습니다.</p><p>이 과정을 통해 깨달은 건 명확했습니다.</p><p>짧은 시간 안에 성과를 내려면 무조건 처음부터 만들기보다, 이미 검증된 것을 빠르게 가져와 AI와 함께 나만의 방식으로 발전시키는 것이 핵심입니다.</p><h3>기본기는 최소한 쌓고 AI 활용하기</h3><blockquote>그럼 코딩 없이 AI 만으로 MVP를 만들 수 있나요?</blockquote><blockquote>아니요.</blockquote><p>짧은 시간 안에 의미 있는 결과를 내려면, AI의 힘과 기본기가 결합되어야 합니다. AI는 강력한 생성 도구입니다 <br>기본기가 전혀 없는 채로 AI를 다룬다면 랜딩페이지처럼 간단한 프로덕트를 만들 수는 있겠지만 이후부터는 한계가 명확해집니다. 문제를 디버깅하거나 기능을 확장할 때 무엇이 잘못되었는지 파악하지 못하고, AI가 제시하는 코드의 의도를 해석하지 못해 결국 속도와 품질 모두 떨어지게 됩니다. 기본기가 없다면 AI가 만들어주는 결과물은 단순한 복사 붙여넣기에 불과합니다</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IiOFKKEYmA0vAG61fd4zWw.png" /></figure><p>실제로 제가 개발하다가 발생한 문제입니다. 로그인이 안 되는 문제를 해결해달라고 하자 AI는 프로젝트를 통째로 삭제하고 다시 클론하려고 했습니다.</p><p>AI의 의도는 지금까지 로컬에서 발생한 코드 수정과 커밋을 모두 무시하고 원격 저장소에 올라간 코드로 다시 시작하고 싶었던것 같습니다. 그렇지만 그 의도였다면 rm -rf로 통쨰로 삭제하는 것이 아니라 git restore . 혹은 git reset — hard와 같은 명령어를 통해 로컬 변경사항만 제거하고 원격 저장소 상태로 되돌리는 방법이 더 적절했을 것입니다.<br>결론은, AI의 제안이 반드시 최선이거나 안전한 방식이 아닐 수 있으며, 일정 수준의 기본기와 명령어에 대한 이해 없이 그대로 따를 경우 예상치 못한 데이터 손실이나 시간 낭비로 이어질 수 있다는 점입니다. AI는 도구일 뿐이며, 개발자가 그것을 올바르게 해석하고 선택할 수 있어야 합니다</p><h3>자바스크립트 학습에서 확장된 플러터</h3><p>문제 핸들링 이외에도 제가 코드를 이해한 방법에 대해 설명해보겠습니다.<br>저는 프론트엔드 개발자로서 React로 UI 컴포넌트를 다뤄본 경험이 있었기에 기존에 쓰던 방식과 AI가 생성한 Flutter 다트 코드를 비교하며 빠르게 이해하고, 수정하고, 원하는 대로 다듬을 수 있었습니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x6VMeJ8ZCRwNz-H0-uN41Q.png" /></figure><p>왼쪽은 자바스크립트와 스타일 컴포넌트 코드이고 오른쪽은 다트코드입니다.<br>저는 다음과 같은 방식으로 양쪽을 비교하며 다트를 이해했습니다.<br>JS+CSS에서는 styled-components를 사용해 font-size, font-weight, font-family, color 등의 스타일을 선언적으로 작성합니다. Flutter에서는 TextStyle 객체를 사용해 속성을 지정합니다.<br>또한 JS에서는 공간 사이 크기를 조정하는 역할을 div에 height를 주어 구성했다면, Flutter에서는 SizedBox(height)로 동일한 역할을 수행합니다.<br>이처럼 React와 Flutter는 구조적으로 유사했습니다. 둘 다 컴포넌트 기반이며, UI를 코드로 명시적으로 선언한다는 공통점이 있었기에 다트라는 새로운 언어를 배우지 않아도 쉽게 코드를 이해할 수 있었습니다.</p><h3>AI를 활용한 빠른 MVP 검증</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yvOlpJx-y4QQCGbDkLaHnQ.png" /></figure><p>짧은 기간안에 MVP를 만들기 위해서 AI 를 통해 개발 시간을 단축하고 피드백을 받아 반복해서 수정해나가야 했습니다. <br>빠른 반복이 저희의 완성도를 높였습니다 저희는 초기 프로토타입을 만든 뒤, 팀원과 현직 의사의 피드백 바탕으로 바로 수정했습니다<br>기존에는 환자 상태를 입력하는 화면이 지도와 한 화면에 있었다면, 이를 다른 화면으로 분리하여 구급대원들이 더 넓은 화면에서 환자 상태를 입력할 수 있게 했습니다</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*O5CugwSMTBgCyI8bsl13cw.png" /></figure><p>그리고 나서 환자의 상태를 빠르게 입력할 수 있도록 Quick Symotoms라는 해시태그를 생성하여 자주 발생하는 환자 상태를 간편하게 버튼형식으로 간단하게 입력할 수 있게 수정하였고요. AI가 코드를 빠르게 생성하고 수정해주면서, 사용자 중심의 개선이 가속화되었습니다. 짧은 시간 안에 성과를 내려면 무조건 처음부터 만들기보다, 이미 검증된 것을 빠르게 가져와 AI와 함께 나만의 방식으로 발전시키고, 피드백은 사용자로부터 받아 빠르게 고도화 하는 것이 핵심입니다.</p><h3>4. 간절하다면 디테일 하나까지 신경쓰기</h3><p>마지막으로 말씀드리고 싶은 것은 디테일 입니다. <br>Top 10에 들어 본선만 남겨두고 있을때, 어떤 방식으로 본선이 진행되는지 안내가 늦게 나왔습니다<br>본선이 부스 운영이라는 사실을 5일 전에 안내 받았죠. 이는 주말을 포함하여 5일이었기 때문에 저희가 할 수 있는 일은 많지 않았습니다</p><p>제한된 공간 안에서 Top 10 팀의 부스가 있을때, 모든 심사위원이 모든 부스를 방문할 것이라고 기대하지 않았습니다. <br>여러분들께 여쭤보고 싶습니다. “1주일 안에 부스를 준비해야 한다면, 여러분은 어떤 전략을 세우시겠습니까? 개발 고도화라고 생각하실 수도 있도, 디자인 개선이라고 하실 수도 있습니다. 하지만 저희 팀은 배너를 만들었습니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vgqoNDRVM-Y_zJe6JpTGhA.png" /></figure><p>제가 앞서 주제에서 심사위원의 이목을 끌지 못하면 서비스를 보여줄 기회가 없다고 했습니다<br>현장도 동일합니다<br>현장에서 이목을 끌지 못하면 저희의 서비스를 보여줄 기회가 없습니다. <br>그래서 저는 급하게 배너를 디자인했습니다. <br>디자인을 마치고 당일 제작이 되는 것을 찾아 주문을 한뒤 월요일에 수령했습니다. <br>그리고 이를 들고 화요일 새벽 비행기에 탑승했습니다. <br>이를 통해 성공적으로 마닐라 부스에 배너를 가져갈 수 있었습니다.</p><h3>영어 발표 준비</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/658/0*ygm5akeSHdpG4JPG" /></figure><p>그리고 행사가 모두 영어로 진행되기 때문에 영어 발표에 나머지 힘을 쏟았습니다.<br>영어가 개발자의 필수 덕목이라고 하지만 외국에서 영어로 발표를 하고 질문에 대한 답을 하는 것은 쉽지 않은 일입니다. <br>그래서 저희는 1분 분량으로 솔루션을 소개하는 영어 발표를 준비하고 예상 질문에 대한 답변도 준비했습니다. <br>마닐라로 가는 비행기 안에서도 팀원들을 채찍질 하면서 영어 대본을 암기하게 시켰습니다.</p><p>경쟁력은 이런 ‘디테일’에서 나왔습니다. 저희는 붉은 배너, 기억에 남는 팀명 ‘Atempo’, 영어 발표로 글로벌 심사위원에게 어필했습니다.</p><p>특히 빨간 배너는 주목성과 설명 효율을 동시에 잡는 전략이었습니다.</p><p>이번 대회를 위해 배너를 만든팀은 저희 밖에 없었고 이는 본선 당일에 시각적으로도 차별화되었으며, 배너에 프린트 된 앱 화면을 이용해 서비스 설명을 쉽게 할 수 있었습니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E-OmC0Yq6vASRz5miHKvBg.png" /></figure><p>마지막으로, 어디에서도 공유하지 않았던 실전 팁 하나를 소개합니다. 바로 팀명을 A로 시작하는 단어로 짓는 것입니다.<br>저는 작년에 구글 솔루션 챌린지에서 Top 100에 선정된 경험이 있습니다. 하지만 당시 팀명은 ‘Glow Alarm’이었고, 알파벳 G로 시작했기 때문에 수상자 목록에서도 중간쯤에 위치해 시각적으로 눈에 띄지 않았습니다.<br>구글은 공식적으로 순위를 매기지 않지만, 리스트나 발표 순서를 정할 때 알파벳 순 정렬을 자주 사용합니다. 이번 대회에서도 마찬가지일 것이라 판단했고, 현장 발표나 부스 운영에서도 가장 먼저 소개되는 팀이 상대적으로 더 주목받는다고 생각했습니다.<br>그래서 저희는 의도적으로 A로 시작하는 단어 중에서 팀명을 선택했고, 그 결과 수상자 목록에서 가장 위, 첫 번째에 이름을 올릴 수 있었습니다. 작은 디테일이지만, 이런 전략적 선택이 실제로 주목도를 높이는 데 도움이 되었습니다.</p><blockquote>주제 선정에 80%이상 신경쓰기<br>1에서 부터 시작하기<br>기본기는 최소한 쌓고 AI 활용하기<br>간절하다면 디테일 하나까지 신경 쓰기</blockquote><p>이 네가지 강점 덕분에 저희는 솔루션 챌린지에서 Top 3안에 들었습니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HaMoDh7I0_vgIaszS0yp0w.png" /></figure><p>수상 이후, 제 삶은 생각보다 훨씬 더 크게 변화했습니다. 상 하나 받았을 뿐인데, 정말 많은 일이 생겼습니다.<br>마닐라 본선에서는 단순히 ‘상 받은 사람’이라는 이유만으로 발표 직후에 현지 사람들과 사진을 찍자는 요청이 끊이지 않았고, 한국으로 돌아와서는 인터뷰 요청, 해커톤 멘토 초청, 그리고 다양한 사람들과의 연결이 자연스럽게 이어졌습니다.<br>구글 코리아 김경훈 사장님이 직접 링크드인에 축하 글을 올려주신것 부터 시작해 다양한 언론사와 인터뷰, 심지어 해커톤 멘토링 요청까지 왔습니다.<br>이 대회는 그저 상 하나를 주는 자리가 아니었습니다. 저에게는 새로운 사람들과 기회를 연결해주는 지름길이 되어주었습니다. 상을 목표로 시작했지만, 상은 오히려 시작에 불과했습니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q4B8tjXzRST1rJEf-E4ARg.png" /></figure><p>그리고 사실, 앞에서 말씀드리지 못했던 중요한 이야기가 하나 있습니다.<br>저는 이 메디콜이라는 서비스를 개발하면서 서비스 자체가 정말 마음에 들었습니다. 이 서비스는 단순히 대회를 위한 프로젝트가 아니라, 사람들의 생명을 살릴 수 있다는 가능성을 보았습니다. <br>그래서 대회 기간 중에도 창업 경진대회에 도전했고, 합격하여 넓은 사무실까지 지원받았습니다. 그렇게 탄생한 것이 지금 제가 대표로 있는 다이스랩입니다.</p><p>스타트업의 발판</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JQV0F89uqfzxxDJmcXdEmQ.png" /></figure><p>바로 중앙응급의료센터에서 저희에게 먼저 연락을 주셨습니다.<br>중앙응급의료센터는 보건복지부 산하의 기관으로, 대한민국의 응급의료 정책을 수립하고 시스템을 관리하는 핵심 행정 기관입니다.<br>실제로 저희가 메디콜 서비스를 설계할 때, ‘사람들이 일일이 전화를 걸어 응급실을 매칭해주는 중앙응급의료센터’라는 국가에서 운영 중인 시스템을 분석하며<br> ‘이걸 어떻게 대체할 수 있을까?’라는 문제의식에서 출발했는데, 아이러니하게도 그 시스템을 만든 주체인 국립중앙의료원에서 저희의 뉴스기사를 보고 저희에게 먼저 연락을 주신 겁니다.<br>중앙응급의료센터는 저희에게 응급의료 세미나에서 메디콜을 공식적으로 발표해달라고 제안했습니다.<br>그리고 응급센터 관계자들과 함께 이 기술이 실제 의료 현장에서 어떻게 실적용할 수 있는지, 제도와 시스템 안에 어떻게 연동할 수 있을지 함께 논의하고 싶다고 말이죠.<br>이 소식을 들었을 때, 저희 팀은 굉장히 벅찬 감정을 느꼈습니다.<br>단순히 수상만으로 끝나는 프로젝트가 아니라, 이제는 국가 의료 시스템을 움직이는 기관과 함께, 실질적 정책과 제도의 변화에 기여할 수 있는 가능성이 열린 것입니다.<br>저희는 이 기회를 시작으로, 진짜 세상을 바꾸는 기술이 되기 위해 더 철저히 준비하고, 더 겸손하게 협업해 나갈 계획입니다.<br> 이렇게 구글 솔루션 챌린지 Top 3라는 눈에 보이는 성과는 병원과 투자자, 그리고 사회와 신뢰를 쌓는 데 큰 도움이 되었습니다.<br>이런 변화는 단숨에 찾아온 것이 아닙니다.</p><h3>평범했던 학생이 큰 임팩트를 만들 수 있던 비결</h3><p>저도 처음부터 뭔가 특별한 사람이 아니었습니다.<br> GDG on Campus에 들어가기 전, 저는 1학년 1학기만 마친 새내기였습니다.<br>프론트엔드와 백엔드라는 용어조차 모를 정도로 평범한 컴퓨터공학부 학생이었습니다.<br>하지만 실력보다는 열정과 가능성을 믿고 받아준 GDG on Campus 덕분에 인사이트를 넓히고 다양한 분야에 본격적으로 시작될 수 있었습니다.<br>그곳에서 저는 다양한 사람들과 교류하고, 도전의 기회를 얻고, 끊임없이 자극을 받았습니다. 결국, 그 경험들이 쌓여 솔루션 챌린지 Top 3라는 성과로 이어졌습니다.<br>저에게 GDG on Campus는 단순한 커뮤니티를 넘어 인생을 바꿔준 시작점이었습니다.</p><h3>GDG on Campus, Google Developer Group</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gz6vGWYBSazOQC6RJF5gxw.png" /></figure><p>혹시 여러분도 지금 대학생이라면, 여러분의 학교에도 GDG on Campus가 있을 수 있습니다. 곧 모집이 열리니까 꼭 도전해보시길 바랍니다.<br>그리고 만약 아직 없다면, 오히려 그게 더 좋은 기회일 수도 있습니다. 바로 여러분이 GDG on Campus의 첫 번째 리드가 되어 시작할 수 있기 때문입니다. 대학생이 아니신 분들은 지역마다 있는 구글 디벨로퍼 그룹에 가입하실 수 있습니다. 자세한 내용은 공식 홈페이지에서 확인하실 수 있습니다.</p><p>연락처</p><p>clicelee@dycelab.xyz<br><a href="http://threads.com/@clicelee"> @clicelee</a></p><p>솔루션 챌린지나 이 글에 관해서 궁금한게 있으시다면 언제든지 답변 해드리겠습니다 :)<br>감사합니다.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50fde03e5c36" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fixing Multilingual Anchor Issues in VitePress with a Single Function`slugify`]]></title>
            <link>https://medium.com/@cliceleee/fixing-multilingual-anchor-issues-in-vitepress-with-a-single-function-slugify-aacea67138af?source=rss-27691f55523b------2</link>
            <guid isPermaLink="false">https://medium.com/p/aacea67138af</guid>
            <category><![CDATA[hash]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[url]]></category>
            <category><![CDATA[anchor]]></category>
            <category><![CDATA[slugify]]></category>
            <dc:creator><![CDATA[clice]]></dc:creator>
            <pubDate>Mon, 17 Feb 2025 14:19:11 GMT</pubDate>
            <atom:updated>2025-02-22T13:53:09.617Z</atom:updated>
            <content:encoded><![CDATA[<p>my first significant open source contribution</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r54bx9Z7SyVdzMuR6yw8gw.png" /></figure><p><a href="https://toss.im/">Toss</a> recently released <a href="https://frontend-fundamentals.com/en/">Frontend Fundamentals</a> as a guideline for writing high-quality frontend code. It serves as a <strong>compass</strong> for frontend developers, introducing four core principles of good code along with practical examples and solutions.</p><p>Additionaly, it was built using <strong>VitePress</strong>.</p><h3>🚀 The Problem</h3><p>When navigating through a <strong>VitePress-powered</strong> documentation, clicking a table of contents (TOC) entry appends a corresponding anchor hash to the URL, allowing users to jump directly to a section of the page.</p><p>For example, in the documentation, a section titled <strong>“📝 Code Example”</strong> would result in the following URLs:</p><p>🔗 <strong>English Document:</strong><br><a href="https://frontend-fundamentals.com/en/code/examples/submit-button.html#%F0%9F%93%9D-code-example">https://frontend-fundamentals.com/en/code/examples/submit-button.html#📝-code-example</a></p><p>🔗 <strong>Korean Document:</strong><br>https://frontend-fundamentals.com/ko/code/examples/submit-button.html#📝-코드-예시</p><p>🔗 <strong>Japanese Document:</strong><br><a href="https://frontend-fundamentals.com/ja/code/examples/submit-button.html#%F0%9F%93%9D-%E3%82%B3%E3%83%BC%E3%83%89%E4%BE%8B">https://frontend-fundamentals.com/ja/code/examples/submit-button.html#📝-コード例</a></p><p>However, when switching to another language, such as <strong>Japanese (</strong><strong>ja)</strong> or <strong>Chinese (</strong><strong>zh-hans)</strong>, only the <strong>folder-based route</strong> changes, but the <strong>hash remains the same</strong>. This leads to an issue where the browser <strong>fails to navigate</strong> to the correct section and instead reloads at the top of the page.</p><p>🔗 <strong>Incorrect behavior after switching languages:</strong><br><a href="https://frontend-fundamentals.com/ja/code/examples/submit-button.html#%F0%9F%93%9D-code-example">https://frontend-fundamentals.com/ja/code/examples/submit-button.html#📝-code-example</a><br><a href="https://frontend-fundamentals.com/ch/code/examples/submit-button.html#%F0%9F%93%9D-code-example">https://frontend-fundamentals.com/ch/code/examples/submit-button.html#📝-code-example</a></p><p><strong>Can you catch the problem?</strong><br>Since the <strong>English hash (</strong><strong>#📝-code-example)</strong> is not recognized in other languages, the browser <strong>fails to scroll to the intended section</strong>.</p><p>The expected behavior is that the <strong>anchor hash should change dynamically</strong> to match the localized title.</p><h3>🔍 Investigating the Issue</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4xnE2mt0BprixoBbi-sn7g.png" /><figcaption><a href="https://vitepress.dev/guide/markdown#header-anchors">https://vitepress.dev/guide/markdown#header-anchors</a></figcaption></figure><p>Upon reviewing the <a href="https://vitepress.dev/guide/markdown#header-anchors">VitePress documentation on header anchors</a>, I discovered a built-in solution:<br> Manually defining anchor names using {#anchor-name} syntax.</p><p>By explicitly specifying the anchor name for each section, regardless of the language, the issue could theoretically be resolved:</p><pre>## 코드 예시 {#code-example}<br>## 代码示例 {#code-example}<br>## Code Example {#code-example}</pre><p>With this approach, all translations of the same section would share a <strong>unified hash (</strong><strong>#code-example)</strong>, ensuring seamless navigation when switching languages:</p><p>✅ <strong>https://example.com/en/#code-example</strong><br>✅ <a href="https://link.com/ko/#code-example"><strong>https://example.com/ko/#code-example</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ISpgiGs0nuwqs-bzt5wxqA.png" /></figure><p>This method is even applied on the <strong>official</strong> <a href="https://vitepress.dev/">VitePress documentation</a>.</p><p>However, this solution introduced a major drawback.</p><p>Given that the documentation contained <strong>hundreds of headers</strong> across <strong>multiple pages and languages</strong>, <strong>manually defining </strong><strong>{#anchor-name} for every single header</strong> would be:<br> ❌ <strong>Tedious</strong><br> ❌ <strong>Error-prone</strong><br> ❌ <strong>Difficult to maintain</strong></p><p>A more <strong>scalable</strong> and <strong>automated</strong> approach was necessary.</p><h3>🛠 Implementing a slugify Function</h3><p>To dynamically generate <strong>consistent</strong> anchor hashes, I implemented a slugify function.<br> The goal was to ensure <strong>unified</strong> header mappings across all languages while keeping <strong>English</strong> as the reference anchor.</p><h3>The solution was structured as follows:</h3><h3>1️⃣ Strip Emojis &amp; Normalize Text</h3><p>Since many headers contained <strong>emojis</strong> (✏️, 📝), they needed to be removed to prevent unnecessary noise in the hash.</p><h3>2️⃣ Check for Predefined Mappings (titleMap)</h3><p>Instead of relying on VitePress’s <strong>default slug generation</strong>, I introduced a predefined <strong>mapping object (</strong><strong>titleMap)</strong>.</p><ul><li>If an <strong>exact match</strong> for a <strong>non-English</strong> header was found in titleMap, the <strong>corresponding English hash</strong> was used.</li></ul><h3>3️⃣ Apply Slugification</h3><p>If no <strong>exact</strong> match was found, the text was <strong>converted</strong> into a <strong>URL-friendly</strong> format by:<br> ✔ <strong>Removing special characters</strong><br> ✔ <strong>Converting spaces to hyphens</strong><br> ✔ <strong>Converting text to lowercase</strong></p><h3>🔧 Here’s the Implementation of the slugify Function</h3><pre>const slugify = (str) =&gt; {<br>  // 1. Remove emojis<br>  let cleanedStr = str<br>    .normalize(&quot;NFKC&quot;)<br>    .replace(/[\p{Emoji_Presentation}\p{Extended_Pictographic}]/gu, &quot;&quot;)<br>    .trim();<br>// 2. Check for an exact match in titleMap<br>  if (titleMap[cleanedStr]) {<br>    return titleMap[cleanedStr];<br>  }<br>  // 3. Find the longest partial match in titleMap<br>  let matchedKey = Object.keys(titleMap)<br>    .filter((key) =&gt; cleanedStr.includes(key))<br>    .sort((a, b) =&gt; b.length - a.length)[0];<br>  if (matchedKey) {<br>    return titleMap[matchedKey];<br>  }<br>  // 4. Apply general slug conversion<br>  let slug = cleanedStr<br>    .trim()<br>    .toLowerCase()<br>    .replace(/[^\w가-힣0-9\s-]/g, &quot;&quot;)<br>    .replace(/\s+/g, &quot;-&quot;)<br>    .replace(/^-+/, &quot;&quot;); // Remove leading hyphen if present<br>  return slug ;<br>};</pre><h3>🔬 Results &amp; Impact</h3><p>After implementing slugify, anchor hashes across all languages were <strong>unified</strong> under a <strong>single system</strong>, significantly improving the user experience.</p><p>✅ <strong>Language switching now preserves the correct scroll position</strong><br> ✅ <strong>The URL hash updates dynamically based on the selected language</strong><br> ✅ <strong>No need to manually specify </strong><strong>{#anchor-name} in markdown files</strong></p><p>Now, clicking a <strong>TOC entry</strong> in <strong>any language</strong> correctly maps to a <strong>unified hash</strong>, ensuring <strong>seamless navigation</strong>:</p><h3>Before (❌ Inconsistent hash, incorrect behavior)</h3><pre>https://example.com/en/#code-example<br>https://example.com/ko/#📝-코드-예시 ❌<br>https://example.com/ch/#📝-代码示例 ❌</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*NuUm5TDm7cCMoyWZANn7jw.gif" /><figcaption>When switching to another language, the hash value does not change, which results in incorrect navigation.<br>Since the hash remains the same across all languages, the browser does not navigate to the correct section and instead moves to the top of the page.</figcaption></figure><h3>After (✅ Consistent hash, correct behavior)</h3><pre>https://example.com/en/#code-example<br>https://example.com/ko/#code-example ✅<br>https://example.com/ch/#code-example ✅</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*-oft1N2mFL1NSXzSYu70dw.gif" /><figcaption>When switching between languages, users can stay on the correct section instead of being sent to the top of the page</figcaption></figure><h3>📌 Key Takeaways</h3><p>✔ <strong>Manually assigning </strong><strong>{#anchor-name} is a viable but tedious solution</strong><br> ✔ <strong>A </strong><strong>slugify function automates this process, ensuring consistency and scalability</strong><br> ✔ <strong>Predefined mappings (</strong><strong>titleMap) allow handling variations in headers</strong><br> ✔ <strong>Removing emojis and normalizing text prevents unnecessary URL noise</strong><br> ✔ <strong>Edge cases (empty slugs) must be handled gracefully</strong></p><p>This approach not only <strong>streamlined documentation maintenance</strong> but also <strong>eliminated a major UX issue</strong> in navigating <strong>multilingual</strong> content in VitePress.</p><h3>✨ Final Thoughts</h3><p>Fixing <strong>anchor inconsistencies</strong> in <strong>multilingual VitePress documentation</strong> required both <strong>understanding markdown anchors</strong> and <strong>implementing a robust slugification strategy</strong>.</p><p>This solution provided a <strong>clean, scalable, and automatic</strong> way to ensure that navigation across <strong>different languages</strong> remained seamless.</p><p>If working with <strong>multilingual documentation</strong>, <strong>consider automating slug generation</strong> instead of manually defining anchors.<br> It saves <strong>time</strong>, <strong>reduces errors</strong>, and <strong>enhances user experience</strong>. 🚀</p><p>💡 <strong>Check out my PR here, you can compare the improvement with videos:</strong><br> 🔗 <a href="https://github.com/toss/frontend-fundamentals/pull/160">https://github.com/toss/frontend-fundamentals/pull/160</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aacea67138af" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Brendan Eich Stepped Down as CEO of Mozilla in Just 2 Months]]></title>
            <link>https://medium.com/@cliceleee/why-eich-stepped-down-as-ceo-of-mozilla-in-just-2-months-224367627377?source=rss-27691f55523b------2</link>
            <guid isPermaLink="false">https://medium.com/p/224367627377</guid>
            <category><![CDATA[brave-browser]]></category>
            <category><![CDATA[brendan-eich]]></category>
            <category><![CDATA[kent-beck]]></category>
            <category><![CDATA[mozilla]]></category>
            <category><![CDATA[leaders]]></category>
            <dc:creator><![CDATA[clice]]></dc:creator>
            <pubDate>Tue, 28 Jan 2025 08:11:57 GMT</pubDate>
            <atom:updated>2025-01-28T09:42:42.366Z</atom:updated>
            <content:encoded><![CDATA[<p>The Qualities a Leader Needs</p><p>Yesterday, I was<a href="https://medium.com/@cliceleee/why-brendan-eich-regretted-the-with-statement-in-javascript-ee1487e28611"> writing about Brendan Eich</a> and became curious about <a href="https://en.wikipedia.org/wiki/Brendan_Eich">his</a> career path. A quick look at his <a href="https://www.linkedin.com/in/brendaneich/">LinkedIn profile</a> revealed something quite interesting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cELcBPGVZhDXV8G6jWxZVw.png" /></figure><p>As a creator, father of Javascript, he was promoted to CEO of Mozilla — only to step down after just two months on April, 2014.</p><h3>So, what exactly happened in 2014?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LjJxfpGzLMo_qdjQIzhupQ.png" /><figcaption><a href="https://www.thepinknews.com/2012/04/04/javascript-inventor-gave-1000-to-support-californias-gay-marriage-ban/">https://www.thepinknews.com/2012/04/04/javascript-inventor-gave-1000-to-support-californias-gay-marriage-ban/</a></figcaption></figure><p>It all began when the public learned that Eich had donated $1,000 to support <a href="https://en.wikipedia.org/wiki/2008_California_Proposition_8">California’s Proposition </a>8, a campaign against same-sex marriage. At the time, the LGBTQ+ community and its allies viewed this stance as incompatible with the values of a leader at Mozilla, a company known for promoting openness and inclusivity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8KjWGB7MBHiAOlD5keJ8-w.png" /></figure><p>Consequently, Eich faced intense criticism and questions about his suitability to serve as CEO, ultimately leading to his resignation.</p><h3>Kent Beck’s Perspective</h3><p><strong>Kent Beck</strong>, author of ‘TDD by example’ and ‘Tidy First’, wrote an article titled <a href="https://medium.com/@kentbeck/53491d6d36b7"><em>A Twist on Brendan Eich and Mozilla</em></a>, published on April 6, 2014, just a few days before his resignation.</p><p>In his piece, Beck does not explicitly state his own final opinion on Eich’s departure. Instead, he poses two key questions to readers, prompting them to consider the delicate balance between freedom of expression and the social responsibility of high-profile leaders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BqrJOmMusqO1OhrUemFgCA.png" /></figure><h3>After Mozilla</h3><p>Eich’s term as CEO ended around April 2014, and one could argue it turned out for the good choice— he went on to create Brave Software, known for the best privacy-focused web browser.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5VT35txRqFWWUcXdiLgKEg.png" /></figure><p>However, it seems he still cannot fully shake the “homophobic” label; even within the Brave community, there are <a href="https://community.brave.com/t/brave-needs-to-address-brendan-eich/281044">posts</a> that criticize him for the past donation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M9mIPDOavGTCWLftw8ObpQ.png" /></figure><h3>Freedom of Expression vs. Social Responsibility</h3><p>I’m not here to pass judgment on whether Eich’s critics were justified in their condemnation. As <a href="https://medium.com/@kentbeck/a-twist-on-brendan-eich-and-mozilla-53491d6d36b7">Kent Beck mentions</a>, there is a perennial conflict between an individual’s right to free expression and the responsibility they bear, especially when that individual holds a position of leadership. Our words and beliefs can come back to haunt us if we aspire to roles that carry significant influence.</p><p>That being said, I do not oppose freedom of expression. Rather, I believe that if you speak publicly or take a controversial stance, you should be prepared to stand by your words — and accept the consequences. It’s one of the essential qualities of a leader to exercise caution in communication, ensuring that personal opinions do not undermine an organization’s mission or values.</p><h3>Final Thoughts</h3><p>Brendan Eich’s brief tenure as Mozilla CEO serves as a reminder that leaders must align with the values of the communities they serve. Freedom of expression is important, but so is the impact that expressions of personal belief can have on an organization’s overall culture and public image. If you aim to be a person of influence, consider both what you say and how you say it — words carry weight, and sometimes the consequences reach further than you might ever expect.</p><p>How do you view the balance between personal beliefs and leadership responsibilities? I’m curious to hear your perspective. Feel free to share your thoughts below.</p><p>Here’s a link you might find interesting to read.</p><p><a href="https://tim.dreamwidth.org/1844711.html">https://tim.dreamwidth.org/1844711.html</a></p><p><a href="https://tim.dreamwidth.org/1852118.html">https://tim.dreamwidth.org/1852118.html</a></p><p><a href="https://modelviewculture.com/pieces/killing-the-messenger-at-mozilla">https://modelviewculture.com/pieces/killing-the-messenger-at-mozilla</a></p><p>written by @clicelee</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=224367627377" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Brendan Eich Regretted the `with` Statement in Javascript]]></title>
            <link>https://medium.com/@cliceleee/why-brendan-eich-regretted-the-with-statement-in-javascript-ee1487e28611?source=rss-27691f55523b------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee1487e28611</guid>
            <category><![CDATA[mdn]]></category>
            <category><![CDATA[with]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[statement]]></category>
            <dc:creator><![CDATA[clice]]></dc:creator>
            <pubDate>Mon, 27 Jan 2025 14:55:41 GMT</pubDate>
            <atom:updated>2025-01-28T10:10:55.543Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vgiPeSu_bZkNLszgBoIw1A.png" /></figure><p>This article is came up during JS study conversation.</p><p>I’m a Core member in GDG on Campus Konkuk University, and we are running a <a href="https://github.com/gdsc-konkuk/24-25-study-js-deep-dive">discussion-based JS study group.</a></p><p>We talked about strict mode and with and this article can be the conclusion of our discussion and may state the key point.</p><p>You can chek our previous conversation about strict mode and with in <a href="https://github.com/gdsc-konkuk/24-25-study-js-deep-dive/pull/15#discussion_r1921082193">this link</a></p><h4>A Brief Overview of ‘with’</h4><p>The withstatement was introduced in JavaScript to make working with object properties easier. By using with, developers could access an object’s properties without repeatedly referencing the object itself. For example:</p><pre>const obj = { a: 1, b: 2 };<br>with (obj) {<br>  console.log(a + b); // 3<br>}</pre><p>At first glance, this seems convenient. However, the withstatement quickly proved to be problematic due to the ambiguity and bugs it introduced.</p><h4>Why Was `with` Eliminated?</h4><p>The with statement was officially forbidden in strict mode starting with ECMAScript 5 (ES5) and is strongly discouraged in modern JavaScript. According to MDN, the use of withis not recommended for several reasons:</p><ul><li><strong>Ambiguity</strong>: The scope resolution within ‘with’ is unpredictable. For instance:</li></ul><pre>const obj = { a: 1 }; let a = 10; <br>with (obj) {   <br>  console.log(a); // Is this obj.a or the outer variable a? <br>}</pre><ul><li>This kind of ambiguity can lead to confusing bugs, making code harder to understand and maintain.</li><li><strong>Performance Issues</strong>: The withstatement hinders optimization by JavaScript engines. Since the scope chain becomes dynamic, engines cannot predict or optimize the code efficiently.</li><li><strong>Strict Mode</strong>: In ES5’s strict mode, ‘with’ is outright forbidden as it conflicts with the goals of predictability and error reduction.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2jkjwpvjsQOIXKG9r2YmxA.png" /><figcaption>MDN Docs</figcaption></figure><p><a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/with">MDN </a>says, use of the with statement is not recommended, as it may be the source of confusing bugs and compatibility issues, makes optimization impossible, and is forbidden in <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Strict_mode">strict mode</a>. The recommended alternative is to assign the object whose properties you want to access to a temporary variable.</p><h3>But WHY?</h3><p>I was so curious because expandability of with seems great. I couldn’t understand <em>WHY</em>.</p><p>Is that the only reason to delete it?</p><p>Even <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/eval">eval()</a> can be used in the browser and didn’t be removed,but…. why with has been ‘removed’?</p><p>For more search, I found a funny debate about with.</p><p>ES Discuss:<a href="https://esdiscuss.org/topic/array-prototype-values-compatibility-hazard"> Array prototype values compatibility hazard</a></p><p>We can check the debate of error which with occured.</p><p>Even Brendan Eich acknowledged the issues with ‘with’, stating that it was a mistake to include it in the language. During discussions in the JavaScript community (notably on the ES Discuss mailing list), developers highlighted the compatibility hazards and potential pitfalls of using ‘with’. The ‘with’ statement was widely used at the time, but its risks outweighed its benefits.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qP948ejzZ0L6uuoZ" /></figure><p>This conversatin is interesting because while the conversation was held, with was used by developers widely(I guess). The truth is during the conversation, with was not eliminated.</p><h4>Alternatives to `with`</h4><p>While the with statement has been eliminated, its intended functionality can still be achieved using safer and more predictable approaches. The recommended alternative is to use temporary variables to access object properties:</p><pre>const obj = { a: 1, b: 2 };<br>const { a, b } = obj;<br>console.log(a + b); // 3</pre><p>This method ensures clarity and avoids the ambiguity that ‘with’ introduces. Modern JavaScript features, such as destructuring assignment, provide concise and elegant ways to work with objects without compromising readability or performance.</p><h4>Why Not Eliminate `eval()`?</h4><p>A common question is why eval() — another controversial feature — was not removed, while with was effectively deprecated. The key difference lies in their use cases. Although ‘eval()’ can be misused, it also has legitimate applications, such as dynamic code execution in specific scenarios. On the other hand, the downsides of ‘with’ far outweighed its benefits, making its removal a more straightforward decision.</p><p>If JS doesn’t delete with , it may occur vicious circle.</p><p>People may mourn the elimation of with .</p><h4>Conclusion</h4><p>The elimination of ‘with’ from JavaScript marked a significant step toward a more predictable and optimized language. Although some developers might mourn its loss, its absence has ultimately led to clearer, more maintainable code.</p><p>I’d love to hear your thoughts on this topic. Do you agree with the decision to eliminate ‘with’? Let’s discuss! Thank you for reading my article. Feel free to share your feedback or insights.</p><p>Written by @clicelee</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee1487e28611" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Viewing xkcd Comics as ASCII Art Whenever You Open the Terminal]]></title>
            <link>https://medium.com/@cliceleee/viewing-xkcd-comics-as-ascii-art-whenever-you-open-the-terminal-cbab8750565d?source=rss-27691f55523b------2</link>
            <guid isPermaLink="false">https://medium.com/p/cbab8750565d</guid>
            <category><![CDATA[shell-script]]></category>
            <category><![CDATA[ascii-art]]></category>
            <category><![CDATA[xkcd]]></category>
            <dc:creator><![CDATA[clice]]></dc:creator>
            <pubDate>Sun, 26 Jan 2025 11:30:19 GMT</pubDate>
            <atom:updated>2025-01-26T11:35:35.358Z</atom:updated>
            <content:encoded><![CDATA[<p>realizing a childhood dream…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NiT59af86WBqgurN.jpg" /></figure><p>When I was young, I really loved a book called <em>What If?</em> by Randall Munroe. While I usually borrowed books from the library, this one was special — I bought it with my own money and kept it as part of my collection.</p><p>After discovering that the author uploads webcomics on the xkcd website daily, I started visiting the website regularly to enjoy his comics.</p><p>Years passed, and I became a computer science student. Eventually, due to laziness, I rarely visit xkcd as frequently. One day, I thought:</p><h3>“What if I could see the daily xkcd comic as ASCII art whenever I open my terminal?”</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2WCrPfioUEiwIB4k.png" /></figure><p>I was already using <a href="https://github.com/dylanaraps/neofetch">neofetch</a>, and neofetch uses ASCII art to display logos (like the Apple logo). That inspired me to do the same with the xkcd comic.</p><h3>So I started a project to fetch the latest xkcd comic and display it in ASCII art whenever I open my terminal.</h3><h3>Plan</h3><p>Here’s how I planned the implementation, taking hints from neofetch:</p><ol><li>Access <a href="https://xkcd.com/">https://xkcd.com/</a>.</li><li>Download the comic image from its URL.</li><li>Convert the image to ASCII art.</li><li>Display the ASCII art every time I open the terminal.</li></ol><p>Let’s make it happen.</p><h3>0. Creating a Rough Outline for the Project</h3><p><em>(Setting up the basic structure.)</em></p><h3>1. Accessing <a href="https://xkcd.com/">https://xkcd.com</a></h3><pre>BASE_URL=&quot;https://xkcd.com/&quot;<br>HTML_CONTENT=$(curl -s &quot;$BASE_URL&quot;)</pre><h3>2. Downloading the Image from Its URL</h3><p>When you visit the xkcd homepage, you can see the comic displayed, and you can find the image URL in the format https://imgs.xkcd.com/comics/[comic_name] near the bottom.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fLsrqjEHbd7XwGvK.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yURmQx1gSO2vpO3Q.png" /></figure><p>We read through the HTML content and use a regular expression to extract that URL:</p><pre>IMAGE_URL=$(echo &quot;$HTML_CONTENT&quot; | grep -o &#39;&lt;meta property=&quot;og:image&quot; content=&quot;[^&quot;]*&quot;&#39; | sed -E &#39;s/&lt;meta property=&quot;og:image&quot; content=&quot;([^&quot;]*)&quot;/\1/&#39;)</pre><p>Then, before converting the image, we save it temporarily in a folder:</p><pre>TEMP_IMAGE=&quot;/tmp/xkcd_comic.png&quot;<br>curl -s &quot;$IMAGE_URL&quot; -o &quot;$TEMP_IMAGE&quot;</pre><h3>3. Converting the Image to ASCII Art</h3><p>This was the most time-consuming part. We want to display ASCII art directly in the terminal, and I tried out various tools for this.</p><h3>Selecting Tools</h3><p>(Discussion about different tools to generate ASCII art.)</p><h3>Properly Converting the Comic into ASCII Art</h3><p>xkcd Comic is formatted like typical comics, it has letters. Converting it to ASCII art using @#+= seems bad idea. Because it cannot express letters completely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Gre1RcGskABJQTU2.png" /></figure><p>Let’s use dot only.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VxFpBwP7GoH5zsk3.png" /><figcaption>much better</figcaption></figure><h3>Review</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rmSh_rtCPBLOLobH.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mLAOd9T0LpHbDwF1A7niiA.png" /></figure><h3>Conclusion</h3><p>Actually, I had been thinking about this project for quite a while, but never started it because of laziness and feeling like I wasn’t skilled enough. However, during [COMMIT: How Are Senior Developers Different From Junior Developers], an event by Goorm, Park Sojin(raon0211) from Toss shared some insights that resonated with me deeply. As soon as I got back home at 11 PM, I started to work, and ended by 3 AM. Actions speak louder than words.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/0*jtX-M6yPCSaHHKyl.png" /><figcaption>ended up at 2:50 am</figcaption></figure><p>If you run into any issues, feel free to leave a comment, open an issue, or submit a PR:</p><p><a href="https://github.com/clicelee/xkcd-ascii-viewer">https://github.com/clicelee/xkcd-ascii-viewe</a>r</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cbab8750565d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>