{"id":4586,"url":"https://github.com/leehosung/awesome-devteam","name":"awesome-devteam","description":"좋은 개발팀을 만드는데 도움이 되는 자료 ","projects_count":123,"last_synced_at":"2026-08-10T10:00:28.600Z","repository":{"id":25263086,"uuid":"28688336","full_name":"leehosung/awesome-devteam","owner":"leehosung","description":"좋은 개발팀을 만드는데 도움이 되는 자료 ","archived":false,"fork":false,"pushed_at":"2026-04-16T00:32:06.000Z","size":242,"stargazers_count":3399,"open_issues_count":0,"forks_count":294,"subscribers_count":63,"default_branch":"master","last_synced_at":"2026-07-22T01:04:38.623Z","etag":null,"topics":["cto","devteam","pair-programming"],"latest_commit_sha":null,"homepage":"","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/leehosung.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE.md","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2015-01-01T14:44:23.000Z","updated_at":"2026-07-08T01:32:26.000Z","dependencies_parsed_at":"2023-02-16T05:45:20.249Z","dependency_job_id":"ceb55a35-7d43-49ad-a23d-efbd62ca960a","html_url":"https://github.com/leehosung/awesome-devteam","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/leehosung/awesome-devteam","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/leehosung%2Fawesome-devteam","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/leehosung%2Fawesome-devteam/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/leehosung%2Fawesome-devteam/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/leehosung%2Fawesome-devteam/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/leehosung","download_url":"https://codeload.github.com/leehosung/awesome-devteam/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/leehosung%2Fawesome-devteam/sbom","scorecard":{"id":582659,"data":{"date":"2025-08-11","repo":{"name":"github.com/leehosung/awesome-devteam","commit":"a970f71029275f39b9593a5ede448820b5b10c91"},"scorecard":{"version":"v5.2.1-40-gf6ed084d","commit":"f6ed084d17c9236477efd66e5b258b9d4cc7b389"},"score":3.3,"checks":[{"name":"Code-Review","score":8,"reason":"Found 8/9 approved changesets -- score normalized to 8","details":null,"documentation":{"short":"Determines if the project requires human code review before pull requests (aka merge requests) are merged.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#code-review"}},{"name":"Packaging","score":-1,"reason":"packaging workflow not detected","details":["Warn: no GitHub/GitLab publishing workflow detected."],"documentation":{"short":"Determines if the project is published as a package that others can easily download, install, easily update, and uninstall.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#packaging"}},{"name":"Token-Permissions","score":-1,"reason":"No tokens found","details":null,"documentation":{"short":"Determines if the project's workflows follow the principle of least privilege.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#token-permissions"}},{"name":"Maintained","score":0,"reason":"0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0","details":null,"documentation":{"short":"Determines if the project is \"actively maintained\".","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#maintained"}},{"name":"Binary-Artifacts","score":10,"reason":"no binaries found in the repo","details":null,"documentation":{"short":"Determines if the project has generated executable (binary) artifacts in the source repository.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#binary-artifacts"}},{"name":"Pinned-Dependencies","score":-1,"reason":"no dependencies found","details":null,"documentation":{"short":"Determines if the project has declared and pinned the dependencies of its build process.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#pinned-dependencies"}},{"name":"Dangerous-Workflow","score":-1,"reason":"no workflows found","details":null,"documentation":{"short":"Determines if the project's GitHub Action workflows avoid dangerous patterns.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#dangerous-workflow"}},{"name":"CII-Best-Practices","score":0,"reason":"no effort to earn an OpenSSF best practices badge detected","details":null,"documentation":{"short":"Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#cii-best-practices"}},{"name":"Security-Policy","score":0,"reason":"security policy file not detected","details":["Warn: no security policy file detected","Warn: no security file to analyze","Warn: no security file to analyze","Warn: no security file to analyze"],"documentation":{"short":"Determines if the project has published a security policy.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#security-policy"}},{"name":"Fuzzing","score":0,"reason":"project is not fuzzed","details":["Warn: no fuzzer integrations found"],"documentation":{"short":"Determines if the project uses fuzzing.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#fuzzing"}},{"name":"Signed-Releases","score":-1,"reason":"no releases found","details":null,"documentation":{"short":"Determines if the project cryptographically signs release artifacts.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#signed-releases"}},{"name":"Branch-Protection","score":0,"reason":"branch protection not enabled on development/release branches","details":["Warn: branch protection not enabled for branch 'master'"],"documentation":{"short":"Determines if the default and release branches are protected with GitHub's branch protection settings.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#branch-protection"}},{"name":"License","score":10,"reason":"license file detected","details":["Info: project has a license file: LICENSE.md:0","Info: FSF or OSI recognized license: MIT License: LICENSE.md:0"],"documentation":{"short":"Determines if the project has defined a license.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#license"}},{"name":"Vulnerabilities","score":4,"reason":"6 existing vulnerabilities detected","details":["Warn: Project is vulnerable to: GHSA-968p-4wvh-cqc8","Warn: Project is vulnerable to: GHSA-fjxv-7rqg-78g4","Warn: Project is vulnerable to: GHSA-896r-f27r-55mw","Warn: Project is vulnerable to: GHSA-p8p7-x288-28g6","Warn: Project is vulnerable to: GHSA-52f5-9888-hmc6","Warn: Project is vulnerable to: GHSA-72xf-g2v4-qvf3"],"documentation":{"short":"Determines if the project has open, known unfixed vulnerabilities.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#vulnerabilities"}},{"name":"SAST","score":0,"reason":"SAST tool is not run on all commits -- score normalized to 0","details":["Warn: 0 commits out of 29 are checked with a SAST tool"],"documentation":{"short":"Determines if the project uses static code analysis.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#sast"}}]},"last_synced_at":"2025-08-20T19:35:35.208Z","repository_id":25263086,"created_at":"2025-08-20T19:35:35.208Z","updated_at":"2025-08-20T19:35:35.208Z"},"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":36484249,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-08-06T04:43:03.162Z","status":"online","status_checked_at":"2026-08-10T02:00:05.122Z","response_time":58,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"created_at":"2024-01-06T20:24:59.528Z","updated_at":"2026-08-10T10:00:28.600Z","primary_language":null,"list_of_lists":false,"displayable":true,"categories":["조직","채용","프로세스","성장","문화","코드 리뷰","TDD","동기","CTO","관리","기타"],"sub_categories":[],"readme":"# awesome-devteam\n\u003c!-- ALL-CONTRIBUTORS-BADGE:START - Do not remove or modify this section --\u003e\n[![All Contributors](https://img.shields.io/badge/all_contributors-9-orange.svg?style=flat-square)](#contributors-)\n\u003c!-- ALL-CONTRIBUTORS-BADGE:END --\u003e\n\n좋은 개발팀을 만드는데 도움이 되는 자료입니다.\n많은 분들의 참여로 좋은 문서들을 많이 모아 나갔으면 합니다.\n\n## 목차\n\n* [채용](#채용)\n* [프로세스](#프로세스)\n* [성장](#성장)\n* [조직](#조직)\n* [문화](#문화)\n* [코드 리뷰](#코드-리뷰)\n* [동기](#동기)\n* [CTO](#CTO)\n* [관리](#관리)\n* [기타](#기타)\n* [Contributors](#contributors-)\n\n## 채용\n\n* [능력있는 개발자는 어떻게 알아볼 수 있나?](https://docs.google.com/document/d/1_phA5XUszSmN7Ta-QHs4DxRz9_iu8YlhxpVjSGEbWcg/edit)\n* [스타트업 면접 후기와 꿀팁](https://brunch.co.kr/@bradlee/39)\n* [슬로워크 입사지원서 설계 이야기](http://slowalk.tistory.com/2382)\n* [성공적인 채용 면접의 공공연한 비밀](https://web.archive.org/web/20221003175533/http://agile.egloos.com/5359401)\n* [성공하는 소프트웨어 엔지니어 - 박종천](https://okky.kr/article/405804)\n* [주니어 개발자를 위한 취업 정보](https://github.com/jojoldu/junior-recruit-scheduler)\n* [개발자 채용 시 기술검증 어떻게 할 것인가](https://brunch.co.kr/@leehosung/47)\n* [면접도 소중한 인연이다](https://medium.com/@nahyunan/면접도-소중한-인연이다-6923297e4c61)\n* [채용, 조금 더 잘하기 위한 몇 가지 제안](https://www.slideshare.net/herenasoo/2018-86722782)\n* [프론트엔드 개발자는 왜 구하기 어렵나요?](https://taegon.kim/archives/4810?fbclid=IwAR0Y5iI0FeJy7aeqsZozFjamWnj7WLd1UX24-QJ3joRI1Fo0iQtHtHSPW0w)\n* [개발자 이력서 작성하기](https://wonny.space/writing/work/engineer-resume)\n* [알고리즘 테스트의 중요성](https://brunch.co.kr/@gigonelee/8)\n* [코더](https://sangminpark.blog/) - 좋은 개발자의 기준\n* [CTO를 어떻게 뽑을까](https://lqez.dev/blog/how-to-hire-cto.html?fbclid=IwAR1g0XMiUWs88t9jrg9cKYcR_xn-FQL9Nf8gE0IffrH554FrWx0AexVuWnQ)\n* [개발자 역량 평가표](https://github.com/EBvi/dev-matrix)\n* [링크드인의 전략적 활용법 11가지](https://kr.linkedin.com/posts/junyoungyoo_링크드인의-전략적-활용법-11가지-activity-7008425783136309248-ekcJ)\n\n## 프로세스\n\n* [Development and Deployment at Facebook](http://ieeexplore.ieee.org/xpl/articleDetails.jsp?reload=true\u0026arnumber=6449236) - 페이스북이 개발과 배포를 하는 방법\n* [프로덕트 스펙 문서 작성법](https://webuildproduct.com/스펙-문서-작성에-관하여-ee61a1fc294f?gi=4267bd7167af#.w69vmjpqq)\n* [The Twelve-Factor App](https://12factor.net/ko/)\n* [[번역] 잘 가요 스크럼, 반가워요 칸반](https://medium.com/@pitzcarraldo/번역-잘-가요-스크럼-반가워요-칸반-e27d1db15699#.watc0ksoc)\n* [Build the RIGHT thing - 린 \u0026 애자일 이야기](https://www.slideshare.net/ChrisCho2/springcamp-2017-build-the-right-thing-pivotal-labs-sf)\n* [프로세스 개선이 현업에서 정착되려면](http://woowabros.github.io/woowabros/2017/04/18/process.html)\n* [개발 문화 만들기](https://brunch.co.kr/@kiyoungleefige/2)\n* [좋은 기능을 만드는 방법](https://speakerdeck.com/uyeong/joheun-gineungeul-mandeuneun-bangbeob)\n* [개발자가 모자라요](http://youngrok.com/개발자가%20모자라요)\n* [칸반 5개월 사용 후기](https://brunch.co.kr/@bradlee/4)\n* [개발 게임화 시스템](https://brunch.co.kr/@bradlee/3)\n* [요기요 Android 개발 Git Branch와 Release Planning](https://medium.com/deliverytechkorea/%EC%9A%94%EA%B8%B0%EC%9A%94-android-%EA%B0%9C%EB%B0%9C-git-branch%EC%99%80-release-planning-e410289c9dc7)\n* [우린 Git-flow를 사용하고 있어요](http://woowabros.github.io/experience/2017/10/30/baemin-mobile-git-branch-strategy.html)\n* [어느 스타트업의 애자일 스크럼와 JIRA에 대한 연구 문서](http://luckyyowu.tistory.com/370)\n\n## 성장\n\n* [더 나은 개발자 되기](http://www.slideshare.net/rockdoli/ss-63333165?ref=https://blog.outsider.ne.kr/1223)\n* [어려운 것을 쉽게 배우는 방법](http://www.moreagile.net/2016/02/learning-new-stuff.html)\n* [당신이 좋은 프로그래머라는 징표](http://jhrogue.blogspot.kr/2012/06/b.html)\n* [신규 Web 서비스시 고려해 볼 사항](http://kwonnam.pe.kr/wiki/web/신규서비스)\n* [프로그래머로서의 성장을 도왔던 태도들](https://ahnheejong.name/articles/becoming-better-programmer/)\n* [회사에서 본인을 빠르게 성장시키는 방법 - People Scaling](https://www.youtube.com/watch?v=drBdnrlsq9o)\n* [누구나 원하는 개발자되기](https://blog.shiren.dev/2020-11-23/)\n* [백엔드 개발자를 꿈꾸는 학생개발자에게](https://d2.naver.com/news/3435170)\n* [컴퓨터과학 스스로 학습하기](https://github.com/minnsane/TeachYourselfCS-KR/blob/main/README.md)\n* [10배 이상 뛰어난 개발자가 되는 법](https://yozm.wishket.com/magazine/detail/1373/)\n* [개발자의 학습과 성장](https://present.do/documents/62a02582f6365307fc441c7f?page=0)\n* [당신이 성장하지 못한 이유](https://yozm.wishket.com/magazine/detail/1986/)\n  \n## 조직\n\n* [Spotify Engineering Culture](https://labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/)\n  * [Spotify doesn’t use “the Spotify model” and neither should you](https://www.jeremiahlee.com/posts/failed-squad-goals/)\n* [Spotify에서 배우는 Agile](http://www.ttimes.co.kr/view.html?no=2017021414297795756)\n* [드라마컴퍼니의 개발 조직 운영](http://blog.dramancompany.com/2016/03/개발그룹은-어떻게-일을-하는가-1/)\n* [팀을 위한 4원칙](https://brunch.co.kr/@greenful/16)\n* [리더를 위한 4원칙](https://brunch.co.kr/@greenful/31)\n* [스포카 : 더 나은 팀을 위하여](https://www.slideshare.net/HeejongAhn/ss-73274788)\n* [피보탈 랩스의 개발조직](http://media.fastcampus.co.kr/knowledge/worldclass-software-developers-role-and-responsibility-pivotallabs/)\n* [CTO vs VP Engineering](https://blog.gregbrockman.com/figuring-out-the-cto-role-at-stripe)\n* [Senior engineers reduce risk](https://hackernoon.com/senior-engineers-reduce-risk-5ab2adc13c97)\n* [세상을 바꾸는 방법](https://selfothercontext.com/how-to-change-the-world/)\n* [개발자와 소프트웨어 생산의 3대 요소](https://seokjun.kim/environment-for-good-developer/)\n* ['기능 공장'에서 일하고 있다는 12가지 신호](https://brunch.co.kr/@cojette/31)\n* [넥슨 해외 메이플팀이 겪은 '기술 부채' 이야기](http://www.thisisgame.com/webzine/gameevent/nboard/227/?n=82128)\n* [뱅크샐러드의 특별한 스펙, '테크 스팩'](https://blog.banksalad.com/tech/we-work-by-tech-spec/)\n* [사람을 찾고 함께 성장하는 길](https://mysetting.io/slides/contrast-and-vector?fbclid=IwAR3Ra9EHtIbDhKSJF_ZjowBuVYOWkTLFStNXPzkfdxrerfj3Tvv6msRhkds)\n\n## 문화\n\n* [구글은 어떻게 일하는가?](http://www.slideshare.net/alleciel/how-google-works-korean?related=1) - 인재, 문화의 중요성\n* [조직문화 패러다임의 진화과정](https://www.facebook.com/stage5/videos/772922059484399/)\n* [우아한 형제들 이야기](http://woowabros.github.io/woowabros/2016/06/30/woowabros_cto.html)\n* [Git 100% 활용하기](https://academy.realm.io/kr/posts/360andev-savvas-dalkitsis-using-git-like-a-pro/)\n* [성공적으로 재택 근무 시스템을 도입하는 방법](http://ppss.kr/archives/88997)\n* [스타트업에서 스크럼 잘하기](https://www.slideshare.net/yonghoon0126/ss-72605097)\n* [운동이 시작되는 방법](https://www.ted.com/talks/derek_sivers_how_to_start_a_movement?language=ko)\n* [스타트업 DNA](https://brunch.co.kr/@yeobag/4)\n* [코드품질 개선을 위한 GS SHOP 고군분투기](https://www.slideshare.net/hnki0104/gs-shop-73646180)\n* [이제 직장에서 엄격한 서열은 잊어야 할 때](https://www.ted.com/talks/margaret_heffernan_why_it_s_time_to_forget_the_pecking_order_at_work?language=ko)\n* [넷플릭스의 문화 : 자유와 책임](https://www.slideshare.net/watchncompass/freedom-responsibility-culture)\n* ['기능 공장'에서 일하고 있다는 12가지 신호](https://brunch.co.kr/@cojette/31)\n* [CEO는 직급 만들기에 주저해야 한다](http://www.ttimes.co.kr/view.html?no=2017051811027720697)\n* [심리적 안정감, 성공적인 성과를 만드는 팀의 필수조건](https://www.slideshare.net/haezoom/ss-76096152)\n* [회사에서 새로운 기술_적용하기](https://www.slideshare.net/junseokjung1/ss-76115779)\n* [스포티파이에서는 결정권자가 누구인지 아무도 신경쓰지 않는다](https://hahnryu.com/2017/06/15/spotify/)\n* [사고를 쳐도 혼나지 않는 회사](https://brunch.co.kr/@svillustrated/13)\n* [조직이 성장하는 법 – 문화와 시스템](https://medium.com/kimjimin-company/조직이-성장하는-법-문화와-시스템-db7730febc8)\n* [왜 엔지니어링 블로그를 운영해야할까?](https://medium.com/styleshare/styleshare-engineering-blog-c4ae14d49cf4)\n* [당신을 성장시켜 주는 조직](https://brunch.co.kr/@younghakjang/1)\n* [더 나은 개발 팀 만들기](https://brunch.co.kr/@gigonelee/10)\n* [팀 문화의 탄생](https://woowabros.github.io/experience/2020/05/13/birth-of-team-culture.html)\n* [뱅크샐러드의 특별한 스펙, '테크 스펙'](https://blog.banksalad.com/tech/we-work-by-tech-spec/)\n\n## 코드 리뷰\n\n* [코드리뷰를 시작하려는 그대에게](https://www.slideshare.net/JiyeonSeo2/ss-73455188)\n* [코드 리뷰 가이드](http://www.haruair.com/blog/3116)\n* [매끄러운 ‘코드 리뷰’를 돕는 10가지 방법](http://1boon.kakao.com/bloter/238819)\n* [카카오스토리 웹팀의 코드리뷰 경험](http://ohgyun.com/712)\n* [코드리뷰를 돕는 10가지 방법](http://www.bloter.net/archives/238819)\n* [소스 코드리뷰](https://brunch.co.kr/@supims/11)\n* [드라마컴퍼니의 Pair Programming 도입 사례](http://blog.dramancompany.com/2015/11/tom과-jaden의-첫-페어-프로그래밍-도전기/)\n* [드라마컴퍼니의 Pair Programming과 Code Review 도입 후기](http://blog.dramancompany.com/2016/05/드라마의-pair-programming과-code-review-도입-후기/)\n* [페어 프로그래밍을 넘어서 - Mob programming](http://www.moreagile.net/2014/12/mob-programming.html)\n* [코드 리뷰, 5가지만 기억하자](http://silentsoft.tistory.com/20)\n* [깃헙을 통한 코드리뷰](http://ohgyun.com/367)\n* [Gerrit을 이용한 코드 리뷰 시스템](http://d2.naver.com/helloworld/6033708)\n* [코드리뷰, GitHub로 바로 적용하기](https://academy.realm.io/kr/posts/codereview-howto/)\n* [카카오스토리 팀의 코드 리뷰 도입 사례 - 코드 리뷰, 어디까지 해봤니?](http://tech.kakao.com/2016/02/04/code-review/)\n* [효과적인 코드 리뷰를 위해서](https://engineering.linecorp.com/ko/blog/effective-codereview/?fbclid=IwAR06sz07ZCaEKqtoeT0s_YRdXw5OhiLRxDgK8gVldpCJVl3GP_Txe6WJRro)\n* [코드 리뷰 in 뱅크샐러드 개발 문화](https://blog.banksalad.com/tech/banksalad-code-review-culture/)\n* [좋은 코드](https://sangminpark.blog/2021/05/28/%ec%a2%8b%ec%9d%80-%ec%bd%94%eb%93%9c/?fbclid=IwAR1xnp3ZCd3Z3XriKdqatpYgvMLxo3TKbJEryfVw_DwVYJpZuGG-y1EnzNg)\n* [코드 리뷰 피라미드](https://drive.google.com/file/u/1/d/1w8nOVhaWI9utZR42dEJndCiOeiydSRfz/view?usp=sharing)\n* [글로벌기업은 코드 리뷰를 어떻게 할까요?](https://www.samsungsds.com/kr/insights/global_code_review.html)\n\n## TDD\n\n* [코드 악취를 맡는 후각 훈련의 시간](https://helloworld.kurly.com/blog/rms-refactoring/?fbclid=IwAR0Ej8tnklxyc0kPVeyxX_CMKDSmtY_IyyGo2WHfMHRoxMEN6VF1TsF5lZQ)\n* [코드 커버리지 80% 넘긴 썰](https://brunch.co.kr/@leehosung/43)\n\n## 동기\n\n* [갈망의 아궁이](https://www.slideshare.net/devcatpublications/ss-6097436?next_slideshow=1)\n* [게임팅커가 되자](https://www.slideshare.net/devcatpublications/2015-44143372)\n* [고난, 비전, 직업에 대한 이야기](https://sangminpark.blog/2016/10/30/고난-비전-직업에-대한-이야기/)\n* [퇴사 부검](https://techblog.woowahan.com/2723/)\n\n## CTO\n\n* [CTO는 무슨 일을 하나?](http://www.mimul.com/pebble/default/2018/01/23/1516704882980.html)\n* [스타트업 CTO의 일](https://brunch.co.kr/@leehosung/40)\n* [스타트업에서 CTO의 역할](https://www.popit.kr/스타트업에서-cto의-역할)\n* [엔지니어링 리더들을 위한 안티-패턴들(Anti-patterns)](https://news.hada.io/topic?id=15744\u0026utm_source=slack\u0026utm_medium=bot\u0026utm_campaign=T04JK938N)\n\n## 관리\n\n* [실무자와 관리자의 8시간은 정말 같을까?](https://brunch.co.kr/@dooook/34)\n* [개발자의 효율성](https://brunch.co.kr/@hika/7)\n* [너와 나는 다른 시간을 달린다](https://brunch.co.kr/@younghakjang/13)\n* [실리콘밸리 임원들이 회의하는 법](http://ppss.kr/archives/67454)\n* [그 때 알았더라면 좋았을 것들](https://www.youtube.com/watch?v=rYT4efmkgCw)\n* [A framework for Engineering Managers](https://github.com/jorgef/engineeringladders)\n\n## 기타\n\n* [Awesome Devblog](https://github.com/awesome-devblog/awesome-devblog)\n* [당근마켓 성장과 개발 스택의 변화](https://youtu.be/ELlQXruFesI)\n* [Git 브랜치 배우기](https://learngitbranching.js.org/?locale=ko)\n* [빠르고 정확하게 답변을 받을 수 있는 질문하는 법](https://blog.2dal.com/author/asbubam/)\n* [프로그래머 역량 체크](https://docs.google.com/document/d/1hnsBid61Ak7YVMerGZuxbHLFgTZ_pRwUs2-xwbkvNpc/)\n* [개발자들을 위한 테크니컬 라이팅 10계명](https://tech.kakaoenterprise.com/110)\n* [테크니컬 라이팅 4대 원칙](https://tech.kakaoenterprise.com/102)\n","projects_url":"https://awesome.ecosyste.ms/api/v1/lists/leehosung%2Fawesome-devteam/projects"}