<?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 Juhee Kang on Medium]]></title>
        <description><![CDATA[Stories by Juhee Kang on Medium]]></description>
        <link>https://medium.com/@juhee.kahng?source=rss-cfadba2ae589------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*T-JT1ZJasBYQVX6dsvL0pw.png</url>
            <title>Stories by Juhee Kang on Medium</title>
            <link>https://medium.com/@juhee.kahng?source=rss-cfadba2ae589------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 22:07:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@juhee.kahng/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[Taking the First Step at Open-Source Contribution]]></title>
            <link>https://medium.com/juhee-kahng/taking-the-first-step-at-open-source-contribution-906dcd569ede?source=rss-cfadba2ae589------2</link>
            <guid isPermaLink="false">https://medium.com/p/906dcd569ede</guid>
            <category><![CDATA[open-source-contribution]]></category>
            <category><![CDATA[first-step-at-open-source]]></category>
            <category><![CDATA[contribution]]></category>
            <category><![CDATA[how-to-contribute]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Juhee Kang]]></dc:creator>
            <pubDate>Sun, 24 Oct 2021 04:54:20 GMT</pubDate>
            <atom:updated>2026-03-22T14:56:07.122Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dlKzZLUvLSktV1Hkx2ZBOA.png" /></figure><p>Explore five approaches to help you contribute to an open-source project for the first time.</p><h3>Introduction</h3><p>Before I get involved in open source in the past, I thought only code patches existed in open source contributions. Code contribution to a particular field requires a lot of background knowledge, and at that time it was quite scary to me since I was just one of the open-source newbies. It was very difficult to have a lot of knowledge like a maintainer, and it took a long time, so it seemed unrealistic that I can contribute to an open-source.</p><p>Despite this situation, with a passion for being a part of the open-source community, I began to look for ways to contribute to the OSS projects. Soon enough, I learned that there are many different ways to contribute such as bug fix, typo correction, documentation, and review, etc. After learning this, it didn’t seem that impossible, so I started my first contribution with the goal of fixing the error I was experiencing at that time.</p><p>The error was related to the interactive tutorial within “<a href="http://kubernetes.io/">kubernetes.io</a>”, which was explaining the process of deploying an app to the Kubernetes cluster. The tutorial code example with this tutorial was out of date, and the error with this code kept me from going further. The problem shown by the error was so clear that it was not difficult to fix this problem. After solving this error, I sent <a href="https://github.com/kubernetes/website/pull/8856">bug-fix PR</a> to the <a href="https://github.com/kubernetes/website">kubernetes/website</a> and my suggestion had been reflected to the repo!</p><p>This experience made me be fascinated by the open-source culture, and since then, I have been mainly working on Kubernetes L10n(localization) as an approver in the ‘sig-docs-ko-owners’ group. In this article, I’d like to introduce and describe the five approaches I’ve tried to contribute to an open-source project.</p><h3>1st: Read Through the Source (Code)</h3><p>This approach is a starter for beginners. It has been started from my thought that “There is no such thing as perfect, so there will be an answer in the source code”.</p><p>In this case, I started to read any type of source(document) on the Kubernetes/website, and within this process, I found a bunch of typos in the original document and sent <a href="https://github.com/kubernetes/website/pull/18393">PR</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*pbXHZqwaOdCwlGBqHu1QAw.png" /><figcaption><a href="https://github.com/kubernetes/website/pull/18393/files#diff-162dd9ae9ef7013160246372f186f16ce12dd06d7fcbd6927fa137883eea3739">k8s/website #18393</a></figcaption></figure><p>It was a small part, but it was a contribution that could improve the completeness of the document. And also, some of them received a `Great Catch!` from the maintainer.</p><p>The very first and easiest way to a contribution is to read through the source of the project. By this process, you’ll find several contributions, including hard coding, code style correction, and typo. It may be difficult to start analyzing the code, but simply opening and reading code is the easiest way to achieve your goal.</p><h3>2nd Approach: Solving Issues</h3><p>You may not be the one who knows deeply about the project. But still, there can be a point where you can contribute.</p><p>There are various issues in the <a href="https://github.com/kubernetes/website">kubernetes/website</a> project that I mainly contribute to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*IFM-M2D4sRb3RUBW4FymQw.png" /><figcaption><a href="https://github.com/kubernetes/website/issues">kubernetes/website issues</a></figcaption></figure><p>By navigating through the issues, I discovered an <a href="https://github.com/kubernetes/website/issues/13991">issue</a> that I could do among them. At the moment that I found this one, I immediately requested the assignment and started the contribution. This issue was about translating the cheatsheet into Korean, and I was able to send a <a href="https://github.com/kubernetes/community/pull/3660">PR</a> pretty easily.</p><p>Browsing through the issue tracker can help you find an issue that can be solved, and by sending a PR to that issue, you can contribute to an open-source.</p><p>Also, there is an issue with a <strong>good first issue</strong> label, which was added by the open-source ecosystem members to encourage beginners to contribute.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*6KsYxewxpdhfdFcKbnG2UA.png" /><figcaption><a href="https://github.com/kubernetes/website/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22">kubernetes/website good first issue</a></figcaption></figure><p>These issues are generally not difficult and consist of problems that beginners can easily solve. Therefore, you can try this approach too.</p><h3>3rd Approach: Reviews</h3><p>Many people may think that reviewing is not a contribution, but reviewing PR or Issues posted by other contributors can also be a contribution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/855/1*EUeO1NW_R1Xd9QmF6tQn8Q.png" /><figcaption><a href="https://github.com/kubernetes/website/pull/10485">kubernetes/website #10485 review</a></figcaption></figure><p>In this case, you may have a question like “I’m not even a maintainer, can I review it?”. You may be worried about it, but an open-source project develops into a better project when various people’s opinions are reflected, so don’t hesitate to review other’s code and PR.</p><h3>4th Approach: Contribute Documentation</h3><p>Document contributions, which take a large part within the total number of open-source contributions, are always open! You can find numerous places to contribute, such as, documenting features that are undocumented features (this happens quite often), or by localizing English documents into Korean and correcting incorrect document content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/909/1*aqI_eckynfXsbBQf9XJ11A.png" /><figcaption><a href="https://github.com/kubernetes/website/pull/28647/files#diff-d7e7b9ade9db17c22a4e990200b225c8d90117d2d5b610868ac6af8fa8460504">kubernetes/website #28647</a></figcaption></figure><h3>5th Approach: Add a New Issue</h3><p>The fifth approach is contributing with an issue when you found a problem but you can’t solve it or when you’re not in a situation where you can solve it(e.g. lack of test environment). For example, you might find a bug that doesn’t work properly and you don’t know how to fix it, or you may want certain features, but it may be difficult to implement. Also, you could enhance the documentation for clarification, and there might be a typo in the code. With these situations, you could leave an issue to the issue tracker and make open-source better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/934/1*Fuy9WY4PNZlodZwEZinztw.png" /><figcaption><a href="https://github.com/kubernetes/website/issues/9050">kubernetes/website #9050</a></figcaption></figure><h3>Conclusion</h3><p>When I first started to get involved in this open-source world, I was at a loss on how to start. But soon enough, I was able to continue it with a little interest in open-source by doing contributions in various ways. If you’re having trouble like me in the past, I hope these five approaches might help you with starting an open-source contribution.</p><p><em>This article is originally published by myself </em><a href="https://dzone.com/articles/taking-the-first-step-at-open-source-contribution"><em>here</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=906dcd569ede" width="1" height="1" alt=""><hr><p><a href="https://medium.com/juhee-kahng/taking-the-first-step-at-open-source-contribution-906dcd569ede">Taking the First Step at Open-Source Contribution</a> was originally published in <a href="https://medium.com/juhee-kahng">juhee.kahng</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[오픈 소스 컨트리뷰션 첫걸음 떼기]]></title>
            <link>https://medium.com/juhee-kahng-ko/%EC%98%A4%ED%94%88-%EC%86%8C%EC%8A%A4-%EC%BB%A8%ED%8A%B8%EB%A6%AC%EB%B7%B0%EC%85%98-%EC%B2%AB%EA%B1%B8%EC%9D%8C-%EB%96%BC%EA%B8%B0-35f504aa05e9?source=rss-cfadba2ae589------2</link>
            <guid isPermaLink="false">https://medium.com/p/35f504aa05e9</guid>
            <category><![CDATA[오픈소스컨트리뷰션]]></category>
            <category><![CDATA[컨트리뷰션]]></category>
            <category><![CDATA[오픈소스시작하기]]></category>
            <category><![CDATA[오픈소스기여]]></category>
            <category><![CDATA[오픈소스]]></category>
            <dc:creator><![CDATA[Juhee Kang]]></dc:creator>
            <pubDate>Wed, 30 Jun 2021 12:01:26 GMT</pubDate>
            <atom:updated>2026-03-22T13:59:00.304Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dlKzZLUvLSktV1Hkx2ZBOA.png" /></figure><blockquote><a href="https://claudiajkang.medium.com/taking-the-first-step-at-open-source-contribution-906dcd569ede">Read this post in English here</a></blockquote><p>과거에 오픈 소스를 시작하기 전에는 오픈 소스 기여에는 코드 패치만 존재하는 줄 알았습니다. 그래서인지 오픈 소스 기여에 많은 두려움이 있었고, 어떻게 시작해야할 지 막막했었습니다.</p><p>특히나 특정 분야에 대한 코드 기여는 많은 배경지식을 필요로 하기 때문에, 난이도가 너무 높았습니다. 왜냐하면 메인테이너처럼 많은 지식을 갖추기 위해서는 많은 시간이 소요될 수 밖에 없기 때문입니다.</p><p>그 후 여러 자료들을 찾아보면서 오픈 소스 컨트리뷰션에는 버그 수정, 오타 수정, 문서화, 리뷰 등 많은 방법이 있다는 것을 알게 되었습니다. 그래서 저는 그 당시 겪고 있던 에러를 해결해보겠다는 목표로 첫 컨트리뷰션에 도전하였습니다.</p><p>그 에러는 <a href="http://kubernetes.io/">kubernetes.io</a> 내의 interactive tutorial과 관련된 것이었는데, kubernetes에 app을 deploy하는 과정을 담은 소스 코드가 오래되어서 실제로 정상적으로 동작하지 않는 문제가 있었습니다. 이를 수정해서 <a href="https://github.com/kubernetes/website">kubernetes/website</a>에 <a href="https://github.com/kubernetes/website/pull/8856">bug fix PR</a>을 보내게 되었고, 그 후로는 sig-docs-ko-owners 그룹에서 approver로 활동하며 문서 한글화를 진행하는 컨트리뷰션을 진행하고 있습니다.</p><p>이 글에서는 오픈 소스를 처음 시작하는 사람들을 위해 제가 지금까지 오픈 소스 프로젝트에 컨트리뷰션을 하기 위해 시도했던 5가지 방법을 소개하고자 합니다.</p><h3>첫 번째 방법 : 코드 분석하기</h3><p>이 방법은 “코드 안에 답이 있다”는 생각에서 시작되었습니다.</p><p>저의 경우는 kubernetes/website내 문서를 조금 유심히 읽어보았고, 그 과정에서 원문에 typo가 있다는 것을 확인하고 <a href="https://github.com/kubernetes/website/pull/18393">PR</a>을 보냈습니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*pbXHZqwaOdCwlGBqHu1QAw.png" /><figcaption><a href="https://github.com/kubernetes/website/pull/18393/files#diff-162dd9ae9ef7013160246372f186f16ce12dd06d7fcbd6927fa137883eea3739">k8s/website #18393</a></figcaption></figure><p>사소하긴 하지만, `<em>Great catch!</em>`라는 메인테이너에게 받을 정도로 프로젝트 내 문서의 완성도를 조금 더 높일 수 있는 컨트리뷰션이었습니다.</p><p>이처럼 첫 번째 방법은 제일 쉽게 컨트리뷰션에 접근할 수 있는 방법인 프로젝트의 코드를 분석하는 것입니다. 이 과정을 통해 하드 코딩, 코드 스타일 수정, 오타 등 여러 가지 컨트리뷰션 거리를 찾을 수 있습니다. 이 경우, 코드를 분석을 시작하는 것이 힘들지 몰라도, 열고 읽어보는 것만으로도 가장 쉽게 컨트리뷰션을 할 수 있습니다.</p><h3><strong>두 번째 방법 : 이슈 해결하기</strong></h3><p>제가 주로 기여를 하는 <a href="https://github.com/kubernetes/website">kubernetes/website</a> 프로젝트에는 다양한 이슈들이 존재합니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*IFM-M2D4sRb3RUBW4FymQw.png" /><figcaption><a href="https://github.com/kubernetes/website/issues">kubernetes/website issues</a></figcaption></figure><p>저는 그 중 제가 할 수 있는 <a href="https://github.com/kubernetes/website/issues/13991">이슈</a>를 발견하였고, 바로 assign하여 contribution을 시작했습니다. 이 이슈는 cheatsheet를 Korean으로 번역하는 것이었고, 이를 해결하는 <a href="https://github.com/kubernetes/community/pull/3660">PR</a>을 추가하여 컨트리뷰션을 할 수 있었습니다.</p><p>이처럼 오픈 소스 프로젝트에 이미 오픈 되어 있는 이슈들을 읽어보면, 그 중 내가 해결할 수 있는 이슈를 발견할 수 있고, 이를 해결함으로써 컨트리뷰션을 할 수 있습니다.</p><p>또한, 이슈 중에는 <strong>good first issue</strong> 라벨이 붙어있는 이슈도 존재하는데, 이는 기존의 오픈 소스 생태계 구성원들이 초심자들을 위해 추가한 이슈입니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*6KsYxewxpdhfdFcKbnG2UA.png" /><figcaption><a href="https://github.com/kubernetes/website/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22">kubernetes/website good first issue</a></figcaption></figure><p>이는 초심자들이 쉽게 해결할 수 있는 문제들로 구성되어 있습니다. 그렇기 때문에 이를 해결하는 PR을 추가함으로써 컨트리뷰션을 진행할 수 있습니다.</p><h3>세 번째 방법 : 리뷰하기</h3><p>많은 사람들이 리뷰를 하는 것이 컨트리뷰션이 아니라고 생각할 수도 있지만, 다른 컨트리뷰터가 올린 PR이나 Issue를 리뷰를 해주는 것도 컨트리뷰션이 될 수 있습니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/855/1*EUeO1NW_R1Xd9QmF6tQn8Q.png" /><figcaption><a href="https://github.com/kubernetes/website/pull/10485">kubernetes/website #10485 review</a></figcaption></figure><p>이 경우에는 “내가 메인테이너가 아닌데 리뷰를 해도 될까?”에 대한 걱정이 생길 수도 있는데, 오픈 소스 프로젝트는 오히려 다양한 사람의 의견이 반영되었을 때 더 좋은 프로젝트가 되는 길이기 때문에 망설이지 말고 도전하여 컨트리뷰션을 할 수 있습니다.</p><h3><strong>네 번째 방법 : 문서 기여하기</strong></h3><p>오픈 소스 컨트리뷰션의 종류 중 많은 부분을 차지하고 있는 문서 기여에서는 다양한 컨트리뷰션을 할 수 있습니다. 가령 기능은 완성되었지만, 문서화되지 않은 기능을 문서화하거나, 영어 문서를 한국어로 번역하는 localization 작업 및 잘못된 문서 내용 수정하는 작업 등을 통해 오픈 소스 프로젝트에 컨트리뷰션할 수 있습니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/909/1*aqI_eckynfXsbBQf9XJ11A.png" /><figcaption><a href="https://github.com/kubernetes/website/pull/28647/files#diff-d7e7b9ade9db17c22a4e990200b225c8d90117d2d5b610868ac6af8fa8460504">kubernetes/website #28647</a></figcaption></figure><h3><strong>다섯 번째 방법 : 이슈 추가하기</strong></h3><p>다섯 번째 방법은 내가 문제를 발견을 했지만, 직접 해결할 수 없는 상황일 때 할 수 있는 컨트리뷰션입니다. 가령, 동작하지 않는 버그를 찾았는데 고치는 방법을 모르겠거나(Bug report), 원하는 기능이 있는데 구현이 어려운 경우(Feature request) 혹은 Typo, Documentation Enhancement 등을 해당 프로젝트에 이슈를 추가함으로써 컨트리뷰션을 할 수 있습니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/934/1*Fuy9WY4PNZlodZwEZinztw.png" /><figcaption><a href="https://github.com/kubernetes/website/issues/9050">kubernetes/website #9050</a></figcaption></figure><h3><strong>결론</strong></h3><p>오픈 소스 컨트리뷰션을 처음 할 당시에는 어떻게 시작해야할 지 막막했었는데, 여러 가지 방법으로 컨트리뷰션을 하며 오픈 소스에 조금씩 흥미를 가지고 계속해서 할 수 있었습니다. 만약 오픈 소스 컨트리뷰션에 어려움이 있으시다면, 앞서 소개한 다양한 방법들 중 한 가지 방법을 선택해서 시간을 투자한다면, “오픈 소스 컨트리뷰션”을 쉽게 시작할 수 있을 것입니다.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35f504aa05e9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/juhee-kahng-ko/%EC%98%A4%ED%94%88-%EC%86%8C%EC%8A%A4-%EC%BB%A8%ED%8A%B8%EB%A6%AC%EB%B7%B0%EC%85%98-%EC%B2%AB%EA%B1%B8%EC%9D%8C-%EB%96%BC%EA%B8%B0-35f504aa05e9">오픈 소스 컨트리뷰션 첫걸음 떼기</a> was originally published in <a href="https://medium.com/juhee-kahng-ko">juhee.kahng.ko</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Control flow: try-catch or if-else?]]></title>
            <link>https://medium.com/juhee-kahng/control-flow-try-catch-or-if-else-afa4ac44482c?source=rss-cfadba2ae589------2</link>
            <guid isPermaLink="false">https://medium.com/p/afa4ac44482c</guid>
            <category><![CDATA[exception-handling]]></category>
            <category><![CDATA[try-catch]]></category>
            <category><![CDATA[control-flow-try-catch]]></category>
            <category><![CDATA[error-handling]]></category>
            <category><![CDATA[control-flow]]></category>
            <dc:creator><![CDATA[Juhee Kang]]></dc:creator>
            <pubDate>Sun, 25 Apr 2021 09:12:21 GMT</pubDate>
            <atom:updated>2026-03-22T13:58:29.911Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MPOqFzgSZC1AUp71ZByTVA.png" /></figure><h3>Introduction</h3><p>Lately, while working on a new project, I had a chance to think about the proper way to handle control flow. As all developers might know well, the most common approaches used are try-catch and if-else. So far, I haven&#39;t thought deeply about the difference between these two. From time to time, I think I mainly adopted a more concise way of writing code. Stability was significant on this project, applying the appropriate control flow processing approach was one of the keys. For this reason, I wrote pseudocode based on the scenario for these two approaches and compared them, and I&#39;d like to share the result with this community.</p><h3>Scenario</h3><p>Suppose that the signup logic of the virtual Web service ‘A’ is not allowed to have duplicate nicknames, e-mails, and phones.</p><p>The signup verification process is as follows:<br>1. Check for duplicate nickname.<br>2. Check duplicate on personal information.<br>a. Verify email address is unique.<br>b. Verify phone number is unique.</p><p>The code below is an implementation of this logic.(I’ve excluded error-handling logic at here on purpose.)</p><pre>// signUp.js <br>function signUp(){      // function of signup<br>     userTable.isUnique(nickname) // Check for duplicate nickname.<br>     duplicateDetailInfo(email, phone); // Check duplicate on personal information. <br>     addUser(user) // Add a user<br>}  <br><br>// duplicateDetailInfo.js<br>function duplicateDetailInfo(email, phone){<br>    userTable.isUnique(email);  // Verify email address is unique.<br>    userTable.isUnique(phone);  // Verify phone number is unique.<br>}<br><br><br>// userTable.js<br>class userTable {<br>    function isUnique(value){<br>        // Will be implemented according to each approach<br>    }<br>}</pre><p>Although it’s not perfect, I purposely wrote the code to explain the difference in control flow.</p><h4>On this code, depending on how to implement userTable.isUniqueas Exception or return values(false, null, etc..), I will explain using try-catch and if-else, respectively.</h4><h3>try-catch Exception</h3><p><strong><em>On this implementation approach, </em></strong><strong><em>userTable.isUnique() will raise an error if the value exists.</em></strong></p><pre>// signup.js <br>function signUp(){<br>     try {<br>         userTable.isUnique(nickname);      // Raise Exception if the nickname is not unique.<br>         duplicateDetailInfo(email, phone); // Check for duplicate personal information.<br>    } catch (e) {<br>        console.log(&quot;fail&quot;)<br>    }<br>    addUser(user);<br>}  <br><br>// duplicateDetailInfo.js<br>function duplicateDetailInfo(email, phone){<br>    userTable.isUnique(email);  // Raise Exception if the email is not unique.<br>    userTable.isUnique(phone);  // Raise Exception if the phone is not unique.<br>}<br><br>// userTable.js<br>class userTable {<br>    function isUnique(value){<br>        value = userDB.find(value);<br>        return !value? true: throw Error(); // Raise Exception if the value is not unique.<br>    }<br>}</pre><p>The problem with this approach is that the flow of processing is not explicitly visible.</p><pre>signUp()<br>├── try<br>│   ├── .isUnique(nickname)<br>│   │    └── raise Exception<br>│   │   <br>│   └── duplicateDetailInfo()<br>│       ├── .isUnique(email)<br>│       │    └── raise Exception<br>│       │   <br>│       └── .isUnique(phone)<br>│            └── raise Exception<br>│           <br>└── catch</pre><p>For example, the nickname exception is processed by the parent function (signUp), so you can easily find the order of the control flow. However, for email and phone exceptions, it is difficult to identify the control flow because it is not easy to know where to handle the exceptions.</p><p>This code consists of two depths, so it is easy to verify, but it is not known what happens to the control flow after this line code. In case when try-catch is used multiple times, it will become harder to figure out the control flow. Furthermore, code will be less intuitive.</p><p>Of course, this try-catch approach has the advantage of being able to handle all exceptions in one place. But, this can be a disadvantage. However, if there are hundreds of exceptions, the code may also be less intuitive because <strong>different exception logic is handled in a single location.</strong></p><h3>if — else</h3><p><strong><em>On this implementation approach, </em></strong><strong><em>userTable.isUnique() will return true if the value exists.</em></strong></p><pre>// signup.js <br>function signUp(){<br>    if (!userTable.isUnique(nickname)) {    // Return false if the nickname is not unique.<br>      return console.log(&quot;fail&quot;)<br>    }   <br>    if(!duplicateDetailInfo(email, phone)) {  // Return false if the details is not unique.<br>      return console.log(&quot;fail&quot;)<br>    };<br>    addUser(user);<br>}  <br><br>// duplicateDetailInfo.js<br>function duplicateDetailInfo(email, phone){<br>    if(!userTable.isUnique(email)) {        // Return false if the email is duplicated.<br>        return false;<br>    }<br>    if(userTable.isUnique(phone)) {         // Return false if the phone is duplicated.<br>        return false;<br>    };<br>    return true<br>}<br><br>// userTable.js<br>class userTable {<br>    function isUnique(value){<br>        value = userDB.find(value);<br>        return value? true: false;          // Return false if the value is not unique.<br>    }<br>}</pre><p>For this approach, <strong>predictable and formatting can safely implement code</strong> is an advantage.</p><p>The advantage of this approach is that it can predict the flow of code and implement the code by specifying the return type(in this case, boolean). Since try-catch statement is not used, the control flow can be easily to figure out because it is handlded directly from a parent function rather than from another location(exception catch). By this benefit, it is usally possible to check quickly even if something goes wrong.</p><pre>signUp()<br>├── .isUnique(nickname)<br>│    └── return false? =&gt; handling error<br>│   <br>└── duplicateDetailInfo()<br>     └── return false? =&gt; handling error </pre><p>In the previous try-catch case shown earlier, it is difficult to identify control flow because it was not easy to determine where exceptions is handled in the case of overlapping email and phone. On the other hand, for the if-else approach, the control flow is intuitively processed according to the return value of function, so it is easy to find out what logic runs next and where the error occurs.</p><p>Of course, this approach also has the disadvantage of having to branch out with if statements for every case that occurs.</p><h3>Conclusion</h3><p>I looked up a lot of materials about control flow and found that using try-catch was considered an anti-pattern because it is difficult to identify the flow of code. Therefore, I believe that the best way is to treat the control flow as an intuitive if-else approach according to the return value, even if the amount of code is large, rather than a try-catch approach where the code is concise but unclear where an exception is handled.</p><p>If you want to get further details about why try-catch exception handling is an anti-pattern, I recommend you refer to <a href="https://softwareengineering.stackexchange.com/q/189222">this post</a>.</p><p>This article is originally published by myself <a href="https://dzone.com/articles/control-flow-try-catch-or-if-else">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=afa4ac44482c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/juhee-kahng/control-flow-try-catch-or-if-else-afa4ac44482c">Control flow: try-catch or if-else?</a> was originally published in <a href="https://medium.com/juhee-kahng">juhee.kahng</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Best Way To Migrate a RabbitMQ Server]]></title>
            <link>https://medium.com/juhee-kahng/the-best-way-to-migrate-a-rabbitmq-server-5ae20712ed2a?source=rss-cfadba2ae589------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ae20712ed2a</guid>
            <category><![CDATA[migration-rabbitmq]]></category>
            <category><![CDATA[rabbitmq-hostname]]></category>
            <category><![CDATA[migrate-a-rabbitmq]]></category>
            <category><![CDATA[migration]]></category>
            <category><![CDATA[rabbitmq]]></category>
            <dc:creator><![CDATA[Juhee Kang]]></dc:creator>
            <pubDate>Tue, 23 Mar 2021 12:42:47 GMT</pubDate>
            <atom:updated>2026-03-22T13:58:21.766Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*5nRPlTHgA8bMtsLTShaUKw.jpeg" /></figure><p>Instead of repetitive tasks, I discovered a relationship between RabbitMQ settings and a hostname, which ultimately decreased repetition when migrating servers.</p><h3>Introduction</h3><p>As the userbase of my company increased over time, I realized it was necessary to apply auto-scaling to my servers. It required server migration. Migrating RabbitMQ settings meant a lot of repetitive tasks to ensure a smooth migration process; rather than perform this, I discovered a relationship between the RabbitMQ settings and the hostname, which ultimately decreased repetition.</p><p>In this article, I’ll explain how to migrate RabbitMQ using the hostname.</p><h3>A Basic Way To Migrate RabbitMQ (Using rabbitmqctl)</h3><p>In order to migrate RabbitMQ to the same existing server setting, you need to manually set each of the settings (such as vhost, username, permission, etc.) from the existing server. For example, there is a RabbitMQ server consisted of the settings which the Vhost is test and username is Claudia. If you migrate this server, you will go through the following steps.</p><h4>Check the Existing Server RabbitMQ Setting</h4><p>1. Check the vhost</p><pre>$ sudo rabbitmqctl list_vhosts<br>Listing vhosts ...<br>name<br>/<br>test</pre><p>2. Check the username</p><pre>$ sudo rabbitmqctl list_users <br>Listing users ... <br>user tags <br>claudia [test] <br>guest [administrator]</pre><h4>Try To Migrate To the RabbitMQ Server</h4><ol><li>Install the RabbitMQ server on a new server</li><li>Create a vhost using rabbitmqctl on the new server</li></ol><pre>$ sudo rabbitmqctl add_vhost test</pre><p>3. Create a user using rabbitmqctlon the new server</p><pre>$ sudo rabbitmqctl add_user claudia claudia</pre><p>4. Set user permission using rabbitmqctl on the new server</p><pre>$ sudo rabbitmqctl set_user_tags claudia administrator <br>$ sudo rabbitmqctl set_permissions -p test claudia “.*” “.*” “.*”</pre><p>It is easy to migrate the RabbitMQ server using this way when the server has some vhost, user, etc… But if the server has many settings, it is inefficient to migrate this way because it will take a lot of time. (Maybe it requires repetition according to the settings.)</p><p>Therefore, I will introduce a new migration way without repetition that works.</p><h3>A New Way To Migrate RabbitMQ Using Copy and Setting Hostname</h3><p>For using the new way, we need to check the setting files. You can find the setting files on /var/lib/rabbitmq. Thus, let&#39;s start a migration using these files.</p><h4>Check the Existing Server RabbitMQ Setting</h4><pre>$ sudo rabbitmqctl list_vhosts<br>Listing vhosts ...<br>name<br>/<br>test<br>$ sudo rabbitmqctl list_users<br>Listing users ...<br>user tags<br>claudia [test]<br>guest [administrator]<br>$ hostname<br>claudia</pre><h4>Try To Migrate the RabbitMQ Server</h4><p>1. Find the setting files on the existing server</p><p>You can find the setting files according to the following command. (Tip: the path of RabbitMQ setting files is /var/lib/rabbitmq.)</p><pre>$ ls /var/lib/rabbitmq/<br>mnesia<br>$ cd /var/lib/rabbitmq/mnesia/<br>root@claudia:/var/lib/rabbitmq/mnesia# ls<br>rabbit@claudia rabbit@claudia-feature_flags<br>rabbit@claudia.pid rabbit@claudia-plugins-expand</pre><p>2. Install the RabbitMQ server on a new server.</p><p>3. Copy the setting file of the existing server to /var/lib/rabbitmq/mnesia on the new server</p><pre>$ scp -r /var/lib/rabbitmq/mnesia &lt;new-server-ip&gt;:/var/lib/rabbitmq/mnesia</pre><p>4. Change the hostname</p><p>If the hostname is not equal to the past one, the new server will not work properly.</p><pre>$ hostnamectl set-hostname claudia <br>$ hostname <br>claudia</pre><p>5. Restart the RabbitMQ server</p><pre>$ sudo systemctl restart rabbitmq-server</pre><h4>Check the RabbitMQ Setting on the New Server</h4><p>You can see that the migration is completed successfully:</p><pre>$ rabbitmqctl list_vhosts<br>Listing vhosts ...<br>name<br>/<br>test<br>$ rabbitmqctl list_users<br>Listing users ...<br>user tags<br>claudia [test]<br>guest [administrator]</pre><p>With this method, no matter how many settings you have, it is easy to complete the migration.</p><h3>How Is This Possible?</h3><p>When starting the RabbitMQ server, it reads the environment files from the base directory according to rabbitMQ_NODENAME. Let&#39;s check the initialization environment process of the <a href="https://github.com/rabbitmq/rabbitmq-server/blob/561d2e660decb29a2b86c52e72137865542a51fb/deps/rabbit_common/src/rabbit_env.erl">rabbitmq-server code</a>, which is a function(get_prefixed_env_var).</p><p><a href="https://github.com/rabbitmq/rabbitmq-server/blob/561d2e660decb29a2b86c52e72137865542a51fb/deps/rabbit_common/src/rabbit_env.erl#L464-L473">rabbit_env.erl#L464–473</a></p><pre>%% -------------------------------------------------------------------<br>%%<br>%% RABBITMQ_NODENAME<br>%%   Erlang node name.<br>%%   Default: rabbit@<br>%%<br>%% RABBITMQ_USE_LONGNAME<br>%%   Flag indicating if long Erlang node names should be used instead<br>%%   of short ones.<br>%%   Default: unset (use short names)</pre><p><a href="https://github.com/rabbitmq/rabbitmq-server/blob/561d2e660decb29a2b86c52e72137865542a51fb/deps/rabbit_common/src/rabbit_env.erl#L744-L836">rabbit_env.erl#L744-L836</a></p><pre>%% -------------------------------------------------------------------<br>%%<br>%% RABBITMQ_MNESIA_BASE<br>%%   Directory where to create Mnesia directory.<br>%%   Default: (Unix) ${SYS_PREFIX}/var/lib/rabbitmq/mnesia<br>%%         (Windows) ${RABBITMQ_BASE}/db<br>%%<br>%% RABBITMQ_MNESIA_DIR<br>%%   Directory where to put Mnesia data.<br>%%   Default: (Unix) ${RABBITMQ_MNESIA_BASE}/${RABBITMQ_NODENAME}<br>%%         (Windows) ${RABBITMQ_MNESIA_BASE}\${RABBITMQ_NODENAME}-mnesia<br><br><br>mnesia_base_dir(#{from_remote_node := Remote} = Context) -&gt;<br>    case get_prefixed_env_var(&quot;RABBITMQ_MNESIA_BASE&quot;) of<br>        false when Remote =:= offline -&gt;<br>            update_context(Context, mnesia_base_dir, undefined, default);<br>        false -&gt;<br>            mnesia_base_dir_from_node(Context);<br>        Value -&gt;<br>            Dir = normalize_path(Value),<br>            update_context(Context, mnesia_base_dir, Dir, environment)<br>    end;<br>mnesia_base_dir(Context) -&gt;<br>    mnesia_base_dir_from_env(Context).<br>    <br>    <br>mnesia_base_dir_from_env(Context) -&gt;<br>    case get_prefixed_env_var(&quot;RABBITMQ_MNESIA_BASE&quot;) of<br>        false -&gt;<br>            Dir = get_default_mnesia_base_dir(Context),<br>            update_context(Context, mnesia_base_dir, Dir, default);<br>        Value -&gt;<br>            Dir = normalize_path(Value),<br>            update_context(Context, mnesia_base_dir, Dir, environment)<br>    end.<br>...</pre><p>This means that if you copy the existing setup file format to the base directory /var/lib/RabbitMQ/mnesia, the setup will be applied as it is. In addition, you can see this type of setup files such as rabbit@&lt;hostname&gt;-&lt;option&gt; because of the default value of RabbitMQ_NODENAME(rabbit@&lt;hostname&gt;).</p><p>Therefore, if you have a hostname that is not the same as the existing server, the server will not run normally.</p><h3>Conclusion</h3><p>There are many different ways to migrate RabbitMQ, but it is difficult to find a way to do it easily and quickly. If you need to migrate RabbitMQ with complex settings, I recommend you use this hostname and the setup file copy method. Maybe using hostname makes for a more easy time to migrate RabbitMQ.</p><p><em>This article is originally published by myself </em><a href="https://dzone.com/articles/the-best-way-to-migration-rabbitmq"><em>here</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ae20712ed2a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/juhee-kahng/the-best-way-to-migrate-a-rabbitmq-server-5ae20712ed2a">The Best Way To Migrate a RabbitMQ Server</a> was originally published in <a href="https://medium.com/juhee-kahng">juhee.kahng</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[알고리즘 초보에서 벗어나기 위한 여정]]></title>
            <link>https://medium.com/juhee-kahng-ko/%EC%95%8C%EA%B3%A0%EB%A6%AC%EC%A6%98-%EC%B4%88%EB%B3%B4%EC%97%90%EC%84%9C-%EB%B2%97%EC%96%B4%EB%82%98%EA%B8%B0-%EC%9C%84%ED%95%9C-%EC%97%AC%EC%A0%95-1ffb6bdfec6b?source=rss-cfadba2ae589------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ffb6bdfec6b</guid>
            <category><![CDATA[wb]]></category>
            <category><![CDATA[알고리즘]]></category>
            <category><![CDATA[백준]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[초보자]]></category>
            <dc:creator><![CDATA[Juhee Kang]]></dc:creator>
            <pubDate>Mon, 11 May 2020 15:06:50 GMT</pubDate>
            <atom:updated>2026-03-22T13:58:53.620Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>알고리즘 초보의 알고리즘 공부과정</em></blockquote><p>어느 순간부터 꼭 이루고 싶은 목표의 장애물이 알고리즘이 되었다. 올해는 그 장애물을 꼭 넘고 싶어서 어쩔 수 없이 알고리즘 실력을 키워야만 하는 상황이 되었다. 그래서 이번 기회에 알고리즘 초보에서 벗어나서 코딩 테스트를 통과하겠다는 목표로 2019.12.31 부터 2020.04.26까지 알고리즘 만 하루 8시간 공부했다. 이 글에서는 어떻게 알고리즘을 공부했는지에 대한 과정 및 방법에 대해 공유하고자 한다.</p><blockquote><em>각 단계의 산출물은 </em><a href="https://github.com/ClaudiaJKang/DA-AR"><em>ClaudiaJKang/DA-AR</em></a><em> 레포에서 확인할 수 있다.</em></blockquote><h3>1. 1단계 : 2019.12.31–2020.02.05 (37일)</h3><blockquote>working branch: step12 branch</blockquote><p><strong>1) 목표</strong></p><p>Hackerrank 자료구조 &amp; 알고리즘 Easy, Medium 난이도 문제 다 풀기</p><p><strong>2) 알고리즘 사이트 선정</strong></p><p>일단 제일 먼저 어떤 사이트(백준, hackerrank, 프로그래머스 등등)를 바탕으로 공부할 것인지 선정했다. 그 당시 나는 영어공부도 하고 싶고 알고리즘도 공부하고 싶었기에 hackerrank로 선정했다.</p><p><strong>3) WBS 만들기</strong></p><p>(1) ~ (3) 단계에 걸쳐서 WBS를 구성하였다.</p><blockquote><em>세로는 알고리즘 문제, 가로는 날짜</em></blockquote><ul><li>(1) hackerrank의 자료구조와 알고리즘에 대한 문제 리스트를 모두 정리</li><li>(2) 엑셀에서 자료구조(D) / 알고리즘(A), 문제 분류, 난이도(Easy-E, Medium-M, Hard-H), 문제이름 순으로 정리</li></ul><blockquote><em>인쇄할 것이기 때문에 최대한 A4용지에 다 들어올 수 있도록 하였다.</em></blockquote><ul><li>(3) 날짜를 기입할 수 있는 칸 추가</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/824/1*c7Zvtj_pMTGYJBJuqAr0_Q.png" /></figure><p><strong>4) WBS를 바탕으로 공부하기</strong></p><p>알고리즘을 공부할 때, 항상 2)에서 완성한 WBS를 프린트해서 가지고 다니면서 문제를 풀고나서 바로바로 시각화 작업을 시작하였다.</p><p>시각화를 위해서 보라색은 푼 문제, 하늘색은 풀고 있는 문제, 남색은 풀었지만 어려운 문제, 핑크색은 어려운 문제 이렇게 규칙을 정하고 시작했다. 처음에는 색깔만 칠하다가 4일차 부터는 한 문제에 얼마나 시간을 투자하는지 알고 싶어서 한 문제를 풀때 시간도 기록했다.</p><p>첫 1주일은 쉬운 문제들 위주로 풀다 보니 약간 어려움 없이 풀 수 있었는데, 2–3주차에는 medium 난이도 문제를 풀기 시작하면서 어려움이 배가 되기 시작했다. 그 문제를 하염없이 붙잡고 있다보니 지치기 일수였고, 이게 알고리즘 공부를 하다가 딴길로 새는 원인이 됬다. 그래서 4주차부터는 medium 난이도는 과감하게 스킵하고 easy위주로 풀었다. 이렇게 진행하니 진도가 더 잘나갔고, 5주차에 hackerrank 자료구조 문제와 알고리즘 Warmup, Implementation 문제를 다 풀 수 있었다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BXKB8HLmiF9VjB8Uky28GA.jpeg" /></figure><p><strong>5) 1단계 결과</strong></p><p>자료구조 위주로 공부는 했는데, 리뷰를 안하고 계속 문제수만 채우는데 급급해서 쉬운 문제는 쉽게 풀고, 조금만 변형된 문제가 나오면 풀지 못하는 그런 상황이 반복되었다. 그래서 다음 단계에는 리뷰 작업을 추가하기로 했다.</p><h3>2. 2단계 : 2020.02.06–2020.03.15 (39일)</h3><blockquote>working branch: step12 branch</blockquote><p><strong>0) 공부 방법 수정</strong></p><p>첫 1단계를 하는 과정에서 친구가 BOJ 관련 공부법에 대한 포스팅을 하나 알려줬다. 그건 <a href="https://ryute.tistory.com/33">BOJ 길라잡이</a> 였는데, 첫 4문제를 시험삼아 풀어봤는데 생각보다 어려웠다. 그래서 구글에서 BOJ에 대한 공부방법 포스팅을 더 찾아봤는데, <a href="https://plzrun.tistory.com/entry/%EC%95%8C%EA%B3%A0%EB%A6%AC%EC%A6%98-%EB%AC%B8%EC%A0%9C%ED%92%80%EC%9D%B4PS-%EC%8B%9C%EC%9E%91%ED%95%98%EA%B8%B0">알고리즘 문제풀이(PS) 시작하기</a> 이 포스팅을 접하게 되었다. 그래서 이번 2단계에서는 이 두 가지 포스팅에서 말하는 공부방법을 적용해보기로 했다.</p><p><strong>1) 목표</strong></p><p><a href="https://ryute.tistory.com/33">BOJ 길라잡이</a>와 <a href="https://plzrun.tistory.com/entry/%EC%95%8C%EA%B3%A0%EB%A6%AC%EC%A6%98-%EB%AC%B8%EC%A0%9C%ED%92%80%EC%9D%B4PS-%EC%8B%9C%EC%9E%91%ED%95%98%EA%B8%B0">알고리즘 문제풀이(PS) 시작하기</a> 내의 문제 다 풀기</p><p><strong>2) 알고리즘 사이트</strong></p><p>백준</p><p><strong>3) WBS 만들기</strong></p><p>(1) <a href="https://ryute.tistory.com/33">BOJ 길라잡이</a>와 <a href="https://plzrun.tistory.com/entry/%EC%95%8C%EA%B3%A0%EB%A6%AC%EC%A6%98-%EB%AC%B8%EC%A0%9C%ED%92%80%EC%9D%B4PS-%EC%8B%9C%EC%9E%91%ED%95%98%EA%B8%B0">알고리즘 문제풀이(PS) 시작하기</a>의 문제 리스트를 모두 정리</p><ul><li>(2) 엑셀에서 문제 분류, 문제 번호, 문제이름 순으로 정리</li></ul><blockquote><em>순서는 알고리즘 문제풀이(PS) 시작하기 포스팅을 기준으로 하고, 두 사이트에서 모두 언급하는 문제는 색깔로 표시해주었다.</em></blockquote><ul><li>(3) 날짜를 기입할 수 있는 칸 추가</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/791/1*MdR8RTIXL3yjS4M4RdRiwA.png" /></figure><p><strong>4) WBS를 바탕으로 공부하기</strong></p><p>이번에는 1주차와는 달리 만약 풀기 어려운 문제가 있다면, 그 다음날 꼭 리뷰해주는 것을 목표로 했다. 그리고 5분안에 그 문제를 풀 수 있으면 리뷰가 완료된 것이라고 여기고 넘어갔다.</p><p>주로 <a href="https://plzrun.tistory.com/entry/%EC%95%8C%EA%B3%A0%EB%A6%AC%EC%A6%98-%EB%AC%B8%EC%A0%9C%ED%92%80%EC%9D%B4PS-%EC%8B%9C%EC%9E%91%ED%95%98%EA%B8%B0">알고리즘 문제풀이(PS) 시작하기</a> 블로그에서 제시해준 방법대로 진행했는데, DP부터 막히기 시작해서, 약간 공부 순서를 수정했다.</p><p>입출력 -&gt; DP 조금 -&gt; 스택 -&gt; 큐/덱 -&gt; 문자 -&gt; 링크드리스트 -&gt; 수학 -&gt; 그래프 -&gt; DP -&gt; 이분탐색 -&gt; 분할정복 -&gt; 그리디 -&gt; 완전탐색</p><p>공부를 하면서 생소한 이론은 <a href="https://blog.naver.com/PostList.nhn?blogId=kks227&amp;categoryNo=299&amp;skinType=&amp;skinId=&amp;from=menu&amp;userSelectMenu=true">대회알고리즘, Ries 마법의 슈퍼마리오</a> 블로그를 보면서 공부해나가면서 풀었다. 그리고 1문제를 푸는 시간이 만약 2시간 이상 넘어가면 풀 수 없다고 정의하고, 해답을 찾아서 이해하려고 노력했다.</p><p>그 결과, 목표했었던 문제 154문제 중 130문제를 풀었다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2GDD87tyJG4ZtSuAYeI2hA.jpeg" /></figure><p><strong>5) 2단계 결과</strong></p><p>1단계 때와는 달리 어려운 문제는 계속해서 리뷰를 진행해서 비슷한 유형의 어려운 문제를 만나도 쉽게 풀 수 있게 되었다. 그리고 알고리즘을 어떤 순서대로 공부해야 되는지에 대한 조금의 감?을 얻게 되었다.</p><h3>3. 3단계 : 2020.03.20–2020.04.25 (37일)</h3><blockquote>working branch: step3 branch</blockquote><p><strong>0) 공부 방법 수정</strong></p><p>2단계 공부 과정에서 알게된 <a href="https://blog.naver.com/PostList.nhn?blogId=kks227&amp;categoryNo=299&amp;skinType=&amp;skinId=&amp;from=menu&amp;userSelectMenu=true">대회알고리즘, Ries 마법의 슈퍼마리오</a> 를 바탕으로 알고리즘을 공부해보기로 했다.</p><p><strong>1) 목표</strong></p><p><a href="https://blog.naver.com/PostList.nhn?blogId=kks227&amp;categoryNo=299&amp;skinType=&amp;skinId=&amp;from=menu&amp;userSelectMenu=true">대회알고리즘, Ries 마법의 슈퍼마리오</a> 블로그의 자료구조, 이분탐색, 정렬, 그리디, 완전탐색, DP, 문자열, 분할정복 포스팅에 있는 문제를 다 풀기</p><p><strong>2) 알고리즘 사이트</strong> 백준</p><p><strong>3) WBS 만들기</strong></p><ul><li>(1) <a href="https://blog.naver.com/PostList.nhn?blogId=kks227&amp;categoryNo=299&amp;skinType=&amp;skinId=&amp;from=menu&amp;userSelectMenu=true">대회알고리즘, Ries 마법의 슈퍼마리오</a>에서 공부하고자 하는 부분의 포스팅 내의 문제 리스트를 모두 정리</li><li>(2) 엑셀에서 문제 분류, 문제이름, 문제 번호 순으로 정리</li></ul><blockquote><em>공부 순서 : 자료구조(링크드리스트, 스택, 큐, 덱, 힙, 트리, 그래프) -&gt; 이분탐색 &amp; 정렬 -&gt; 그리디 -&gt; 완전탐색 -&gt; DP &amp; 문자열 &amp; 분할정복</em></blockquote><ul><li>(3) 날짜를 기입할 수 있는 칸 추가</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/741/1*1sk3DY5HHl4ioMfJRqqqgQ.png" /></figure><p><strong>4) WBS를 바탕으로 공부하기</strong></p><p>2단계 때 리뷰했던 것보다 더 조금 빡세게 이해될 때까지 리뷰과정을 진행했고, 1개의 개념을 계속해서 파기보다 여러가지 개념을 하루에 여러개씩 푸는 방법으로 공부했다. 그리고 2단계에서 개념을 공부했지만, 한번 훑는다는 느낌으로 개념도 다시 봤다.</p><p>그리고 이번 단계에서는 푸는 문제가 1시간이 넘어가면 바로 답을 찾아봤다. 이번에 공부하면서 정말 효과적이었던 이유 중에 하나는 <a href="https://blog.naver.com/PostList.nhn?blogId=kks227&amp;categoryNo=299&amp;skinType=&amp;skinId=&amp;from=menu&amp;userSelectMenu=true">대회알고리즘, Ries 마법의 슈퍼마리오</a> 에는 풀이가 있다는 것이었다. 이 블로그 작성자님의 백준 아이디가 네이버 블로그 아이디와 동일한데, 만약 못풀겠으면 이분 풀이를 보고 이해를 하면 이론에서 이해했던 방법대로 접근해서 풀 수 있어서 효과적이었다.</p><p>또한, 이번 단계에서는 2단계보다 리뷰를 많이 한 만큼 계속해서 깔끔한 코드로 만들어 나가는 작업도 같이하였다. 그래서 이번 단계에서는 165문제를 풀었다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DR6FpO2JeiV7mp0IUOX-GA.jpeg" /></figure><p><strong>5) 3단계 결과</strong></p><p>2단계에 걸쳐서 알고리즘을 미리 공부했다 보니 1, 2단계보다 알고리즘을 푸는 속도는 훨씬 빨라졌지만, 어려운 문제를 만났을 때 혼자 못푸는 경우도 생각보다 많았다.</p><h3>4. 결론</h3><p>의도한 것은 아니지만 약 37일씩 3단계 걸쳐서 공부를 진행하고 나서 보니, 새로운 문제를 많이 접하는 것도 중요하지만 그 것보다 중요한 것이 리뷰과정이라는 것을 알게 되었다. 막상 리뷰로 하다보면 리뷰 시간이 생각보다 오래 걸려서 스킵하고 싶어지는 마음이 커지지만, 결국 이 시간이 나의 실력을 만든다고 생각하고 버텼다. 그 결과, 코딩 테스트가 시작되고 나서 문제를 딱 접한 순간 이 문제 백준에서 풀었던 문제다 라고 할 수 있었던 문제를 많이 볼 수 있었다. 그 외에도 내가 보지 못했던 문제도 차근차근 문제를 읽다 보면 어떤 알고리즘 방법으로 이 문제를 풀 수 있겠구나 라는 것이 보여서 어려움 없이 코딩테스트를 통과할 수 있었다.</p><ul><li><a href="https://drive.google.com/file/d/1UejulmGkcsT6FsSOUhd8JtosrtHDsxO3/view?usp=sharing">WBS 알고리즘 엑셀 파일</a></li><li><a href="https://bit.ly/3bHuWBx">2단계 WBS 엑셀 파일</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ffb6bdfec6b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/juhee-kahng-ko/%EC%95%8C%EA%B3%A0%EB%A6%AC%EC%A6%98-%EC%B4%88%EB%B3%B4%EC%97%90%EC%84%9C-%EB%B2%97%EC%96%B4%EB%82%98%EA%B8%B0-%EC%9C%84%ED%95%9C-%EC%97%AC%EC%A0%95-1ffb6bdfec6b">알고리즘 초보에서 벗어나기 위한 여정</a> was originally published in <a href="https://medium.com/juhee-kahng-ko">juhee.kahng.ko</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[Fedora31] Setting touchscreen in Dell XPS 13 7390 2 in 1]]></title>
            <link>https://medium.com/juhee-kahng/fedora31-setting-touchscreen-in-dell-xps-13-7390-2-in-1-1535546dfc50?source=rss-cfadba2ae589------2</link>
            <guid isPermaLink="false">https://medium.com/p/1535546dfc50</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[dell-xps-2-in-1-7390]]></category>
            <category><![CDATA[touchscreen]]></category>
            <category><![CDATA[xps-linux]]></category>
            <category><![CDATA[fedora-31]]></category>
            <dc:creator><![CDATA[Juhee Kang]]></dc:creator>
            <pubDate>Sun, 08 Dec 2019 07:06:08 GMT</pubDate>
            <atom:updated>2026-03-22T14:56:48.908Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/822/0*ALU7xonYthLH0P2D.png" /></figure><p>A few years ago, my main OS was Fedora and so I installed Fedora 31 on my new laptop. However, the touchscreen was not working in Fedora 31.</p><p>Thus, this article describes how to properly use the touchscreen on Fedora 31 on Dell XPS 2n 1 7390 machines.</p><p>You can find the same problem in <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1787997">Red hat Bugzilla</a>.</p><blockquote>In Fedora 32, the touchscreen is well worked.</blockquote><h3>1. Check Kernel version, after installing Fedora 31</h3><p>If you installed properly Fedora 31 on your laptop, kernel version of your machine would be 5.3.7-301.fc31.</p><pre># Check current kernel version <br>$ uname -a<br>&lt;kernel version&gt;</pre><p>You need to install 5.4.x version kernel in order to use the touchscreen on Fedora 31 because the fixed patch related to use touchscreen was applied after 5.4.0 version kernel.</p><blockquote><em>The under content is the patch related to use the touchscreen on Dell XPS 13 7390 2 in 1.</em></blockquote><pre>commit a8ff78f7f773142eb8a8befe5a95dd6858ebd635  <br>...<br>The BIOS bug is present on Dell XPS 13 7390 2-in-1:  <br>  <br>[ 0.001734] 5 base 4000000000 mask 6000000000 write-combining  <br>  <br>4000000000-7fffffffff : PCI Bus 0000:00  <br>4000000000-400fffffff : 0000:00:02.0 (i915)  <br>4010000000-4010000fff : 0000:00:15.0 (intel-lpss-pci)  <br>  <br>Link: https://bugzilla.kernel.org/show_bug.cgi?id=203485  <br>...</pre><h3>2. Download Kernel 5.4.x version source code</h3><p>Kernel version 5.4.x is known to have the touch screen setting. However, I used [torvalds/linux] source because I confirmed that the touch screen works well and proceeded based on this source code.</p><pre># Download kernel source code<br>$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git<br>$ cd linux<br>$ git checkout master</pre><h3>3. Setting config file</h3><pre># Copy current kernel config file<br>$ cp /boot/config-5.3.7-301.fc31.x86_64 .<br><br># Setting config details to build (touchscreen module built-in configuration)<br>$ make menuconfig</pre><p>After entering the command, which is make memuconfig , the following screen will appear.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NCkxsRMP4M9wawKc.png" /></figure><p>Press /, and find the intel_lpss_pci module. (Intel_lpss_pci module is a touch screen module.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AFCtmUkdg9CysrCj.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*t03JG6murnbG41OR.png" /></figure><p>If it looks like the screen above, press 1.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Lni3GtutJbTycJ2h.png" /></figure><p>You can see that the intel_lpss_pci module is set to M (module). However, I want to set this module to built-in and so I changed it by pressing y.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MMtfgWgO4QrevpLj.png" /></figure><p>Now press tab to press save and press exit key.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Vwa4aWUCXJt_fOb1.png" /></figure><h3>4. Build Kernel</h3><p>Build the kernel with the binrpm-pkg option due to using rpm command for installation.</p><pre>$ make prepare <br>$ make binrpm-pkg -j &lt;the number of cpu core&gt;</pre><blockquote><em>binrpm-pkg option</em></blockquote><pre>$ make help<br>...<br>Kernel packaging:  <br>...<br>binrpm-pkg - Build only the binary kernel RPM package<br>...</pre><h3>5. Install Kernel</h3><p>Kernel pkg, which has been built in step 4, is stored in $ HOME / rpmbuild / RPMS. Change path to this directory and start to install the kernel.</p><pre>$ cd ~/rpmbuild/RPMS/x86_64/<br>$ ls<br>kernel-5.4.0+-7.x86_64.rpm  kernel-headers-5.4.0+-7.x86_64.rpm<br># Kernel installation.<br>$ sudo rpm -ivh kernel-5.4.0+-7.x86_64.rpm<br># Kernel header installation.<br>$ sudo rpm -Uvh kernel-headers-5.4.0+-7.x86_64.rpm</pre><h3>6. Reboot</h3><p>Boot the kernel, which is installed in step 5. Check if the kernel version 5.4.0 is properly installed with the following command.</p><pre>$ uname -a<br>Linux 5.4.0+</pre><p>After the kernel installation, there was a problem of not being able to network after booting.</p><h3>7. Fixed Network issue</h3><p>Update the network firmware to the latest file through the following procedure and the network will operate normally.</p><pre>git clone https://chromium.googlesource.com/chromiumos/third_party/linux-firmware chromiumos-linux-firmware<br>cd chromiumos-linux-firmware<br>sudo cp iwlwifi-*  /lib/firmware/<br>cd /lib/firmware<br>sudo ln -s iwlwifi-Qu-c0-hr-b0-50.ucode iwlwifi-Qu-b0-hr-b0-50.ucode</pre><blockquote><a href="https://gitlab.com/emrose/xps13-7390_debian/issues/5#note_240886447"><em>reference</em></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1535546dfc50" width="1" height="1" alt=""><hr><p><a href="https://medium.com/juhee-kahng/fedora31-setting-touchscreen-in-dell-xps-13-7390-2-in-1-1535546dfc50">[Fedora31] Setting touchscreen in Dell XPS 13 7390 2 in 1</a> was originally published in <a href="https://medium.com/juhee-kahng">juhee.kahng</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[Fedora31] Dell XPS 13 7390 2 in 1 터치스크린 설정]]></title>
            <link>https://medium.com/juhee-kahng-ko/fedora31-dell-xps-13-7390-2-in-1-%ED%84%B0%EC%B9%98%EC%8A%A4%ED%81%AC%EB%A6%B0-%EC%84%A4%EC%A0%95-bb48e8b09619?source=rss-cfadba2ae589------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb48e8b09619</guid>
            <category><![CDATA[dell-xps-2-in-1-7390]]></category>
            <category><![CDATA[페도라]]></category>
            <category><![CDATA[델xps]]></category>
            <category><![CDATA[리눅스]]></category>
            <category><![CDATA[터치스크린]]></category>
            <dc:creator><![CDATA[Juhee Kang]]></dc:creator>
            <pubDate>Sun, 08 Dec 2019 06:23:57 GMT</pubDate>
            <atom:updated>2026-03-22T13:56:07.041Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*zgRAciDMaBHyRzwQn2Z7iA.png" /></figure><blockquote><a href="https://medium.com/@claudiajkang/fedora31-setting-touchscreen-in-dell-xps-13-7390-2-in-1-1535546dfc50">Read this post in English here</a></blockquote><p>몇년 전부터, 나의 주 OS는 Fedora였고, 자연스럽게 새로운 노트북에 Fedora 31을 설치하였다. 하지만, Dell XPS 2 in 1 7390에서 지원되는 터치스크린이 잘 동작하지 않았다.</p><p>이 글에서는 Dell XPS 2n 1 7390 머신의 Fedora 31에서 터치스크린을 정상적으로 사용하기 위한 방법에 대해 설명하고자 한다.</p><p><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1787997">레드햇 버그질라</a>에서도 이 문제에 대한 내용은 확인 할 수 있다.</p><blockquote>Fedora 32 버전에서는 터치 스크린이 잘 동작한다!</blockquote><h3>1. Fedora 31 설치 이후 커널 버전 확인</h3><p>Fedora 31이 정상적으로 설치가 되었다면, 현재 컴퓨터에는 5.3.7-301.fc31 버전의 커널이 설치되어있을 것이다.</p><pre># 현재 커널 버전 확인<br>$ uname -a<br>&lt;커널 버전&gt;</pre><p>Dell XPS 13 7390 2 in 1 터치스크린 사용 관련 패치는 5.4.x 버전의 커널 소스부터 적용되기 때문에 터치스크린 을 사용하기 위해서는 커널 5.4.x 버전 설치가 필요하다.</p><blockquote><em>다음 아래 내용은 Dell XPS 13 7390 2 in 1 터치스크린 관련 리눅스 커널 패치 내용이다.</em></blockquote><pre>commit a8ff78f7f773142eb8a8befe5a95dd6858ebd635  <br>...<br>The BIOS bug is present on Dell XPS 13 7390 2-in-1:  <br>  <br>[ 0.001734] 5 base 4000000000 mask 6000000000 write-combining  <br>  <br>4000000000-7fffffffff : PCI Bus 0000:00  <br>4000000000-400fffffff : 0000:00:02.0 (i915)  <br>4010000000-4010000fff : 0000:00:15.0 (intel-lpss-pci)  <br>  <br>Link: https://bugzilla.kernel.org/show_bug.cgi?id=203485  <br>...</pre><h3>2. 커널 5.4.x 버전 커널 소스 코드 다운</h3><p>커널 5.4.x 버전부터는 터치스크린 설정이 되어 있는 것으로 알고 있으나, 2019.12.07일 기준으로 [torvalds/linux]에서는 터치스크린이 잘 작동되는 것을 확인하여 5.4.0 버전의 소스코드를 바탕으로 진행하였다.</p><pre># 소스코드 다운로드 <br>$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git<br>$ cd linux<br>$ git checkout master</pre><h3>3. config 설정</h3><pre># 현재 커널버전 config 복사<br>$ cp /boot/config-5.3.7-301.fc31.x86_64 .<br><br># 빌드할 커널 config 세부 설정 (터치스크린 모듈 빌트인 설정을 위해)<br>$ make menuconfig</pre><p>make memuconfig 명령을 치게 되면 다음과 같은 화면이 나오게 된다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BTXmrnkrYNAEe9T8.png" /></figure><p>/를 눌러, intel_lpss_pci 모듈을 검색한다. (intel_lpss_pci 모듈이 터치스크린 모듈이다.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*n5v9qVfGJG7Je5LM.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DJDo_ROpEzZjqrGH.png" /></figure><p>위의 화면처럼 나온다면, 1을 누른다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yI85jCXRyqfm7Bcr.png" /></figure><p>현재 intel_lpss_pci 모듈이 M(모듈)으로 되어 있는 것을 확인 할 수 있고, 나는 이 모듈을 빌트인으로 설정해서 빌드하고 싶기 때문에, y를 눌러서 설정을 바꿔주었다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7bp4_ypFPTU-aPUQ.png" /></figure><p>이제 tab키를 눌러 save를 해준 후, exit로 빠져나온다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IOYYlJZOm56-BF7Q.png" /></figure><h3>4. 커널 빌드</h3><p>커널을 rpm 명령을 사용하여 설치할 것이기 때문에 binrpm-pkg 옵션으로 커널을 빌드한다.</p><pre>$ make prepare <br>$ make binrpm-pkg -j &lt;cpu core 개수&gt;</pre><blockquote><em>binrpm-pkg 옵션</em></blockquote><pre>$ make help<br>...<br>Kernel packaging:  <br>...<br>binrpm-pkg - Build only the binary kernel RPM package<br>...</pre><h3>5. 커널 설치</h3><p>4번 과정에서 빌드가 완료된 커널 pkg는 $HOME/rpmbuild/RPMS 위치에 저장이 되어있다. 그 위치로 이동하여 이제 커널 설치를 진행한다.</p><pre>$ cd ~/rpmbuild/RPMS/x86_64/<br>$ ls<br>kernel-5.4.0+-7.x86_64.rpm  kernel-headers-5.4.0+-7.x86_64.rpm<br># 커널 설치<br>$ sudo rpm -ivh kernel-5.4.0+-7.x86_64.rpm<br># 커널 헤더 설치<br>$ sudo rpm -Uvh kernel-headers-5.4.0+-7.x86_64.rpm</pre><h3>6. 재부팅</h3><p>5번 과정에서 설치한 커널버전으로 부팅한다.</p><p>아래 명령을 통해 5.4.0 버전의 커널이 정상적으로 설치되어 있는지 확인한다.</p><pre>$ uname -a<br>Linux 5.4.0+</pre><p><strong>커널 설치 이후, 부팅을 하고 나서 네트워크가 안되는 문제가 발생하였다.</strong></p><h3>7. 네트워크 문제 해결</h3><p>네트워크 펌웨어를 최신으로 아래 과정을 통해 최신파일로 교체해주면 네트워크가 정상적으로 작동하게 된다.</p><pre>git clone https://chromium.googlesource.com/chromiumos/third_party/linux-firmware chromiumos-linux-firmware<br>cd chromiumos-linux-firmware<br>sudo cp iwlwifi-*  /lib/firmware/<br>cd /lib/firmware<br>sudo ln -s iwlwifi-Qu-c0-hr-b0-50.ucode iwlwifi-Qu-b0-hr-b0-50.ucode</pre><blockquote><a href="https://gitlab.com/emrose/xps13-7390_debian/issues/5#note_240886447">참고</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb48e8b09619" width="1" height="1" alt=""><hr><p><a href="https://medium.com/juhee-kahng-ko/fedora31-dell-xps-13-7390-2-in-1-%ED%84%B0%EC%B9%98%EC%8A%A4%ED%81%AC%EB%A6%B0-%EC%84%A4%EC%A0%95-bb48e8b09619">[Fedora31] Dell XPS 13 7390 2 in 1 터치스크린 설정</a> was originally published in <a href="https://medium.com/juhee-kahng-ko">juhee.kahng.ko</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>