부록 A — 참고 문헌

이 문서는 코딩 커리어 핸드북 v1.2.0에 수록된 링크 1,501개 전체를 장별로 정리한 원본 부록 색인입니다. 다른 기기로 책을 읽으면서 휴대폰이나 컴퓨터에서 링크를 열 때 특히 유용합니다.

이 목록은 당시 모습 그대로 보존한 기록이므로, 일부 링크는 출간 이후 주소가 바뀌었거나 더 이상 접속되지 않을 수 있습니다.

A.1 커리어: Readme

약 20% 더 많은 돈을 법니다: https://careerkarma.com/blog/software-engineer-vs-developer/
Kelly Vaughn: https://twitter.com/kvlly/status/1262887951878537216
인생을 바꿀 만한 금액: https://danluu.com/startup-tradeoffs/
그린필드: https://en.wikipedia.org/wiki/Greenfield_project
다음 에이전시 설문 조사를 참고하십시오: https://devquarterly.com/report/q2_2020/web
FAANG: https://www.investopedia.com/terms/f/faang-stocks.asp
톱니바퀴의 부품: https://news.ycombinator.com/item?id=21961560
빙하처럼 느린 개발 속도: https://news.ycombinator.com/item?id=23917131
OSI 모델: https://en.wikipedia.org/wiki/OSI_model
좁은 허리(Narrow Waists): https://www.swyx.io/writing/narrow-waists/
데이터 과학: http://datascicareer.com/
사이버 보안: https://danielmiessler.com/blog/build-successful-infosec-career/
탐독할 자료: https://en.wikipedia.org/wiki/Wirth%27s_law
CAP 정리: https://en.wikipedia.org/wiki/CAP_theorem
클라우드 배포판: https://gist.github.com/sw-yx/ff8a4f6757286444fa20b43f6b98b205
#NoCode 자동화를 구축하는 생산성 마니아들: https://www.swyx.io/writing/no-code-rpa/
시스젠더 이성애자: https://lgbtqexperiment.com/2019/04/06/what-is-the-intent-behind-cishet-and-does-it-matter/
컴퓨터 과학 전공자 중 여성은 17%에 불과합니다: https://jaxenter.com/women-in-computer-science-majors-133646.html
업계 설문 조사: https://insights.stackoverflow.com/survey/2020#developer-profile-gender%E2%80%A6
2020년 Pinterest를 상대로 제기된 고발: https://www.fastcompany.com/90523292/discrimination-charges-at-pinterest-reveal-a-hidden-silicon-valley-hiring-problem
1940년대의 전문 프로그래머는 여성이었습니다: https://www.history.com/news/coding-used-to-be-a-womans-job-so-it-was-paid-less-and-undervalued
그레이스 호퍼 해군 소장: https://en.wikipedia.org/wiki/Grace_Hopper#UNIVAC
에이다 러브레이스는 이를 위한 프로그램을 작성하고 있었습니다: https://www.mentalfloss.com/article/53131/ada-lovelace-first-computer-programmer
당신의 특권 빌려주기: https://www.youtube.com/watch?v=hyiMathkUrQ
Women in Games International: https://www.getwigi.com/
PyLadies: https://www.pyladies.com/
Front-End Foxes: https://www.vuevixens.org/about/
BlacksInTechnology: https://www.blacksintechnology.net/
Latina Geeks: https://latinageeks.com/
Lesbians Who Tech: https://lesbianswhotech.org/
MotherCoders: http://www.mothercoders.org/
VetsinTech: https://vetsintech.co/

A.2 커리어: 입문자

FreeCodeCamp: https://www.freecodecamp.org/
FrontendMasters: https://frontendmasters.com/bootcamp/
TreeHouse: https://join.teamtreehouse.com/100-days-of-code/
The Odin Project: https://www.theodinproject.com/
Codecademy: https://www.codecademy.com/learn/introduction-to-javascript
대학교: https://www.youtube.com/watch?v=WGJJIrtnfpk
of: https://www.youtube.com/watch?v=_uQrJ0TkZlc
YouTube: https://www.youtube.com/watch?v=rfscVS0vtbw
데이터 과학: https://livebook.manning.com/book/build-your-career-in-data-science/
사이버 보안: https://danielmiessler.com/blog/build-successful-infosec-career/
클라우드: https://forrestbrazeal.com/2020/04/23/the-cloud-resume-challenge/
데브옵스: https://medium.com/@yasmintaylor846/guide-to-becoming-an-dev-ops-goddess-and-a-six-figure-tech-boss-451cdfcb5b61
모바일 개발: https://blog.bitsrc.io/how-to-start-a-career-as-a-mobile-developer-d63f197ad501
멋진 개발자 팟캐스트 목록: https://www.swyx.io/writing/fave-podcasts/
엔지니어처럼 말하기: https://www.youtube.com/watch?v=w3Pi5Ofvrbc
Egghead: http://egghead.io/
Frontend Masters: https://frontendmasters.com/
Codecademy: https://www.codecademy.com/
ACloudGuru: https://read.acloud.guru/
Pluralsight: https://www.pluralsight.com/
100 Days of Code: https://www.100daysofcode.com/
No Zero Days: https://medium.com/@fayadh56/the-concept-of-no-more-zero-days-and-why-motivation-is-fleeting-9c1c307f8948
CodeNewbies: https://www.codenewbie.org/
FreeCodeCamp: https://www.freecodecamp.org/
DEV: http://dev.to/
CareerKarma: https://careerkarma.com/
CodingBlocks: https://www.codingblocks.net/
Codebar: https://codebar.io/
CodingCoach: https://mentors.codingcoach.io/
조엘 테스트: https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-steps-to-better-code/
테스팅 트로피: https://kentcdodds.com/blog/write-tests/
테스팅 허니콤: https://labs.spotify.com/2018/01/11/testing-of-microservices/
어느 정도 자세히 알아 두십시오: https://github.com/alex/what-happens-when
the Missing Semester: https://www.youtube.com/channel/UCuXy5tCgEninup9cGplbiFw?app=desktop
First Timers Only: https://www.firsttimersonly.com/
다음 자료: https://github.com/kamranahmedse/developer-roadmap
TeachYourSelfCS: https://teachyourselfcs.com/
Open Source Society University: https://github.com/ossu/computer-science
스콧 영의 MIT 챌린지: https://www.scotthyoung.com/blog/myprojects/mit-challenge-2/
자바스크립트를 배운다는 것은 어떤 느낌인가: https://hackernoon.com/how-it-feels-to-learn-javascript-in-2016-d3a717dd577f?gi=e31701e17ad9
Docker: 이것이 미래입니다: https://circleci.com/blog/its-the-future/
우리 $FAMOUS_COMPANY가 $HYPED_TECHNOLOGY로 전환한 이유: https://saagarjha.com/blog/2020/05/10/why-we-at-famous-company-switched-to-hyped-technology/

A.3 커리어: 구직

핸드북: https://yangshun.github.io/front-end-interview-handbook/
워크숍: https://frontendmasters.com/courses/interviewing-frontend/
흔히 볼 수 있는 일반적인 조언: https://www.youtube.com/watch?v=ebJ0XBOjowo
Steve Yegge: https://steve-yegge.blogspot.com/2008/03/get-that-job-at-google.html
거짓 음성(false negative): https://en.wikipedia.org/wiki/False_positives_and_false_negatives
생일 문제: https://en.wikipedia.org/wiki/Birthday_problem
하시브 쿠레시(Haseeb Qureshi): https://haseebq.com/how-to-break-into-tech-job-hunting-and-interviews/
경로 의존성: https://en.wikipedia.org/wiki/Path_dependence
내가 좋아하는 것, 내가 잘할 수 있는 것, 세상이 가치 있게 여기는 것의 교집합: http://strategicdiscipline.positioningsystems.com/bid/98239/The-Hedgehog-Concept
멋진 개발 팟캐스트 목록: https://github.com/sw-yx/awesome-dev-podcasts
종료된 대선 캠페인: https://www.youtube.com/watch?v=TDh2iKzBh4E
200: https://twitter.com/kefimochi/status/1256626623270404098
300: https://learnersbucket.com/tech/how-i-got-my-first-job-after-failing-for-more-than-300-times/
CodeNewbie: https://www.codenewbie.org/podcast
FreeCodeCamp: https://freecodecamp.libsyn.com/
Breaking Into Startups: https://breakingintostartups.com/
Hacker News: https://news.ycombinator.com/submitted?id=whoishiring
CodePen: https://codepen.io/jobs/
StackOverflow: https://stackoverflow.com/jobs
POCIT Jobs: https://www.pocitjobs.com/
Include.io: https://include.io/
Wallbreakers: https://wallbreakers.com/
Ada’s List: https://adaslist.co/jobs
Hire Tech Ladies: https://www.hiretechladies.com/
Diversify Tech Co: https://www.diversifytech.co/join/
YSYS: https://www.thisisysys.com/
Tech Talent Charter: https://www.techtalentcharter.co.uk/home
JavaScript 30: https://javascript30.com/
Just-Build-Websites: https://github.com/melanierichards/just-build-websites
디자인/UX 직무에서는 훌륭한 포트폴리오가 큰 도움이 됩니다: https://medium.com/capitalonedesign/how-i-landed-a-ux-job-in-8-months-without-work-experience-or-a-degree-a057d32df1f9
Mekka Okereke: https://twitter.com/mekkaokereke/status/1266051694284038144
아이디어를 얻으려면 이 템플릿을 사용하십시오: https://www.careercup.com/resume
Canva 이력서 템플릿: https://www.canva.com/templates/search/resumes/
ZipJob: https://zipjob.com/free-review
창의적인 방법: https://thekanyestory.com/
그가 자신의 큰 기회를 얻게 된 계기로 꼽는 것: https://twitter.com/kelseyhightower/status/1254466032799870977
Cisco의 CCNA: https://www.cisco.com/c/en/us/training-events/training-certifications/certifications/associate/ccna-routing-switching.html
CompTIA, EC-Council 및 GSEC: https://alphacybersecurity.tech/five-tips-to-land-a-cyber-job/
나를 추천해 줄 사람: https://twitter.com/forrestbrazeal/status/1254822420244049921
이런 스레드: https://twitter.com/venikunche/status/1267844999699447813
Jeff Escalante: https://twitter.com/jescalan
전문가: https://www.careercup.com/interview
모의 면접을 진행하며 코칭해 주는 팟캐스트: https://stackoverflow.blog/2020/02/18/podcast-coaching-a-developer-interview/
HiredInTech의 가이드: https://www.hiredintech.com/system-design
High Scalability의 인기 게시물: http://highscalability.com/all-time-favorites/
시스템 설계 저장소: https://github.com/checkcheckzz/system-design-interview
Cracking the Coding Interview: http://www.crackingthecodinginterview.com/
기술 면접 과정 해독하기: https://twitter.com/EmmaBostian/status/1257989726168121351
자가 균형 레드-블랙 트리: https://en.wikipedia.org/wiki/Red%E2%80%93black_tree
힙 정렬: https://www.geeksforgeeks.org/heap-sort/
Byte by Byte의 50가지 질문 목록: https://www.byte-by-byte.com/wp-content/uploads/2019/01/50-Coding-Interview-Questions.pdf
Leetcode: https://leetcode.com/
Algoexpert: https://www.algoexpert.io/product
그래프 알고리즘: https://towardsdatascience.com/data-scientists-the-five-graph-algorithms-that-you-should-know-30f454fa5513?gi=31c4cc4a9f43
자료 구조: https://www.amazon.com/structure-coding-interviews-Kamal-Rawat/dp/9387284506
동적 프로그래밍: https://www.goodreads.com/book/show/34394300-dynamic-programming-for-coding-interviews
널리 알려진 자료: https://news.ycombinator.com/item?id=22331804
기술 면접은 코드 역량보다는 압박 속에서 실력을 발휘하는 능력을 시험합니다: https://news.ncsu.edu/2020/07/tech-job-interviews-anxiety/
메가 인터뷰 가이드(the Mega Interview Guide): https://github.com/danieldelcore/mega-interview-guide
Coding Interview University: https://github.com/jwasham/coding-interview-university
테스트 주도 개발: https://en.wikipedia.org/wiki/Test-driven_development
Interviewing.io: https://interviewing.io/
Byteboard: https://byteboard.dev/directory
Pramp: https://www.pramp.com/
데일 카네기 인간관계론(How to Win Friends and Influence People): https://www.goodreads.com/book/show/4865.How_to_Win_Friends_and_Influence_People
질문이 있는지 누군가 물어보면 질문을 하십시오: https://kevin.burke.dev/kevin/ask-questions-during-interviews/
조엘 테스트: https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-steps-to-better-code/
대신 다음의 업데이트된 목록을 참고하십시오: https://github.com/viraptor/reverse-interview
회사 문화에 관한 좋은 질문들: https://www.keyvalues.com/culture-queries
채용 담당자에게 물어볼 더 곤란한 질문들은 여기에 있습니다: https://chelseatroy.com/2018/05/04/questions-for-prospective-managers/
엔지니어링 리더십 질문 목록을 갖추어 두십시오: https://rushabhdoshi.com/2019/11/04/hiring-engineering-leaders.html
Daniel Vassallo: https://twitter.com/dvassallo/status/1261865145422065665
Treehouse는 견습 프로그램을 제공합니다: https://join.teamtreehouse.com/talentpath/
Shopify의 Dev Degree에 지원하십시오: https://engineering.shopify.com/blogs/engineering/dev-degree-behind-the-scenes
GitHub, AWS, Facebook 등의 펠로십: https://fellowship.mlh.io/
1년 동안 Fast.ai 과정 밟기: https://www.fast.ai/2018/08/27/grad-school/
Outreachy: https://www.outreachy.org/
CodePlatoon: https://www.codeplatoon.org/
Code2040: http://www.code2040.org/
Internshala: https://internshala.com/
Josh Goldberg: https://twitter.com/JoshuaKGoldberg/status/1261757663664320517
Digital Project Masters: https://www.digitalprojectmasters.com/
Write the Docs: https://www.writethedocs.org/
Support Drive: https://supportdriven.com/
High Agency의 예시: https://twitter.com/george__mack/status/1068238562443841538
전례가 없지는 않습니다: https://haseebq.com/farewell-app-academy-hello-airbnb-part-ii/

A.4 커리어: 주니어 개발자

Scott Hanselman: https://twitter.com/shanselman/status/1256499721029316608
그들의 방법론에 맞춰 다듬어질 수 있는: https://stackoverflow.blog/2019/12/12/why-you-should-be-hiring-more-junior-developers/
현명하게 질문하는 법: http://www.catb.org/esr/faqs/smart-questions.html
페어 프로그래밍하기: https://en.wikipedia.org/wiki/Pair_programming
처음에는 어색하게 느껴질 수 있습니다: https://twitter.com/jkup/status/1256253109288009735
Pivotal: https://medium.com/@ryanjjones10/what-is-the-pivotal-process-417fab075f4f
익스트림 프로그래밍: https://www.amazon.com/Extreme-Programming-Explained-Embrace-Change/dp/0321278658
끝까지 페어로 함께하기: https://www.newyorker.com/magazine/2018/12/10/the-friendship-that-made-google-huge
내 코드를 선제적으로 리뷰하기: https://www.netlify.com/blog/2020/03/05/feedback-ladders-how-we-encode-code-reviews-at-netlify/#one-more-tip-the-ground-floor
Google의 코드 리뷰 가이드라인: https://google.github.io/eng-practices/review/
고무 오리에게 설명해 보기: https://en.wikipedia.org/wiki/Rubber_duck_debugging
문제를 재현하는 최소한의 예제 제공하기: https://stackoverflow.com/help/minimal-reproducible-example
“좋은 질문은 어떻게 하나요?”에 관한 StackOverflow 가이드: https://stackoverflow.com/help/how-to-ask
더닝-크루거 효과: https://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
체스터턴의 울타리: https://fs.blog/2020/03/chestertons-fence/
현실 세계에서는 도움이 되지 않습니다: https://overreacted.io/goodbye-clean-code/
이야기와 모든 답글을 읽어 보십시오: https://www.reddit.com/r/cscareerquestions/comments/6ez8ag/accidentally_destroyed_production_database_on/
Instagram은 출시 당일에 스스로 DDoS를 일으켰습니다: https://twitter.com/kevin/status/1256431142086955009
Pixar의 누군가가 토이 스토리 2에 rm -rf를 실행해 영화의 90%를 삭제했습니다: https://twitter.com/swyx/status/1018618475311521793
한 은행의 프로덕션 환경을 대상으로 침투 테스트를 하다가 하룻밤 사이에 500만 달러를 허위로 만들어 낸 사례: https://twitter.com/alexstamos/status/1255993897697697793
실수로 Apple 온라인 스토어에서 iPhone을 내려 버린 일: https://twitter.com/taquitos/status/1256054066754367488
에볼라 사태 중에 말 그대로 시에라리온 전체를 인터넷에서 끊어 버렸습니다: https://twitter.com/NYCDubliner/status/1256545814782119936
데이터베이스를 실수로 삭제하지 않는 방법을 누군가에게 가르치다가 실수로 데이터베이스를 삭제한 사례: https://twitter.com/rdmurphy/status/1256796867632848897
실수로 사용자 1만 5천 명에게 2시간 동안 1분마다 이메일을 보내고, 사과 이메일에서 같은 실수를 반복한 사례: https://twitter.com/hellopablo/status/1255991899766349825
프로필을 저장하려던 모든 사람의 프로필이 오히려 삭제되었습니다: https://twitter.com/capnfabs/status/1256002755933745152
1024번 저장할 때마다 하드 드라이브를 포맷한 워드 프로세서: https://twitter.com/GeePawHill/status/1256342997643526151
엉뚱한 건물에 가서 전혀 관계없는 회사의 네트워크를 다운시켰습니다: https://twitter.com/AlanJohnstone2/status/1256368555487948801
Steam: https://github.com/valvesoftware/steam-for-linux/issues/3671
Windows: https://news.ycombinator.com/item?id=18189139
iTunes: https://www.wired.com/2001/11/glitch-in-itunes-deletes-drives/
빌 본(Bill Vaughan): https://quoteinvestigator.com/2010/12/07/foul-computer/
캔버스 전략: https://www.businessinsider.com/ryan-holidays-canvas-strategy-2015-2
가장 흔한 예시: https://twitter.com/JesusMurF/status/1064820162422034432
새 직장을 시작하는 정말 좋은 방법: https://twitter.com/swyx/status/1064742523426430976
테스트를 작성하십시오. 너무 많이 작성하지는 마십시오. 대부분은 통합 테스트로 작성하십시오.: https://kentcdodds.com/blog/write-tests/
마이클 폴란의 유명한 말: https://www.webmd.com/food-recipes/news/20090323/7-rules-for-eating
Netflix: https://twitter.com/trentmwillis/status/1064921178228158465
Ionic: https://twitter.com/jthoms1/status/1065029579826434048
PayTM: https://twitter.com/kuldeepkeshwar/status/1064959419295776768
1:1 면담에서 활용할 수 있는 그 밖의 경력 개발 질문입니다: https://github.com/VGraupera/1on1-questions
The Imposter’s Handbook: https://bigmachine.io/products/the-imposters-handbook/
TeachYourselfCS: https://teachyourselfcs.com/
연속으로 망친 발표 10번: https://podtail.com/en/podcast/screaming-in-the-cloud/episode-39-give-10-bad-talks-all-in-a-row-and-then/
키 입력을 아끼십시오: https://www.hanselman.com/blog/DoTheyDeserveTheGiftOfYourKeystrokes.aspx
인터넷에서 도움이 되는 법: https://twitter.com/patio11/status/991746610253086720

A.5 커리어: 주니어에서 시니어로

고성장 스타트업에서의 3년: https://twitter.com/copyconstruct/status/1260350540212404226
연습, 연습, 또 연습: https://twitter.com/dan_abramov/status/1260762854631800835
드레이퓌스 기술 습득 모델: https://en.wikipedia.org/wiki/Dreyfus_model_of_skill_acquisition
엔지니어링에서 암묵지는 실제로 존재합니다: https://commoncog.com/blog/tacit-knowledge-is-a-real-thing/
공개된 포스트모템 읽어 보기: http://danluu.com/postmortem-lessons/
복무 기간(tours of duty): https://hbr.org/2013/06/tours-of-duty-the-new-employer-employee-compact
Keavy McMinn의 사례: https://keavy.com/work/who-i-want-to-work-for/
더닝-크루거 효과: https://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
난이도 기준점: https://twitter.com/mekkaokereke/status/1027552576454021120
14가지 리더십 원칙: https://www.amazon.jobs/en/principles
성급한 추상화 피하기(Avoid Hasty Abstractions): https://kentcdodds.com/blog/aha-programming/
스토리텔링: https://stanete.com/storytelling-tips-technical-interviews

A.6 커리어: 시니어 개발자

GoF(Gang of Four): https://springframework.guru/gang-of-four-design-patterns/
Addy Osmani의 책: https://addyosmani.com/resources/essentialjsdesignpatterns/book/
컴파일러에 관한 드래곤 북: https://en.wikipedia.org/wiki/Compilers:_Principles,_Techniques,_and_Tools
운영 체제에 관한 공룡 책: https://www.os-book.com/OS10/
게임 프로그래밍 패턴: http://gameprogrammingpatterns.com/
시스템 설계: https://github.com/donnemartin/system-design-primer
알고리즘: https://github.com/williamfiset/Algorithms/
실무에서 실제로 사용할 수도 있는 자료 구조 & 알고리즘 예시 목록: https://blog.pragmaticengineer.com/data-structures-and-algorithms-i-actually-used-day-to-day/
아주 작은 실수 하나가 수억 규모의 손실을 초래할 수 있습니다: https://www.henricodolfing.com/2019/06/project-failure-case-study-knight-capital.html
사람의 생명이 걸려 있을 때: https://www.theverge.com/2019/3/22/18275736/boeing-737-max-plane-crashes-grounded-problems-info-details-explained-reasons#B10ojB
구체적으로 열거된 비상 상황: https://google.github.io/eng-practices/review/emergencies.html
변수 이름 짓기: https://www.joelonsoftware.com/2005/05/11/making-wrong-code-look-wrong/
장애 포스트모템 템플릿: https://medium.com/@adhorn/incident-postmortem-template-7b0e0a04f7a8
포스트모템을 공개하십시오: https://github.com/danluu/post-mortems
워드 커닝햄(Ward Cunningham): https://en.wikipedia.org/wiki/Ward_Cunningham
이름을 딴 법칙: https://en.wikipedia.org/wiki/Ward_Cunningham#Cunningham's_Law
신중한 부채와 무모한 부채: https://martinfowler.com/bliki/TechnicalDebtQuadrant.html
세 가지 범주의 부채: https://guides.hashicorp.now.sh/general-code/tech-debt#what-is-technical-debt
Joel Spolsky: https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/
하이럼의 법칙: https://www.hyrumslaw.com/
서둘러 DRY를 지키려 하는 것: https://overreacted.io/goodbye-clean-code/
성급한 추상화: https://kentcdodds.com/blog/aha-programming/
피할 수 없는 변경에 최적화하십시오: https://overreacted.io/optimized-for-change/
Dan Abramov의 Deconstruct 2019 발표: https://www.deconstructconf.com/2019/dan-abramov-the-wet-codebase
스트랭글러(Strangler) 또는 퍼사드(Facade) 패턴: https://docs.microsoft.com/en-us/azure/architecture/patterns/strangler
브리지 패턴: https://en.wikipedia.org/wiki/Bridge_pattern
Sarah Dayan: https://twitter.com/frontstuff_io/status/1264189583220244480
위험 줄이기, 활성화하기, 마무리하기: https://lethain.com/migrations/
윌 라슨(Will Larson): https://lethain.com/migrations/
CircleCI와 Darklang의 창업자인 Paul Biggar의 이야기입니다: https://medium.com/darklang/how-dark-deploys-code-in-50ms-771c6dd60671#bf0c
Facebook이 마이그레이션을 수행하는 방식에 대한 Dan Abramov의 이야기입니다: https://www.software-engineering-unlocked.com/episode-13-bad-tests-dan-abramov/
Piranha: https://eng.uber.com/piranha/
그중 17%는 사용되지 않았습니다: https://manu.sridharan.net/files/ICSE20-SEIP-Piranha.pdf
Thoughtbot의 Joël Quenneville: https://thoughtbot.com/blog/addressing-technical-debt
켄트 벡은 이렇게 권고했습니다: https://wiki.c2.com/?MakeItWorkMakeItRightMakeItFast
Sebastian Markbåge: https://twitter.com/sebmarkbage/status/1063585097545220096
기계가 악역을 맡게 하십시오: https://hackernoon.com/dont-be-the-bad-cop-in-pull-request-reviews-let-software-do-that-job-1eb9e574c2d1
금융 부채 비유의 불일치: https://twitter.com/jessitron/status/1123310331957145601
맨먼스 미신(Mythical Man Month) 문제: https://en.wikipedia.org/wiki/The_Mythical_Man-Month
Rachel Stephens는 다음과 같이 말합니다: https://redmonk.com/rstephens/2017/08/08/technical-debt/
Hashicorp의 기술 부채 정책: https://guides.hashicorp.now.sh/general-code/tech-debt#what-if-you-discover-technical-debt
Rick의 실제 이야기: https://www.freecodecamp.org/news/we-fired-our-top-talent-best-decision-we-ever-made-4c0a99728fde/
Apprenticeship Patterns: https://www.oreilly.com/library/view/apprenticeship-patterns/9780596806842/ch05s03.html
Better Allies의 Karen Catlin: https://medium.com/@betterallies/5-things-allies-can-do-to-sponsor-coworkers-from-underrepresented-groups-266cd512e289
Lara Hogan: https://larahogan.me/blog/what-sponsorship-looks-like/
사만다 브레투스: https://www.samanthabretous.com/blog/black-women-equal-pay-day-heres-how-you-can-help/
소프트웨어 개발에서의 인지 편향: http://smyachenkov.com/posts/cognitive-biases-software-development/
계속 갈망하고, 계속 우직하게 나아가십시오: https://www.youtube.com/watch?v=UF8uR6Z6KLc
Charity Majors: https://twitter.com/mipsytipsy/status/998075428169383937
Shift Left: https://www.infostretch.com/resources/white-papers/shift-left/
Infostretch: https://www.infostretch.com/resources/white-papers/shift-left/
스티브 잡스: https://www.forbes.com/sites/carminegallo/2011/01/04/the-7-success-principles-of-steve-jobs/
히포크라테스 선서: https://en.wikipedia.org/wiki/Hippocratic_Oath
테드 넬슨: https://en.wikipedia.org/wiki/Computer_Lib/Dream_Machines
Dream Machines: http://dreammachin.es/
Hacker Laws 저장소: https://github.com/dwmkerr/hacker-laws
제품 팀의 7가지 편향: https://www.linkedin.com/pulse/why-products-dont-succeed-7-biases-product-teams-shreyas-doshi/
프로그래밍에 관한 경구: http://pu.inf.uni-tuebingen.de/users/klaeren/epigrams.html
시니어 개발자의 한계 돌파하기: https://dev.to/theburningmonk/breaking-the-senior-developer-ceiling-bj2
기술 리더십 경로에서 성공하기: https://keavy.com/work/thriving-on-the-technical-leadership-path/
시니어 엔지니어가 된다는 것에 관하여: https://www.kitchensoap.com/2012/10/25/on-being-a-senior-engineer/
무엇이 시스템 관리자를 “시니어 시스템 관리자”로 만드는가?: https://everythingsysadmin.com/2012/09/seniorsysadmins.html
아키텍트로 승진하기: https://news.ycombinator.com/item?id=23152092

A.7 커리어: 코딩 그 너머

우리 업계의 정말 수많은 번아웃 사례: https://hn.algolia.com/?q=burnout
번아웃 증상을 알아차리십시오: https://www.youtube.com/watch?v=Yk53eWIu7Nw
번창하는 소프트웨어 컨설턴트(The Prosperous Software Consultant): https://medium.com/@dabit3/the-prosperous-software-consultant-5dc8d705c5dd
Secrets of Consulting: https://www.goodreads.com/en/book/show/566213
컨설턴트를 위한 질문: https://gumroad.com/l/questions-for-consultants/
그의 컨설팅 재무 현황: https://theburningmonk.com/2020/07/i-left-full-time-employment-heres-what-happened-since/
코딩할 줄 아는 사람이 성장해 나갈 수 있는 그 밖의 대안 커리어 경로: https://www.freecodecamp.org/news/alternative-career-paths/
- Mark Roddy: https://twitter.com/digitallogic/status/1169625740796579842
피터의 법칙: https://en.wikipedia.org/wiki/Peter_principle
피플웨어(Peopleware): https://www.goodreads.com/book/show/67825.Peopleware
Sarah Mei: https://twitter.com/sarahmei/status/862583216095416320
결정적 순간의 대화: https://www.goodreads.com/book/show/15014.Crucial_Conversations
매니저가 되지 말아야 할 17가지 이유: https://charity.wtf/2019/09/08/reasons-not-to-be-a-manager/
엔지니어링 매니저를 위한 보이트-캄프 테스트: https://www.no.lol/2019-03-09-should-i-become-a-tech-lead/#the-voight-kampff-test-for-engineering-managers
최소 복무 기간: https://charity.wtf/2019/01/04/engineering-management-the-pendulum-or-the-ladder/
노트: https://twitter.com/cpojer/status/1177434208316227584
엔지니어/매니저 진자: https://charity.wtf/2017/05/11/the-engineer-manager-pendulum/
책과 블로그: https://randsinrepose.com/books/
조직 리더십 트랙: https://charity.wtf/2019/01/04/engineering-management-the-pendulum-or-the-ladder/
엔지니어링 관리의 체계: https://lethain.com/elegant-puzzle/
신임 매니저 가이드: http://katemats.com/leadership/
소프트웨어 리드 위클리(Software Lead Weekly): https://softwareleadweekly.com/?ref=hackernoon.com
Leading Snowflakes: http://leadingsnowflakes.com/
The Manager’s Path: https://www.amazon.com/Managers-Path-Leaders-Navigating-Growth/dp/1491973897
피닉스 프로젝트(The Phoenix Project): https://www.amazon.com/gp/product/1942788290
유능한 소프트웨어 엔지니어링 매니저 되기(Become an Effective Software Engineering Manager): https://theengineeringmanager.com
매니저가 되는 법: https://getweeklyupdate.com/manager-guide
Manager’s Playbook: https://github.com/ksindi/managers-playbook
Resilient Management: https://resilient-management.com/
팀장의 탄생(The Making of a Manager): https://juliezhuo.com/book/manager.html
Becoming a Technical Leader: https://www.goodreads.com/book/show/714344.Becoming_a_Technical_Leader
맨먼스 미신(the Mythical Man-Month): https://www.goodreads.com/book/show/13629.The_Mythical_Man_Month
High Output Management: https://getlighthouse.com/blog/high-output-management/
멀티플라이어(Multipliers): https://www.goodreads.com/book/show/8310410-multipliers
리더의 용기(Dare to Lead): https://www.goodreads.com/book/show/40109367-dare-to-lead
인피니트 게임(The Infinite Game): https://www.goodreads.com/book/show/38390751-the-infinite-game
24%에서 66% 사이 어딘가: https://medium.com/pminsider/the-top-3-myths-of-becoming-a-product-manager-18fe244c9c64
불싯 잡: https://www.newyorker.com/books/under-review/the-bullshit-job-boom
1931년 P&G에서 처음 만들어졌습니다: https://www.mindtheproduct.com/history-evolution-product-management/
구글다움(Googley): http://www.businessinsider.com/the-meanings-of-googliness-2013-8
한 세대 전체: https://www.businessinsider.com/what-apm-graduates-are-doing-now-2014-10?IR=T
브렛 테일러: https://en.wikipedia.org/wiki/Bret_Taylor
공개적으로 밝힌 바 있습니다: https://www.amazon.com/In-The-Plex-Google-Thinks/dp/1455875724
출처가 불분명할 수 있음: https://hbr.org/2011/08/henry-ford-never-said-the-fast
제품 요구사항 문서(Product Requirements Documents): https://en.wikipedia.org/wiki/Product_requirements_document
PRD: https://www.atlassian.com/agile/product-management/requirements
다른 벤 다이어그램: https://productcoalition.com/the-10-best-and-worst-venn-diagrams-explaining-product-management-f6006c82476c
그들이 어떤 것의 CEO도 아닌 이유: https://medium.com/@brandontluong/to-people-calling-product-managers-mini-ceo-please-stop-9864aabca31a
모든 책임은 지지만 권한은 전혀 없는 자리: https://secretpmhandbook.com/all-the-responsibility-none-of-the-authority-a-new-podcast/
Growth Hackers: https://growthhackers.com/posts
Sean Ellis: https://growthhackers.com/sean-ellis
Andrew Chen: https://andrewchen.co/how-to-be-a-growth-hacker-an-airbnbcraigslist-case-study/
Aha.io 블로그: https://blog.aha.io/
MindTheProduct: https://www.mindtheproduct.com/
Reforge 블로그: https://www.reforge.com/blog/
협곡 건너기(Crossing the Canyon): https://www.reforge.com/blog/crossing-the-canyon-product-manager-to-product-leader
블로그 글: https://amplitude.com/blog/author/john-cutler
기능 공장에서 일하고 있다는 12가지 징후: https://amplitude.com/blog/12-signs-youre-working-in-a-feature-factory-3-years-later
좋은 프로덕트 매니저, 나쁜 프로덕트 매니저: https://a16z.com/2012/06/15/good-product-managerbad-product-manager/
신임 PM에게 보내는 편지: https://sriramk.com/memos/brian_armstrong_new_PM_letter.pdf
25분으로 보는 제품 관리 20년: https://www.youtube.com/watch?v=i69U0lvi89c
PMHQ 커뮤니티: https://www.productmanagerhq.com/
Women in Product: https://www.womeninproduct.com/
Product Hunt: https://www.producthunt.com/
개발자 아보카도(Developer Avocado): https://blog.usejournal.com/the-birth-of-developer-avocados-61e4ac235033
DevRel을 가장 잘 측정하는 방법: https://openviewpartners.com/blog/measuring-the-impact-of-your-developer-relations-team/
Patrick McKenzie는 이렇게 말합니다: https://training.kalzumeus.com/newsletters/archive/do-not-end-the-week-with-nothing
좋은 기업 엔지니어링 블로그는 어떻게 쓰이는가: https://danluu.com/corp-eng-blogs/
개발자 커뮤니티 구축하기: https://ladybug.dev/
개발자 에반젤리즘: 전체 이야기: https://caseysoftware.com/blog/developer-evangelism-the-whole-story
DevRel에 입문하기 위한 7가지 팁: https://dev.to/dabit3/7-tips-for-breaking-into-devrel-7jk
Developer Relations: (More Than) The Art of Talking Good(개발자 관계: 말 잘하는 기술, (그 이상)): https://emilyfreeman.io/blog/developer-relations-more-than-the-art-of-talking-good
Get Together: https://www.people-and.com/get-together-book
DevRelCons: https://www.devrelcon.net/
서밋: http://www.devrelsummit.com/
David Perell의 글: https://twitter.com/david_perell/status/1261851180881174529
Pluralsight: https://www.pluralsight.com/
LinkedIn Learning: https://www.linkedin.com/learning/
Treehouse: https://teamtreehouse.com/teachers/signup
Frontend Masters: https://frontendmasters.com/
Egghead.io: https://egghead.io/
저는 전업 교육자입니다!: https://kentcdodds.com/blog/full-time-educator/
나만의 제품 만들고 출시하기: https://www.youtube.com/watch?v=KBlOxBQrP9I
커리어를 해킹하라: https://www.youtube.com/watch?v=-MUhcgXBj_A
7가지 기둥을 갖춘 개발자: https://www.youtube.com/watch?v=Y4wnbkatj20&feature=youtu.be
첫 출시를 성공적으로 해내기: https://www.youtube.com/watch?v=ajrDxZRpP9M
인디 해커: https://indiehackers.com/
사람들이 원하는 것을 만드십시오: http://www.paulgraham.com/good.html
데이비드 오길비(David Ogilvy)는 이렇게 말한 적이 있습니다: https://mediatel.co.uk/news/2013/11/27/dont-say-what-you-think-say-what-you-feel/
길고 느린 죽음의 경사로(the Long, Slow Ramp of Death): https://baremetrics.com/blog/long-slow-saas-ramp-of-death
더 긴 목록과 Paul Graham의 답변: http://www.paulgraham.com/notnot.html
정치적 테마의 시리얼 판매하기: https://www.honeycopy.com/marketing-ideas/airbnb-cereal-story
#엔젤투자자: https://twitter.com/hashtagangels?lang=en
Backstage Capital: https://backstagecapital.com/
Astia Global: https://astia.org
Indie.vc: https://www.indie.vc/
Earnest Capital: https://earnestcapital.com/
퍼포먼스 마케팅: https://en.wikipedia.org/wiki/Performance-based_advertising
주목받는 중: https://www.forbes.com/sites/forbestechcouncil/2019/10/16/developer-tools-quietly-become-a-growth-story/#7cf71e36dea4
전담: https://www.heavybit.com/
투자: https://oss.capital/
Zoom 같은 비즈니스: https://twitter.com/NatSandman/status/1281608476641210368?s=20
IPO 전 13년 동안: https://www.inc.com/jeremy-quittner/atlassian-ipo-one-of-bigggest-in-2015-profitability-is-key.html
체크리스트: https://www.enterpriseready.io/#
심지어 스타트업 전체도: https://techcrunch.com/2020/03/17/lightspeed-backed-workos-launches-to-help-startup-services-become-enterprise-ready/
계단식 성장: https://robwalling.com/2015/03/26/the-stairstep-approach-to-bootstrapping/
사다리: https://nathanbarry.com/wealth-creation/
제품화된 서비스: https://productizeandscale.com/what-is-productized-service/
확장되지 않는 일을 하십시오: http://paulgraham.com/ds.html
저명한 소프트웨어 스타트업 투자자인 Chetan Puttagunta는 다음과 같이 말합니다: https://twitter.com/chetanp/status/1201540828096679940
Joel Spolsky는 다음과 같이 주장합니다: https://www.joelonsoftware.com/2012/01/06/how-trello-is-different/
Indiehackers 커뮤니티와 팟캐스트: http://indiehackers.com/

A.8 원칙: Readme

- 레이 달리오: https://www.principles.com/
HashiCorp의 도(The Tao of Hashicorp): https://www.hashicorp.com/our-principles
MongoDB는 이를 자사의 가치(Values)라고 부릅니다: https://www.mongodb.com/company
파이썬의 선(The Zen of Python): https://en.wikipedia.org/wiki/Zen_of_Python

A.9 원칙: 공개적으로 배우기

암흑 물질 개발자: https://www.hanselman.com/blog/DarkMatterDevelopersTheUnseen99.aspx
공개적으로 게시되지 않는 80%의 일자리: https://www.npr.org/2011/02/08/133474431/a-successful-job-search-its-all-about-networking
사람들: https://code-cartoons.com/
정말 좋아하는 것: https://wizardzines.com/
만화: https://arkwright.github.io/scaling-react-server-side-rendering.html
모든 웹 성능 테스트 도구: https://www.swyx.io/writing/webperf-tests/
정체성을 작게 유지하기: http://www.paulgraham.com/identity.html
프로그래밍 심리학(The Psychology of Computer Programming): https://www.goodreads.com/book/show/1660754.The_Psychology_of_Computer_Programming
그 책의 십계명: https://blog.codinghorror.com/the-ten-commandments-of-egoless-programming/
에고는 방해 요소입니다: https://josebrowne.com/on-coding-ego-and-attention/
에고라는 적: https://www.goodreads.com/book/show/27036528-ego-is-the-enemy
원래 에세이를 쓴 이후로.: https://www.swyx.io/writing/learn-in-public
커닝햄의 법칙: https://meta.wikimedia.org/wiki/Cunningham%27s_Law
긍정적 강화: https://www.verywellmind.com/what-is-positive-reinforcement-2795412
약속 장치(Commitment Device): https://en.wikipedia.org/wiki/Commitment_device
가용성 편향(Availability Bias): https://en.wikipedia.org/wiki/Availability_heuristic
Nathan Barry는 다음과 같이 말했습니다: https://nathanbarry.com/marco-polo/
블룸의 분류학: https://cft.vanderbilt.edu/guides-sub-pages/blooms-taxonomy/
인바운드 마케팅: https://www.hubspot.com/inbound-marketing
상호성과 호감: https://www.influenceatwork.com/principles-of-persuasion/
자기 자신을 상품화하기: https://nav.al/productize-yourself
아무것도 없이 한 주를 끝내지 마십시오: https://training.kalzumeus.com/newsletters/archive/do-not-end-the-week-with-nothing
NASA 과학자들이 조직 차원의 지식 관리를 어떻게 하는지에 대한 이 회고: https://www.govloop.com/community/blog/how-do-rocket-scientists-learn-aka-knowledge-management-lessons-learned-at-goddard-nasa/
제프 앳우드(Jeff Atwood): https://blog.codinghorror.com/how-to-stop-sucking-and-be-awesome-instead/
Kelsey Hightower: https://thepodlets.io/episodes/007-kubernetes-as-per-kelsey-hightower/
Kent C. Dodds: https://kentcdodds.com/blog/intentional-career-building
브라이언 체스키: https://mastersofscale.com/brian-chesky-handcrafted/
Jeff Weiner: https://greylock.com/transformational-moments/
명시적 학습: https://medium.com/@reidhoffman/those-who-teach-can-do-98a30e9a74ea

A.10 원칙: 오픈 소스 앱 클론

Ryan Florence: https://mobile.twitter.com/ryanflorence/status/1119661699617787904
Spectrum: https://github.com/withspectrum/spectrum
Codesandbox: https://github.com/CompuIves/codesandbox-client
FreeCodeCamp: https://github.com/freeCodeCamp/freeCodeCamp/
Ghost: https://github.com/TryGhost/Ghost
DEV: https://github.com/thepracticaldev/dev.to
GitLab: https://gitlab.com/gitlab-org/gitlab
Fathom: https://github.com/usefathom/fathom
Planner: https://planner.now.sh/
TIL: https://til.netlify.com/
Excalidraw: https://github.com/excalidraw/excalidraw
Userbase: https://github.com/encrypted-dev/userbase
Instagram 클론: https://github.com/Sandermoen/instaclone
트위터 클론: https://github.com/muzam1l/tclone
Trello: https://react-trello.app/
JIRA: https://github.com/oldboyxx/jira_clone
YouTube 클론: https://www.reddit.com/r/reactjs/comments/hmu0dt/youtube_clone_pern_stack/
레트로 Windows UI: https://www.reddit.com/r/reactjs/search/?q=windows&restrict_sr=1
Daniel Stefanovic의 Build Your Own X: https://github.com/danistefanovic/build-your-own-x
필사(copywork): https://www.smashingmagazine.com/2017/02/improving-ui-design-skills-copywork/
Dave Ceddia: https://www.reddit.com/r/reactjs/comments/gf2veh/react_trello_clone_httpsreacttrelloapp/
Allen Hemberger와 Alinea 요리책: https://twitter.com/kevinleeme/status/1284184707110809600
공개적으로 일하기: https://chriscoyier.net/2012/09/23/working-in-public/

A.11 원칙: 도구를 알기

React의 초기 프로토타입: https://github.com/jordwalke/FaxJs
처음으로 외부에서 상당한 반향을 얻은 버전: https://futureofcoding.org/episodes/011
초기: https://github.com/reactjs/react-basic/pull/7
진행 중: https://www.swyx.io/speaking/react-from-scratch/
후회함: https://twitter.com/dan_abramov/status/1064248583229243392
자주 오해받는 것: https://twitter.com/dan_abramov/status/984102762865745920
시도했다가 실패한 API들입니다: https://cdb.reacttraining.com/react-call-return-what-and-why-7e7761f81843
React에 기여하기: https://www.swyx.io/speaking/contributing-to-react/
새 기능은 어떻게 추가합니까: https://www.youtube.com/watch?v=aS41Y_eyNrU
React의 트레이드오프: https://www.youtube.com/watch?v=ANtSWq-zI0s&vl=en
단점: https://blog.jim-nielsen.com/2019/thoughts-on-rich-harris-talk/
React의 아주 작은 클론: https://preactjs.com/
React가 그 밖에 하는 일: https://preactjs.com/guide/v10/differences-to-react

A.12 원칙: 새것에 전문화

어떤 제품의 보완재 가격이 내려가면 그 제품에 대한 수요가 증가합니다: https://www.joelonsoftware.com/2002/06/12/strategy-letter-v/
제임스 레이버: https://en.wikipedia.org/wiki/James_Laver#Laver's_Law
자기회귀 조건부 이분산성(Autoregressive Conditional Heteroskedasticity): https://en.wikipedia.org/wiki/Autoregressive_conditional_heteroskedasticity
탈레브는 저서 안티프래질에서 다음과 같이 말합니다: https://en.wikipedia.org/wiki/Antifragile
장기적인 사람들과 장기적인 게임을 하십시오.: https://nav.al/long-term

A.13 원칙: 지식을 오픈 소스하십시오

PostgreSQL은 훨씬 적은 예산으로 기능부터 개발자 경험에 이르기까지 모든 면에서 Oracle을 넘어섰습니다.: https://news.ycombinator.com/item?id=22768834
앞으로 어떤 언어도 다시는 클로즈드 소스가 되지 않을 것입니다: https://www.youtube.com/watch?v=jmPZztKIFf4
npm에 따르면: https://blog.npmjs.org/post/173260195980/announcing-npm6
Open Knowledge Foundation: http://okfn.org/
Sindre Sorhus에게서 영감을 받은 Awesome 저장소들: https://github.com/sindresorhus/awesome
Gitbook: https://www.gitbook.com/
간단한 오픈 소스 Google Sheet: https://docs.google.com/spreadsheets/d/1zlKo3f_qMPA4I5OCI1oIwNxoSCtPTJtOgG8lEwViSg0/edit#gid=385172494
나만의 치트시트를 시작했습니다: https://github.com/typescript-cheatsheets/react-typescript-cheatsheet/
React Suspense: https://github.com/sw-yx/concurrent-react-notes
디자인 팁: https://github.com/sw-yx/spark-joy/
Node.js CLI: https://github.com/sw-yx/cli-cheatsheet

A.14 원칙: 설렘을 주는 것

곤도 마리에의 2019년 Netflix 시리즈: https://en.wikipedia.org/wiki/Tidying_Up_with_Marie_Kondo
폰 레스토프 고립 효과: https://en.wikipedia.org/wiki/Von_Restorff_effect
깨진 유리창은 더 많은 범죄를 부추길 수 있습니다: https://en.wikipedia.org/wiki/Broken_windows_theory
미적 도미노 효과: https://www.itdp.org/2019/08/20/what-is-the-opposite-of-broken-windows/
카일 심슨(Kyle Simpson): https://fronteers.nl/congres/2014/sessions/kyle-simpson-choose-your-own-js-adventure
성급한 추상화를 피하십시오: https://kentcdodds.com/blog/aha-programming/
우발적 복잡성(Accidental Complexity)에 대해 경고하는 프레드 브룩스(Fred Brooks): https://en.wikipedia.org/wiki/No_Silver_Bullet
복잡성을 풀어내라고(decomplect) 촉구하는 Rich Hickey: https://www.infoq.com/presentations/Simple-Made-Easy/
클린 코드: https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship-ebook/dp/B001GSTOAM
이에 대해 합리적인 테스트를 작성하십시오: https://medium.com/@kentbeck_7670/test-desiderata-94150638a4b3
지역적 추론을 용이하게 합니다: https://sophiebits.com/2020/01/01/fast-maintainable-db-patterns.html
변경에 최적화하기: https://overreacted.io/optimized-for-change/
이에 대해서는 다양한 의견이 있습니다: https://www.swyx.io/writing/how-to-name-things/
Jem Young: https://frontendhappyhour.com/episodes/complex-flavors-complex-systems/
시간 낭비: https://stackoverflow.com/questions/184618/what-is-the-best-comment-in-source-code-you-have-ever-encountered
코드의 작동 방식을 보여 주는 ASCII 아트 다이어그램: https://github.com/facebook/react/blob/b87aabdfe1b7461e7331abb3601d9e6bb27544bc/packages/react-dom/src/events/ReactBrowserEventEmitter.js
Sarah Drasner에 따르면 다음과 같습니다. https://css-tricks.com/the-art-of-comments/
강연 버전은 여기에서 보실 수 있습니다: https://www.youtube.com/watch?v=yhF7OmuIILc
Jared Short: https://www.youtube.com/watch?v=rA4eVtpFnVs
Syslog 심각도 수준: https://en.wikipedia.org/wiki/Syslog#Severity_level
좋은 질문을 하는 방법: https://stackoverflow.com/help/how-to-ask
Annotate: https://apps.apple.com/us/app/annotate-capture-and-share/id918207447?mt=12
Zappy: https://zapier.com/zappy
LICEcap: https://www.cockos.com/licecap/
All Contributors 봇: https://allcontributors.org/
Netlify의 피드백 사다리: https://www.netlify.com/blog/2020/03/05/feedback-ladders-how-we-encode-code-reviews-at-netlify/
Conventional: Comments: https://conventionalcomments.org/
semantic release 봇: https://github.com/semantic-release/semantic-release
설치 방법, 예제, API 문서를 앞부분에 배치하십시오: https://twitter.com/DavidKPiano/status/1046833198146228225
목차 생성기: https://github.com/technote-space/toc-generator
dotenv-safe: https://www.npmjs.com/package/dotenv-safe
카피레프트: https://en.wikipedia.org/wiki/Copyleft
tldrlegal: https://tldrlegal.com/
Open Source Initiative에서 승인한 라이선스: https://opensource.org/licenses
GitHub UI를 통해: https://help.github.com/en/github/building-a-strong-community/adding-a-license-to-a-repository
이 현상에 관한 학술 연구: https://cmustrudel.github.io/papers/icse18badges.pdf
Shields.io: https://shields.io/
“크리스마스 트리” 효과: https://cmustrudel.github.io/announcement/badges
Hipster Logo Generator: https://hipsterlogogenerator.com/
Hatchful: https://hatchful.shopify.com/
Excalidraw: https://excalidraw.com
Awesome README: https://github.com/matiassingers/awesome-readme
프로필 README: https://github.com/abhisheknaiidu/awesome-github-profile-readme
GitHub 스타일 Markdown: https://github.github.com/gfm/
prettier: http://prettier.io/
husky와 pretty-quick: https://github.com/azz/pretty-quick
doctoc: https://github.com/thlorenz/doctoc
GitHub 액션: https://github.com/technote-space/toc-generator
ASCII Flow: http://asciiflow.com/
Monodraw: https://monodraw.helftone.com/
Excalidraw: https://excalidraw.com/
Draw.io: https://draw.io
VS Code: https://marketplace.visualstudio.com/items?itemName=hediet.vscode-drawio
Miro: https://miro.com
Matt Hova: https://twitter.com/Matt_Hova/status/1259940583793033216
문서를 프로젝트의 성숙도에 맞추십시오: https://www.swyx.io/writing/documentation-levels/
Muzzle: https://muzzleapp.com/
“건전한” 농담은 이곳입니다: https://github.com/15Dkatz/official_joke_api
개발자 농담은 이것을 참고하십시오: https://github.com/wesbos/dad-jokes
데브옵스 농담은 이곳을 참고하십시오: https://github.com/cardsagainstcontainers
공개 API 목록: https://github.com/public-api-lists/public-api-lists
Divya Tagtachian: http://twitter.com/shortdiv
동네 해산물 맛집: https://noti.st/shortdiv/N2JWhh/the-quest-for-serverless#s84HNCu
시카고의 딥디시 피자: https://www.youtube.com/watch?v=5tMduUTAMSU
재미있는 네덜란드어 말장난과 함께 GDPR을 다루는 발표: https://www.youtube.com/watch?v=Faaf5tzqvZg
밀크티를 활용한 데모: https://www.vuemastery.com/conferences/vueconf-us-2018/a-react-point-of-vue-divya-sasidharan/
졸로프 라이스: https://www.netlify.com/blog/2018/08/17/reflections-on-speaking-at-concatenate-conf-nigerias-first-international-developer-conference/
아바타: https://www.humaaans.com/
일러스트레이션: https://www.blackillustrations.com/
Slides.com처럼 시각적 요소가 많은 앱: https://www.youtube.com/watch?v=o0NtjY17v5w
Marcy Sutton: https://marcysutton.com/web-accessibility-resources
Lindsey Kopacz: https://www.a11ywithlindsey.com/blog
Jen Luker: https://github.com/knitcodemonkey/presentation-proposals
대중문화를 인용한 예: https://www.matthewgerstman.com/tech/ts-tricks-higher-order-components/
Pavel이라는 동료의 이야기를 들려주며: https://www.linkedin.com/pulse/continuous-deployment-docker-lessons-learned-stefana-muller
Superhuman 같은 앱: https://blog.superhuman.com/how-leaders-achieve-inbox-zero-2788fe8759bc?gi=687e80b5dd85
emptystat.es: http://emptystat.es/
데이비드 앨런의 『쏟아지는 일 완벽하게 해내는 법(Getting Things Done)』: https://gettingthingsdone.com/
예시: https://twitter.com/adamwathan/status/1250575985264734209
감사 편지: https://workingoutloud.com/blog//the-gratitude-letter
표지판 든 토끼(Sign bunny): https://www.npmjs.com/package/sign-bunny
Cowsay: http://npm.im/cowsay
피클 옷을 입고 피클을 나눠 주는 Design Pickle: https://www.chargify.com/blog/subscription-rockstars-design-pickle/
인쇄한 명함: https://twitter.com/sxywu/status/877357398054141952
책을 발사믹 식초처럼 졸여 낸 정수: https://www.sjo.com/dont-be-lazy/
상호성의 원칙: https://senseimarketing.com/the-principle-of-reciprocity-and-influence-marketing/
명예의 전당에 오른 미식축구 선수 로저 스타우바크: https://www.forbes.com/sites/shephyken/2016/02/27/theres-no-traffic-jam-on-the-extra-mile/

A.15 원칙: 백금률

칭찬 샌드위치: https://www.wikihow.com/Use-the-Compliment-Sandwich-to-Critique
사실 그다지 중요하지도 않습니다: https://nassimtaleb.org/tag/minority-rule/
이를 인식하고 도움을 요청하는 것이 여러분의 경력을 구할 수 있습니다: https://twitter.com/drose_999/status/1282864720572059649
Brian Chesky에게서 배운 것입니다: https://uxdesign.cc/applying-airbnbs-11-star-framework-to-the-candidate-experience-3f0b9c4e68a3
그레천 루빈의 네 가지 성향 프레임워크: https://www.businessinsider.com/gretchen-rubin-the-four-tendencies-framework-2017-4

A.16 원칙: 충분히 좋음

만족화(satisficing): https://en.wikipedia.org/wiki/Satisficing
극대화(maximizing): https://www.psychologytoday.com/us/blog/science-choice/201506/satisficing-vs-maximizing
Richard Gabriel이 처음 만든 용어입니다: https://en.wikipedia.org/wiki/Worse_is_better
여기: https://dreamsongs.com/RiseOfWorseIsBetter.html
존 메이너드 케인스(John Maynard Keynes): https://rwer.wordpress.com/2013/09/19/why-it-is-better-to-be-roughly-right-than-precisely-wrong/
엘스버그 역설: https://en.wikipedia.org/wiki/Ellsberg_paradox
『타이탄의 도구들(Tribe of Mentors)』에 실린 애덤 로빈슨(Adam Robinson)의 이야기: https://tribeofmentors.com/
존 B. 구디너프(John B. Goodenough): https://en.wikipedia.org/wiki/John_B._Goodenough

A.17 Principles: 제1원리 사고

똑똑한 사람들이 하는 가장 어리석은 일: https://medium.com/@byrnehobart/reasoning-from-first-principles-the-dumbest-thing-smart-people-do-46ff1cbba867
빅 오 표기법: https://rob-bell.net/2009/06/a-beginners-guide-to-big-o-notation
두 개발자가 Node.js의 기술적 장점에 대해 논하는 패러디 영상: https://www.youtube.com/watch?v=bzkRVzciAZg
모든 프로그래머가 알아야 할 지연 시간 수치: https://gist.github.com/jboner/2841832
생각의 속도는 고작 110m/s에 불과합니다: https://twitter.com/ID_AA_Carmack/status/1260698271422570497
냅킨 수학: https://github.com/sirupsen/napkin-math
암달의 법칙: https://en.wikipedia.org/wiki/Amdahl%27s_law
1: https://fs.blog/2018/04/first-principles/
2: https://jamesclear.com/first-principles
3: https://blog.useproof.com/first-principles/
Naval Ravikant: https://twitter.com/naval/status/944303595771412480
찰리 멍거: https://fs.blog/2018/04/first-principles/
일론 머스크: https://www.youtube.com/watch?v=NV3sBlRgzTI
간단한 PPE 프로그램: http://www.ox.ac.uk/admissions/undergraduate/courses-listing/philosophy-politics-and-economics
삼단논법: https://en.wikipedia.org/wiki/Syllogism
공리: https://en.wikipedia.org/wiki/Axiom
부정 명제는 증명할 수 없습니다: https://en.wikipedia.org/wiki/Evidence_of_absence
참이라고 믿는 것이 실제로는 참이 아닐 수 있습니다. 사회과학의 재현성 위기가 그 예입니다: https://en.wikipedia.org/wiki/Replication_crisis
확실성: https://en.wikipedia.org/wiki/Certainty
귀납의 문제: https://en.wikipedia.org/wiki/Problem_of_induction
우물 안 개구리: https://www.nyrb.com/products/the-frog-in-the-well
그 본질에 의문 제기하기: https://twitter.com/hbo/status/783075652060663808?lang=en
맨 인 블랙: https://www.quotes.net/mquote/61238
훅을 클로저로 이해하기: https://www.swyx.io/speaking/react-hooks/
Concurrent React 후속편: https://egghead.io/lessons/react-egghead-talks-concurrent-react-from-scratch?af=95qfq1
React Router에 관한 자료: https://tylermcginnis.com/build-your-own-react-router-v4/
Redux에 관해서는 이것: https://egghead.io/courses/getting-started-with-redux
하드웨어-소프트웨어 인터페이스에 관해서는 이것을 참고하십시오: https://www.nand2tetris.org/
직접 만들어 보는 Build Your Own X 프로젝트를 모아 둔 GitHub입니다!: https://github.com/danistefanovic/build-your-own-x
드레이크 방정식: https://en.wikipedia.org/wiki/Drake_equation
음악: https://www.lightnote.co/
컴퓨팅: https://www.nand2tetris.org/
요즘 시스템 사고(Systems Thinking)라는 이름으로 유행하고 있습니다: http://donellameadows.org/archives/leverage-points-places-to-intervene-in-a-system/
Jobs to Be Done(해결해야 할 일): https://jtbd.info/
무어의 법칙과 워스의 법칙으로 본 한계: https://www.swyx.io/writing/collapsing-layers/
개인 성장의 확장 요인을 모델링하기 위한 빅 오 표기법: https://www.swyx.io/writing/big-l-notation/
생산성을 위한 좋은 습관: https://www.franklincovey.com/the-7-habits/habit-2.html
Christine Yen은 Honeycomb.io가 하는 일의 방향을 잡기 위해 다음과 같은 질문을 즐겨 던집니다: https://youtu.be/VA0b6v9vaEM
돈 밸런타인의 질문: https://www.sequoiacap.com/article/remembering-don-valentine/
두 단어: https://www.swyx.io/writing/two-words
게임 vs 메타게임: https://www.swyx.io/writing/learn-in-private/
Will Larson: https://lethain.com/systems-thinking/
냅킨 수학(Napkin Math): https://github.com/sirupsen/napkin-math
지루한 기술(Boring Technology): http://boringtechnology.club/#23
Wait But Why의 일론 머스크 이야기: https://waitbutwhy.com/2015/11/the-cook-and-the-chef-musks-secret-sauce.html
닐 카카르(Neil Kakkar)의 제1원리 사고: https://neilkakkar.com/A-framework-for-First-Principles-Thinking.html
도넬라 메도즈의 레버리지 포인트: http://donellameadows.org/archives/leverage-points-places-to-intervene-in-a-system/
제1원리에 관한 Li Haoyi의 글: http://www.lihaoyi.com/post/FromfirstprinciplesWhyIbetonScalajs.html
선인장과 족제비에 대한 Venkatesh Rao의 글: https://www.ribbonfarm.com/2014/02/20/the-cactus-and-the-weasel/
믿음의 강도를 데시벨로 나타냅니다: https://news.ycombinator.com/item?id=24864782

A.18 원칙: 글쓰기

Google의 첫 엔지니어링 부사장 Urs Hölzle: https://www.linkedin.com/feed/update/urn:li:activity:6530173230102122496
Shit Happens(사고는 일어나기 마련): https://twitter.com/timbray/status/1260393664196403200
의사소통의 60-70%는 비언어적입니다: https://www.pgi.com/blog/2020/03/how-much-of-communication-is-really-nonverbal/
Matt Mullenweg에 따르면: https://ma.tt/2020/04/five-levels-of-autonomy/
원격 근무의 초능력: https://snir.dev/blog/remote-async-communication/
인접 기술: https://nesslabs.com/adjacent-skills
스티브 잡스: https://sriramk.com/memos/jobs-top-100.pdf
빌 게이츠: https://sriramk.com/memos/billgates-moviemaker.pdf
마크 저커버그: https://sriramk.com/memos/zuck-unity.pdf
글로 소통하는 문화를 장려하기: https://www.mcls.io/blog/encouraging-a-culture-of-written-communication
Gergely Orosz: https://blog.pragmaticengineer.com/on-writing-well/
Sahil Lavingia: https://www.youtube.com/watch?v=grXrGaT7DLw
Mark Erikson: https://blog.isquaredsoftware.com/2020/05/blogged-answers-why-i-write/
문서 주도 개발(Documentation Driven Development): https://gist.github.com/zsup/9434452
“식스 페이저” 서술형 메모: https://www.anecdote.com/2018/05/amazons-six-page-narrative-structure/
명확한 글쓰기와 명확한 사고는 함께 갑니다: https://slab.com/blog/jeff-bezos-writing-management-strategy/
John Resig은 다음에 그 공을 돌립니다: https://www.khanacademy.org/computing/computer-programming/html-js-jquery/jquery-dom-access/a/history-of-jquery
“가장 좋은 문서를 작성하는 사람이 승리합니다!”: https://saas.transistor.fm/episodes/taylor-otwell-didnt-even-like-computers
GitLab 핸드북: https://about.gitlab.com/company/culture/all-remote/handbook-first-documentation/
Google에는 이에 관한 훌륭한 강좌가 있습니다: https://developers.google.com/tech-writing
Don’t Go Home with Nothing(빈손으로 돌아가지 마십시오): https://training.kalzumeus.com/newsletters/archive/do-not-end-the-week-with-nothing
Twilio Voices: https://go.twilio.com/twilio-voices/
Digital Ocean: https://www.digitalocean.com/community/get-paid-to-write
Linode: https://www.linode.com/docs/contribute/
WonderProxy: https://wonderproxy.com/blog/looking-for-authors/
ClubHouse: https://clubhouse.io/clubhouse-write-earn-give-program/
Smashing Magazine: https://www.smashingmagazine.com/write-for-us/
CSS Tricks: https://css-tricks.com/guest-posting/
A List Apart: https://alistapart.com/about/contribute/
LogRocket: https://blog.logrocket.com/become-a-logrocket-guest-author-7d970eb673f9/
FloydHub: https://blog.floydhub.com/write-for-floydhub/
Stack Overflow: https://stackoverflow.blog/2020/01/27/blog-contributor-guidelines/
WhoPaysTechnicalWriters.com: https://whopaystechnicalwriters.com/
최다 기여자: https://stackoverflow.com/users/22656/jon-skeet
iOS와 Swift 전문가: https://flight.school/
블로그를 통해 만난 사람: https://blog.codinghorror.com/introducing-stackoverflow-com/
성공적인 오픈 소스 프로젝트 만들기: https://github.com/facebook/create-react-app/pull/489#issuecomment-244574463
Paul Graham: http://www.paulgraham.com/writing44.html
팀 페리스: https://www.youtube.com/watch?v=wCPbPMRNnvk&feature=youtu.be
Alex MacArthur: https://macarthur.me/posts/blog-for-your-own-sake
Joel Spolsky: https://stackoverflow.fogbugz.com/default.asp?W25795
코너 화이트 설리번: https://thetwentyminutevc.com/conorwhitesullivan/
글쓰기는 생각하기입니다: https://medium.learningbyshipping.com/writing-is-thinking-an-annotated-twitter-thread-2a75fe07fade
원문 출처 하이퍼링크: https://www.dw.com/en/hyperlink-when-tim-berners-lee-invented-the-world-wide-web-not-the-internet/a-19448729
Andrew Bosworth: https://boz.com/articles/writing-thinking
고무 오리 디버깅: https://en.wikipedia.org/wiki/Rubber_duck_debugging
채리티 메이저스(Charity Majors): https://charity.wtf/2019/10/30/a-managers-bill-of-responsibilities-and-rights/
앤디 그로브: https://www.amazon.com/High-Output-Management-Andrew-Grove-ebook/dp/B015VACHOK/
닐 디그래스 타이슨: https://www.perell.com/podcast/neil-degrasse-tyson
가장 잘 표현한 말입니다: http://www.paulgraham.com/essay.html
Emacs Org 모드: https://orgmode.org/
그들은 당신의 키 입력이라는 선물을 받을 자격이 있습니까: https://www.hanselman.com/blog/DoTheyDeserveTheGiftOfYourKeystrokes.aspx
블룸의 분류학: https://cft.vanderbilt.edu/guides-sub-pages/blooms-taxonomy/
내가 백엔드를 작성하는 방법: https://github.com/fpereiro/backendlore
에버그린 콘텐츠: https://ahrefs.com/blog/evergreen-content/
당신에게는 뻔한 것이 다른 사람에게는 놀라운 것입니다: https://sivers.org/obvious
무료 진: https://wizardzines.com/
아주 짧은 한입 크기의 TIL 모음: https://github.com/jbranchaud/til
왜 super(props)를 작성합니까?: https://overreacted.io/why-do-we-write-super-props/
Chris Coyier는 이렇게 말합니다: https://twitter.com/chriscoyier/status/925081793576837120
노트: https://twitter.com/karpathy/status/1159699558172991488
Troy Hunt: https://www.youtube.com/watch?v=-MUhcgXBj_A&feature=youtu.be
조용했던 네 달: https://www.youtube.com/watch?v=7HI5CISSPms&feature=youtu.be
세상의 온갖 주제에 대해 수년간 블로그를 써야 했습니다: https://www.youtube.com/watch?v=-MUhcgXBj_A
주목받을 때까지 충분히 오래 버티십시오: https://nathanbarry.com/endure/
폴라니의 역설: https://en.wikipedia.org/wiki/Polanyi%E2%80%99s_paradox
KeySearch: https://keysearch.co/research
Monica Lent의 무료 블로깅 강좌: https://bloggingfordevs.com/
스카이스크래퍼 기법: https://ahrefs.com/blog/skyscraper-technique/
Write Epic Shit(끝내주는 글을 쓰십시오): https://fizzle.co/sparkline/write-epic-shit
CSS Grid 완벽 가이드: https://css-tricks.com/snippets/css/complete-guide-grid/
프로그래머가 이름에 대해 믿는 잘못된 통념: https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/
매일 블로그를 쓰며 얻은 SEO 교훈: https://flaviocopes.com/blog-seo/
글쓰기의 다섯 기둥: https://www.perell.com/blog/the-ultimate-guide-to-writing-online#block-yui_3_17_2_1_1555023647237_47521
흥미로운 사람이 되려면 (다른 사람에게) 관심을 가지십시오: https://dramatictrainingsolutions.com/interesting-interested-dale-carnegie/
데릭 시버스(Derek Sivers): https://robhope.com/yo-sivers
이키가이: https://medium.com/thrive-global/ikigai-the-japanese-secret-to-a-long-and-happy-life-might-just-help-you-live-a-more-fulfilling-9871d01992b7
자주 언급됨: https://nav.al/possible-careers
제이컵 캐플런모스: https://jacobian.org/2009/nov/11/technical-style/
단 한 번의 쉬운 단계로 궁극의 블로그 성공을 거두는 법: https://blog.codinghorror.com/how-to-achieve-ultimate-blog-success-in-one-easy-step/
하루에 형편없는 글 두 페이지: https://99u.adobe.com/articles/7252/tim-ferriss-on-the-creative-process-and-getting-your-work-noticed
모닝 페이지: https://littlecoffeefox.com/morning-pages-changed-life/
브라이언 코펠먼(Brian Koppelman)은 이렇게 합니다: https://fs.blog/knowledge-project/brian-koppelman/
그는 하루에 1000단어씩 쓰기로 다짐했습니다: https://nathanbarry.com/commitment-changed-career/
느리지만 꾸준한 진전만이 큰일을 이루는 유일한 방법입니다: https://nathanbarry.com/365/
스티브 예기(Steve Yegge): https://gist.github.com/chitchcock/1281611
Patrick McKenzie: https://kalzumeus.com/
Dan Luu: https://danluu.com/
닉 매기울리(Nick Maggiuli): https://www.youtube.com/watch?v=7HI5CISSPms&feature=youtu.be
Addy Osmani의 말을 인용합니다: https://twitter.com/addyosmani/status/1260779133769924608
750 Words: https://750words.com/
Diary Email: https://diaryemail.com/
WriteNext: http://writenext.io/
Commit: https://www.producthunt.com/posts/commit
No Zero Days: https://www.reddit.com/r/NonZeroDay/
글쓰기 프롬프트(Writing Prompts): https://www.reddit.com/r/WritingPrompts/
이 책의 자체 커뮤니티: https://twitter.com/coding_career
Pat Walls처럼 매일 블로그 글 쓰기: https://patwalls.com/this-new-blog

A.19 원칙: 내려놓은 것을 집어

스케치 노트: https://illustrated.dev/
Tan Li Hau: https://twitter.com/lihautan
Svelte 코드베이스의 TODO 집어 들기: https://www.youtube.com/watch?v=NSUa1124ahs
자아를 작게 유지하십시오: https://www.swyx.io/speaking/kentcdodds-podcast/
지프의 법칙: https://en.wikipedia.org/wiki/Zipf%27s_law
서브레딧: https://www.reddit.com/r/reactjs
트윗 노출 200~300만 회: https://www.swyx.io/writing/10000-loose-fans/
무작위로 트윗함: https://twitter.com/CesarKuriyama/status/331652847806595072
결국 Cesar의 앱을 자신의 명작 영화 〈아메리칸 셰프(Chef)〉에 등장시켰습니다: https://www.indiehackers.com/podcast/141-cesar-kuriyama-of-1-second-everyday
니르 이얄(Nir Eyal)의 훅(Hooked) 모델을 읽어 보십시오: https://www.nirandfar.com/how-to-manufacture-desire/
저를 태그해 주십시오: https://twitter.com/swyx

A.20 전략: 서론 전략

제임스 P. 카스(James P. Carse)의 『유한 게임과 무한 게임(Finite and Infinite Games)』: https://en.wikipedia.org/wiki/Finite_and_Infinite_Games
루딕 오류(the Ludic Fallacy): https://en.wikipedia.org/wiki/Ludic_fallacy
한 구글 직원의 말을 빌리면 다음과 같습니다: https://news.ycombinator.com/item?id=5496914
Google Plus에서 Vic Gundotra 밑에서 일한 경험에 대해: https://techcrunch.com/2018/10/15/a-former-google-ui-designer-suggests-inept-management-played-a-role-in-the-networks-demise-beyond-facebooks-impact/
Google 알고리즘 업데이트 이후 진행된 Digg의 v4 재작성에 관하여: https://news.ycombinator.com/item?id=22835645
API의 위 또는 아래: https://rein.pk/replacing-middle-management-with-apis
헨리 민츠버그(Henry Mintzberg): https://www.mindtools.com/pages/article/mintzberg-5ps.htm
바로 그 주제를 다룬 책이 있습니다: https://jlzych.com/2018/06/27/notes-from-good-strategy-bad-strategy/
되돌리려고 하지 마십시오: https://twitter.com/LT3000Lyall/status/1271781515916013568
매몰 비용: https://en.wikipedia.org/wiki/Sunk_cost#Fallacy_effect
문화는 전략을 아침 식사로 먹어 치운다: https://www.managementcentre.co.uk/culture-eats-strategy-for-breakfast/

A.21 전략: 배움의 기어

비유적인 고무 오리: https://en.wikipedia.org/wiki/Rubber_duck_debugging
점들은 인생의 훨씬 나중에야 비로소 연결할 수 있습니다: https://www.youtube.com/watch?v=D1R-jKKp3NA
블룸의 분류학: https://cft.vanderbilt.edu/guides-sub-pages/blooms-taxonomy/
100 Days of Code: https://www.100daysofcode.com/
Samantha Ming: https://twitter.com/samantha_ming
Hiro Nishimura: http://awsnewbies.com/
Julia Evans: https://wizardzines.com/
Lin Clark: https://code-cartoons.com/
Tobias Koppers와 Webpack: https://www.youtube.com/watch?v=k86Z_6_BJy0
CSS와 함께한 Jen Simmons: https://vimeo.com/316326187
CSS를 다루는 Lea Verou: https://cult.honeypot.io/originals/a-journey-into-software-development-with-lea-verou/
Vue와 함께한 Evan You: https://www.youtube.com/watch?v=OrxmtDw4pVI
Node를 만든 Ryan Dahl: https://www.youtube.com/watch?v=SAc0vQCC6UQ
Deno: https://www.youtube.com/watch?v=M3BM9TB-8yA

A.22 전략: 스페셜리스트 또는 제너럴리스트

허수아비(strawman): https://en.wikipedia.org/wiki/Straw_man
Platform as a Service(서비스형 플랫폼): https://en.wikipedia.org/wiki/Platform_as_a_service
풀스택 팀: https://medium.com/@AngelJaime/transitioning-to-full-stack-product-teams-and-what-did-we-learn-along-the-way-96a97a8b08d5
Valve가 직원 핸드북에서 정의한 내용: https://www.businessinsider.com/game-developer-valve-hiring-strategy-2014-12?IR=T
스콧 애덤스(Scott Adams)는 우리가 두 가지 이상의 분야에서 매우 뛰어난 실력을 갖춰야 한다고 말합니다: https://dilbertblog.typepad.com/the_dilbert_blog/2007/07/career-advice.html
제프 스콧이 제게 보낸 답장: https://twitter.com/JeffWScott/status/1251493372717600768
Range: https://www.amazon.com/Range-Generalists-Triumph-Specialized-World/dp/0735214484
첫 번째 더닝 크루거 정점: https://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
팀 페리스: https://thriveglobal.com/stories/6-brilliant-thoughts-from-tools-of-titans-by-tim-ferriss/
그가 모르는 것들: https://overreacted.io/things-i-dont-know-as-of-2018/
Cory House는 컨설팅 문의가 15배 증가했습니다: https://youtu.be/Y4wnbkatj20?t=1311

A.23 전략: 기술에 베팅하기

the Changelog: https://changelog.com/nightly
Mikeal Rogers의 일간 뉴스레터: https://github.com/mikeal/daily
Tiobe Index: https://www.tiobe.com/tiobe-index/
GitHub Octoverse: https://octoverse.github.com/
StackOverflow: https://insights.stackoverflow.com/survey/2019
npm: https://www.businesswire.com/news/home/20190423005225/en/npm-Survey-What%E2%80%99s-New-JavaScript-2019
State of JavaScript: https://stateofjs.com/
ExplodingTopics: https://explodingtopics.com/
RedditList: http://redditlist.com/
Echobind: https://blog.echobind.com/the-roi-of-self-directed-investment-time-for-software-engineers-a9ad633f882
두 번째 시스템 증후군(Second System Syndrome): https://en.wikipedia.org/wiki/Second-system_effect
다음은 UI 엔지니어링을 위한 목록입니다: https://overreacted.io/the-elements-of-ui-engineering/
즐겨 설명하는 내용입니다: https://www.youtube.com/watch?v=l7QdIQVTly0
과학혁명의 구조(The Structure of Scientific Revolutions): https://en.wikipedia.org/wiki/The_Structure_of_Scientific_Revolutions
패러다임 전환: https://en.wikipedia.org/wiki/Paradigm_shift
VHS 대 베타맥스: https://en.wikipedia.org/wiki/Videotape_format_war
React + Redux + TypeScript 대 Elm: https://www.reddit.com/r/javascript/comments/2z5lci/why_are_people_using_react_over_elm/
이에 대한 훌륭한 비유: https://shoptalkshow.com/418/
콜 옵션: https://www.investopedia.com/terms/c/calloption.asp
Jessie Frazelle: https://www.codenewbie.org/podcast/can-you-do-open-source-full-time
Charity Majors: https://twitter.com/mipsytipsy/status/1247705319339368448
Ryan Florence: https://softwareengineeringdaily.com/2020/03/03/react-fundamentals-with-ryan-florence/
Kelsey Hightower: https://www.lastweekinaws.com/podcast/screaming-in-the-cloud/the-staying-power-of-kubernetes-with-kelsey-hightower/
데니스 가보르: https://quoteinvestigator.com/2012/09/27/invent-the-future/
Joyent CTO 브라이언 캔트릴(Bryan Cantrill): https://www.youtube.com/watch?v=9QMGAtxUlAc&t=2225s
“인터넷 아키텍처”는 보안과 성능보다 가용성과 단순성을 중시합니다: https://www.swyx.io/writing/networking-essentials-architecture-and-principles-2g5e/
C++의 목표와 우선순위: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/p2137r0.html
Angular 팀의 대규모 이탈: https://medium.com/@jeffbcross/jeffs-letter-to-the-angular-team-and-community-5367934a16c9
TJ Holowaychuk의 Node.js 이탈: https://medium.com/code-adventures/farewell-node-js-4ba9e7f3e52b
Guido van Rossum의 Python 리더십 사임: https://hub.packtpub.com/why-guido-van-rossum-quit/

A.24 Strategy: 이익 센터 대 비용 센터

Microsoft Research: https://www.microsoft.com/en-us/research/
Google X: https://x.company/
오늘날 기업 연구소는 예전보다 훨씬 적습니다: https://blog.dshr.org/2020/05/the-death-of-corporate-research-labs.html

A.25 전략: 커리어 래더

관리자 1명당 엔지니어 6~8명: https://lethain.com/sizing-engineering-teams/
피터의 법칙: https://en.wikipedia.org/wiki/Peter_principle
드레이퍼스의 지도된 기술 습득 모델(Dreyfus model of Directed Skill Acquisition): https://www.kitchensoap.com/2012/10/25/on-being-a-senior-engineer/
스태프 엔지니어의 4가지 유형: https://lethain.com/staff-engineer-archetypes/
반대하되 따르기(disagree and commit): https://en.wikipedia.org/wiki/Disagree_and_commit
성장 마인드셋: https://www.brainpickings.org/2014/01/29/carol-dweck-mindset/
Fog Creek: https://www.joelonsoftware.com/2009/02/13/fog-creek-professional-ladder/
Rent the Runway: https://dresscode.renttherunway.com/blog/ladder
스프레드시트: https://docs.google.com/spreadsheets/d/1k4sO6pyCl_YYnf0PAXSBcX776rNcTjSOqDxZ5SDty-4/edit?usp=sharing
Artsy: https://artsy.github.io/blog/2015/04/03/artsy-engineering-compensation-framework/
CapGemini UK: https://capgemini.gitbooks.io/grade-ladder/content/
Basecamp: https://basecamp.com/handbook/appendix-05-titles-for-programmers
Thumbtack: https://engineering.thumbtack.com/how-we-built-an-engineering-job-ladder-from-the-ground-up/
스프레드시트: https://docs.google.com/spreadsheets/d/15ACBs-crUHnqf1wANUQwX9oZIDOi5tvJJXGWpKTcf00/edit#gid=0
CircleCI: https://circleci.com/blog/why-we-re-designed-our-engineering-career-paths-at-circleci/
스프레드시트: https://docs.google.com/spreadsheets/d/131XZCEb8LoXqy79WWrhCX4sBnGhCM1nAIz4feFZJsEo/edit#gid=0
Envoy: https://github.com/envoy/Engineering/blob/master/engineering_bands.md
Financial Times: https://medium.com/ft-product-technology/improving-our-career-map-for-engineers-4210185c6246
웹앱: https://engineering-progression.ft.com/
API: https://engineering-progression.ft.com/docs/api/
Patreon: https://patreonhq.com/how-patreon-levels-engineers-a28a3491ae6a
Meetup: https://github.com/meetup/engineering-roles/
Socialbakers: https://github.com/Socialbakers/engineeringroles
Medium: https://medium.com/s/engineering-growth-framework/engineering-growth-tracks-b1fad620787e
gist: https://gist.github.com/david206/b8dceddd687bb2c60805c9669cc89eaa
Starling 소프트웨어: http://www.starling-software.com/employment/programmer-competency-matrix.html
Hacker News: https://news.ycombinator.com/item?id=4626695
Kickstarter: https://gist.github.com/jamtur01/aef437a79fee5a9cefdc
Brandwatch: https://docs.google.com/document/d/1PCj7f-91G6dGdIlfDpCHcm68L80hRELk00eO-gZvh1o/edit
이 스프레드시트의 IC 및 관리직: https://docs.google.com/spreadsheets/d/1weNoeSUfHYOHy9sHKad_ax6qrVXNFlP4ieTwaRll70M/edit#gid=0
Spotify: https://labs.spotify.com/2016/02/15/spotify-technology-career-steps/
Chuck Groom: https://blog.usejournal.com/the-software-engineering-job-ladder-4bf70b4c24f3
칸 아카데미: http://engineering.khanacademy.org/posts/career-development.htm
doc: https://docs.google.com/document/d/1qr0d05X5-AsyDYqKRCfgGGcWSshTMd_vfTggfhDpbls/edit
Monzo: https://progression.monzo.com/engineering/web
Square: https://developer.squareup.com/blog/squares-growth-framework-for-engineers-and-engineering-managers/
스프레드시트: https://docs.google.com/spreadsheets/d/12h50IYqd7fsO7tJ0l1OuHYbz5vN2d24a8EIDFhu2AZQ/edit#gid=2035430096
Buffer: https://buffer.com/resources/engineering-career-framework/
Progression.fyi: https://www.progression.fyi/
직함과 직급에 관한 Holloway 가이드: https://www.holloway.com/s/trh-job-titles-levels-fundamentals-for-software-engineering

A.26 전략: 기술 전략

지난 Business of Software(소프트웨어 비즈니스) 콘퍼런스 강연의 풍부한 목록: https://businessofsoftware.org/videos/
직접 개발할 것인가, 구매할 것인가: https://www.scalyr.com/blog/build-vs-buy/
Google 지도의 위성 보기가 하마터면 “Bird Mode”라는 이름이 될 뻔했던 이야기를 읽어 보십시오: https://9to5google.com/2019/02/25/sergey-brin-google-maps-bird-mode/
Marc Andreesen은 “왜 소프트웨어가 세상을 집어삼키고 있는가(Why Software is Eating the World)”라는 글을 썼습니다: https://a16z.com/2011/08/20/why-software-is-eating-the-world/
헬스케어: https://a16z.com/2019/08/16/software-eaten-world-healthcare/
바이오테크: https://a16z.com/2019/08/23/software-eats-healthcare-bio-next/
암호화폐: https://a16z.com/2019/08/29/internet-past-crypto-future-crypto-regulatory-summit/
API 경제: https://a16z.com/2018/03/13/api-economy-why-what-how/
자신의 경력 동안 컴퓨팅 산업에서 일어난 변화를 다음과 같이 설명했습니다: https://www.goodreads.com/book/show/66863.Only_the_Paranoid_Survive_Lessons_from_the_CEO_of_INTEL_Corporation
클레이튼 크리스텐슨은 이를 다음과 같이 설명했습니다: https://claytonchristensen.com/books/the-innovators-solution/
Slack 대 Microsoft Teams: https://stratechery.com/2020/the-slack-social-network/
Apple Silicon: https://mondaynote.com/apple-silicon-the-passing-of-wintel-79a5ef66ad2b
소프트웨어로 돈을 버는 방법은 두 가지뿐입니다. 번들링과 언번들링입니다.: https://hbr.org/2014/06/how-to-succeed-in-business-by-bundling-and-unbundling
거대한 언번들링: https://a16z.com/2019/09/11/platforms-verticals-unbundling/
Craigslist: https://www.cbinsights.com/research/craigslist-unbundling/
Excel: https://tomtunguz.com/unbundling-of-excel/
칩 설계 산업: https://stratechery.com/2020/chips-and-geopolitics/
케이블 TV: https://twitter.com/benedictevans/status/1271767978200182784
LinkedIn: https://a16z.com/2019/09/11/platforms-verticals-unbundling/
은행: https://www.cbinsights.com/research/disrupting-banking-fintech-startups/
프린시펄-에이전트 문제(Principal-Agent Problem): https://www.intelligenteconomist.com/principal-agent-problem/
천 회 노출당 비용(Cost Per Mille): https://en.wikipedia.org/wiki/Cost_per_mille
클릭당 비용(Cost per Click): https://sproutsocial.com/glossary/cost-per-click/
정말 방대한 마케팅 기술 모음: https://chiefmartec.com/2019/04/marketing-technology-landscape-supergraphic-2019/
Wirecutter: https://thewirecutter.com/
the Points Guy: https://thepointsguy.com/
제휴 마케팅: https://neilpatel.com/what-is-affiliate-marketing/
Status as a Service(서비스로서의 지위): https://www.eugenewei.com/blog/2019/2/19/status-as-a-service
리드 호프먼의 LinkedIn 시리즈 B 피치 덱: https://www.reidhoffman.org/linkedin-pitch-to-greylock/
47 U.S.C. § 230: https://en.wikipedia.org/wiki/Section_230_of_the_Communications_Decency_Act
IaaS/PaaS/SaaS: https://www.bmc.com/blogs/saas-vs-paas-vs-iaas-whats-the-difference-and-how-to-choose/
고정비에서 변동비로: https://www.investopedia.com/ask/answers/032515/what-difference-between-variable-cost-and-fixed-cost-economics.asp
매출총이익률(gross margin): https://en.wikipedia.org/wiki/Gross_margin
마케팅 퍼널: https://openviewpartners.com/blog/the-ultimate-saas-funnel-guide/
전환율: https://www.custify.com/7-ways-saas-companies-can-increase-conversion-rates
이탈률(churn): https://en.wikipedia.org/wiki/Churn_rate
좌석당 과금(per-seat): https://en.wikipedia.org/wiki/Per-seat_license
가치 지표(value metrics): https://www.chargebee.com/blog/saas-pricing-and-value-metrics/
1999년 유명한 “No Software(소프트웨어는 이제 그만)” 캠페인으로 이를 소개했습니다: https://retool.com/blog/salesforce-for-engineers/
네트워크 효과: https://www.investopedia.com/terms/n/network-effect.asp
무에서 돈 만들기: http://abovethecrowd.com/2019/02/27/money-out-of-nowhere-how-internet-marketplaces-unlock-economic-wealth/
더 많은 내용은 이 목록을 참고하십시오: https://a16z.com/2020/02/18/marketplace-100/
유동성: https://medium.com/point-nine-news/wtf-is-marketplace-liquidity-f2caca3802c0
다른 어느 곳보다 빠르게: https://medium.com/@ai/an-important-marketplace-metric-search-to-fill-6f2b31aa1051
테이크 레이트(take rate): https://www.fool.com/investing/2017/01/08/why-the-take-rate-is-so-important-in-e-commerce.aspx
총 거래액(Gross Merchandise Volume): https://en.wikipedia.org/wiki/Gross_merchandise_volume
Gumroad는 3.5%의 수수료를 부과합니다: https://gumroad.com/features/pricing
Apple과 Google의 앱 스토어는 30%를 가져갑니다: https://www.theregister.co.uk/2018/08/29/app_store_duopoly_30_per_cent/
마켓플레이스의 계층 구조: https://medium.com/@sarahtavel/the-hierarchy-of-marketplaces-introduction-and-level-1-983995aa218e
광고 사업 전체: https://www.marketingdive.com/news/amazons-ad-sales-surge-41-to-record-48b/571467/
구독 비즈니스 전체: https://en.wikipedia.org/wiki/Amazon_Prime
스티브 잡스는 마크 베니오프에게 Salesforce AppExchange에 대한 아이디어를 주었습니다: https://retool.com/blog/salesforce-for-engineers/
자산 경량화(asset light): https://www.monkshill.com/views/2019/3/5/bits-vs-atoms-why-we-invest-in-asset-light-businesses
Zappos: https://www.zappos.com/c/shipping-and-returns
100만 달러 배상 책임 보험 프로그램: https://techcrunch.com/2014/11/20/airbnb-rolls-out-million-dollar-liability-insurance-program-for-hosts/
Lenny Rachitsky의 연구: https://www.lennyrachitsky.com/p/maintaining-quality-kickstarting
완전 경쟁: https://a16z.com/2015/02/24/managing-tensions-in-online-marketplaces/
수요 제약 또는 공급 제약: https://www.lennyrachitsky.com/p/how-to-know-if-youre-supply-or-demand
마켓플레이스 공급을 늘리는 방법을 백과사전처럼 정리해 두기: https://andrewchen.co/grow-marketplace-supply/
도구를 보고 왔다가 네트워크 때문에 머무르게 됩니다: https://cdixon.org/2015/01/31/come-for-the-tool-stay-for-the-network
소비자 직접 판매(Direct to Consumer): https://www.cbinsights.com/research/direct-to-consumer-retail-strategies/
Julian Garamendy: https://twitter.com/JulianGWeb
게임은 거대한 메가트렌드입니다: https://www.matthewball.vc/all/7reasonsgaming
차마스 팔리하피티야가 인용한 빌 게이츠의 말: https://stratechery.com/2018/the-bill-gates-line/
Ben Thompson에 따르면: https://stratechery.com/2017/amazons-operating-system/
생각을 바꾸었습니다: https://stratechery.com/2018/techs-two-philosophies/
Matthew Ball의 장대한 Epic Games 입문서: https://www.matthewball.vc/all/epicgamesprimermaster
세 가지 특성을 다음과 같이 정의합니다: https://www.developerecosystem.com/posts/wtf-is-a--platform/
자연 독점: https://www.investopedia.com/terms/n/natural_monopoly.asp
스탠 시(Stan Shih): https://en.wikipedia.org/wiki/Stan_Shih
스마일 커브: https://en.wikipedia.org/wiki/Smiling_curve
자율주행차: https://stratechery.com/2017/intel-mobileye-and-smiling-curves/
테일러 스위프트: https://stratechery.com/2014/differentiation-value-creation-internet-age/
롤업: https://corporatefinanceinstitute.com/resources/knowledge/deals/roll-up-strategy/
애그리게이션 이론(Aggregation Theory): https://stratechery.com/2015/aggregation-theory/
Ben Thompson 저: https://stratechery.com/2017/defining-aggregators/
한계 비용: https://en.wikipedia.org/wiki/Marginal_cost
Ben이 자신의 사이트에 쓴 글: https://stratechery.com/2019/a-framework-for-regulating-competition-on-the-internet/
마음의 자전거: https://youtu.be/4x8wTj-n33A
오픈 코어 모델: https://coss.media/open-core-definition-examples-tradeoffs/
대규모 라이선스 변경(the Great Relicensing): https://coss.media/open-source-creator-licensing-fundamentals/
단위 경제성(unit economics): https://www.quora.com/What-are-unit-economics
부트스트랩(bootstrapped): https://www.investopedia.com/terms/b/bootstrap.asp
Joel Spolsky가 이 아이디어를 잘 소개하고 있습니다: https://www.joelonsoftware.com/2000/05/12/strategy-letter-i-ben-and-jerrys-vs-amazon/
모든 협업 앱은 이메일 기능을 원합니다: http://www.catb.org/jargon/html/Z/Zawinskis-Law.html
사용자 생성 콘텐츠: https://en.wikipedia.org/wiki/User-generated_content
모든 B2B 앱은 대시보드를 원합니다: https://www.saastr.com/want-go-upmarket-need-great-dashboard/

A.27 전략: 전략적 인식

성공하는 사람들의 7가지 습관: https://en.wikipedia.org/wiki/The_7_Habits_of_Highly_Effective_People
제임스 클리어(James Clear)의 말을 바꾸어 표현하면: https://twitter.com/JamesClear/status/1283939089260195840
Technology Radar: https://www.thoughtworks.com/radar/
This Week in Machine Learning: https://twimlai.com/
잔카를로 로타: http://themattheweffect.org/tag/richard-feynman/
그가 가장 좋아하는 12가지 문제: https://joebalcom.blog/12-favorite-problems//
Adam Robinson은 즐겨 이렇게 말합니다: https://ma.tt/2017/11/adam-robinson-on-understanding/
당신과 당신의 연구(You and Your Research): https://www.youtube.com/watch?v=a1zDuOPkMSw&feature=youtu.be
정보를 놓칠까 하는 두려움: https://learning-from-leaders.de/get-rid-of-the-fear-of-missing-information/
폴 사포(Paul Saffo): https://www.optimize.me/quotes/paul-saffo/20764-point-of-view-is-that-quintessentially/
Charity Majors, Honeycomb CTO: https://twitter.com/mipsytipsy/status/1247705319339368448
MooTools 마피아: https://twitter.com/viviancromwell/status/793515757212622848
캐즘 마케팅(Crossing the Chasm): https://en.wikipedia.org/wiki/Crossing_the_Chasm
AI 겨울: https://en.wikipedia.org/wiki/AI_winter
카를로타 페레스(Carlota Perez)는 평생 이 주제를 연구해 왔습니다: https://avc.com/2015/02/the-carlota-perez-framework/
저는 이를 적용하여 React 메타프레임워크의 부상을 설명했습니다: https://www.swyx.io/writing/react-distros/
워스의 법칙: https://en.wikipedia.org/wiki/Wirth%27s_law
골드러시 때는 삽을 파십시오: https://www.quora.com/What-are-some-examples-of-sell-shovels-in-a-gold-rush
조엘 스폴스키(Joel Spolsky): https://www.joelonsoftware.com/2002/06/12/strategy-letter-v/
Gwern Branwen: https://www.gwern.net/Complement
워들리 맵: https://blog.gardeviance.org/2015/02/an-introduction-to-wardley-value-chain.html
1: https://www.youtube.com/watch?v=NnFeIt-uaEc
2: https://www.youtube.com/watch?v=JMlFv2Sod54
3: https://www.youtube.com/watch?v=eIc2Gmmio3c
로마 클럽: https://en.wikipedia.org/wiki/Club_of_Rome
성장의 한계(Limits to Growth): https://en.wikipedia.org/wiki/The_Limits_to_Growth
12가지 레버리지 포인트: http://donellameadows.org/archives/leverage-points-places-to-intervene-in-a-system/
이후 책으로도 출간되었습니다: https://www.amazon.com/Thinking-Systems-Donella-H-Meadows/dp/1603580557
엔지니어링 관리에 시스템 사고 적용하기: https://lethain.com/tags/systems-thinking/
내려놓은 것을 집어: https://www.swyx.io/writing/learn-in-public-hack/
Daniel Miessler는 홈 랩을 갖출 것을 강력히 권장합니다: https://danielmiessler.com/blog/build-successful-infosec-career/#lab
rupa/z: https://github.com/rupa/z
다소 논란의 여지가 있음: https://www.nytimes.com/2019/11/26/style/narrative-violation-venture-capital-tech.html
네오가 똑같은 고양이를 두 번 보는 장면으로, 매트릭스의 글리치를 나타냅니다: https://www.youtube.com/watch?v=icID__07xBI
미래에 살기: http://www.paulgraham.com/startupideas.html

A.28 전략: 메가트렌드

역사의 종말 착각(End of History illusion): https://www.youtube.com/watch?v=XNbaR54Gpj4
Paul Graham의 말을 빌리면 다음과 같습니다: http://www.paulgraham.com/startupideas.html
Blackrock은 다음과 같이 정의합니다: https://www.blackrock.com/sg/en/investment-ideas/themes/megatrends
허영 지표(vanity metric): https://www.tableau.com/learn/articles/vanity-metrics
전체 시장 규모(Total Addressable Market): https://en.wikipedia.org/wiki/Total_addressable_market
보이지 않는 점근선: https://www.eugenewei.com/blog/2018/5/21/invisible-asymptotes
오디오: https://www.matthewball.vc/all/audiotech
암호화폐: https://a16z.com/2020/04/30/crypto-fund-ii/
가상 현실: https://en.wikipedia.org/wiki/Oculus_VR#Facebook_acquisition_and_chief_scientist_designation
양자 우월성: https://en.wikipedia.org/wiki/Quantum_supremacy
딥러닝: https://www.youtube.com/watch?v=RM-Jtc2ryfM
윌리엄 깁슨: https://quoteinvestigator.com/2012/01/24/future-has-arrived/
잠버 형제(Samwer Brothers): https://www.wired.co.uk/article/inside-the-clone-factory
하이구이(海归): https://en.wikipedia.org/wiki/Haigui
중국의 YouTube: https://www.youku.com/
중국의 구글: https://www.baidu.com/
중국의 Amazon: https://www.alibaba.com/
중국의 익스피디아: https://www.ctrip.com/
중국의 Uber: https://www.didiglobal.com/
한층 더 긴밀한 유대: https://www.youtube.com/watch?v=v6q14yBlpjY
TSMC의 모리스 창: https://en.wikipedia.org/wiki/Morris_Chang
Nvidia의 젠슨 황: https://en.wikipedia.org/wiki/Jensen_Huang
Airbnb가 TypeScript를 도입했다고 발표했습니다: https://www.youtube.com/watch?v=P-J9Eg7hJwE
Shopify의 React Native 전환: https://engineering.shopify.com/blogs/engineering/react-native-future-mobile-shopify
설문 조사 결과 종합하기: https://www.swyx.io/speaking/intro-to-typescript/
비디오 게임이 세상을 장악할 7가지 이유: https://www.matthewball.vc/all/7reasonsgaming
팟캐스트: https://medium.com/@awilkinson/howard-stern-is-getting-ripped-off-1b721cc2f3f2
뉴스레터: https://substack.com/
동영상 강의: https://teachable.com/
성인 콘텐츠: https://onlyfans.com/
전자책: http://gumroad.com/
노코드 업체와 RPA 제공업체: https://www.swyx.io/writing/no-code-rpa/
Fathom: https://usefathom.com/
Fastmail: https://www.fastmail.com/
Hey: https://hey.com/
DuckDuckGo는 매년 50%씩 성장하고 있습니다: https://duckduckgo.com/traffic
일부: https://www.zukunftsinstitut.de/index.php?id=1532
기타: https://dcgross.com/2020-startup-themes
샘 올트먼의 아이디어 발상법: https://blog.samaltman.com/idea-generation
너무 늦었다는 불길한 예감이 들었습니다: https://www.youtube.com/watch?v=cldkL157x_o
실리콘밸리로 이주했습니다: https://nymag.com/intelligencer/2014/10/marc-andreessen-in-conversation.html
소셜, 위치 기반, 모바일: https://neilpatel.com/blog/solomo/
그들은 이미 존재하는 수많은 미디어 공유 앱과 맞서야 했습니다: http://milesgrimshaw.com/sequoia-investment-memo/
최후 진입자(last mover): https://techcrunch.com/2015/06/17/the-last-mover-advantage/

A.29 전술: 협상

Fearless Salary Negotiation: https://www.amazon.com/Fearless-Salary-Negotiation-step-step/dp/0692568689
Glassdoor: https://glassdoor.com
Levels.fyi: https://www.levels.fyi/
Team Blind: https://www.teamblind.com/
/r/cscareerquestions: https://www.reddit.com/r/cscareerquestions/
Buffer: https://buffer.com/salary/senior-customer-advocate/average/
Krit: https://docs.google.com/spreadsheets/d/1JIRE_t0jrFt1jQ1Awxsbq95LNQ3rqjN0Wi3dQck9s0s/edit#gid=1738148510
GitLab: https://about.gitlab.com/handbook/total-rewards/compensation/compensation-calculator/calculator/
여성에게 남성 동료보다 약 20% 적은 급여를 지급합니다: https://twitter.com/Bosefina/status/1269338890067984384
협상 결렬 시 최선의 대안(BATNA): https://en.wikipedia.org/wiki/Best_alternative_to_a_negotiated_agreement
연봉 협상: https://www.kalzumeus.com/2012/01/23/salary-negotiation/
예시 대화 스크립트는 여기에서 볼 수 있습니다: https://www.yesware.com/blog/sales-call-script/
연봉 협상에 실제로 사용된 대화 스크립트는 여기에 있습니다: https://www.accidentalciso.net/post/promotions-the-reward-for-good-work-is-more-work
Google과 Facebook의 사례: https://twitter.com/patio11/status/1269539448196173825
협상에서의 미러링: https://www.masterclass.com/classes/chris-voss-teaches-the-art-of-negotiation/chapters/mirroring
주식 보상에 대한 오픈 가이드(The Open Guide to Equity Compensation): https://github.com/jlevy/og-equity-compensation
부트캠프를 마치고 Airbnb로부터 25만 달러의 제안을 협상해 냈습니다: https://haseebq.com/farewell-app-academy-hello-airbnb-part-ii/
10가지 규칙: https://www.freecodecamp.org/news/ten-rules-for-negotiating-a-job-offer-ee17cccbdab6/
Fearless Salary Negotiation: https://www.amazon.com/Fearless-Salary-Negotiation-step-step/dp/0692568689
생각할 시간을 요청하십시오: https://fearlesssalarynegotiation.com/salary-negotiation-email-sample/#ask-for-time-template
카운터 오퍼: https://fearlesssalarynegotiation.com/salary-negotiation-script/
상세한 카운터 오퍼 이메일 템플릿: https://fearlesssalarynegotiation.com/salary-negotiation-email-sample/#counter-minimum-template
Never Split the Difference(우리는 어떻게 마음을 움직이는가): https://www.goodreads.com/book/show/26156469-never-split-the-difference
Bargaining for Advantage: Negotiation Strategies for Reasonable People(합리적인 사람을 위한 협상 전략): https://www.goodreads.com/book/show/23801.Bargaining_for_Advantage?from_search=true&from_srp=true&qid=WQx7saRO4G&rank=1
Getting to Yes: Negotiating Agreement Without Giving In(YES를 이끌어내는 협상법): https://www.goodreads.com/book/show/313605.Getting_to_Yes?ac=1&from_search=true&qid=HcfBQa9GvT&rank=1
Getting Past No: https://www.amazon.com/Getting-Past-Negotiating-Difficult-Situations/dp/0553371312

A.30 전술: 비공개로 배우기

공개적으로 배우기: http://swyx.io/LIP
강연: https://www.swyx.io/speaking/learn-in-public-nyc
팟캐스트: https://www.swyx.io/speaking/freecodecamp-podcast
여기에는 RSS 피드가 도움이 됩니다.: https://twitter.com/chriscoyier/status/1214606808125341696#m
그래프 따라가기: https://twitter.com/swyx/status/1216519772210388992
“사용하는 것의 소스 코드를 읽으십시오.”: https://twitter.com/ryanflorence/status/1281052845836431361
jQuery 소스에서 배운 10가지: https://paulirish.com/2010/10-things-i-learned-from-the-jquery-source/
11가지 더: https://www.youtube.com/watch?v=ARnp9Y8xgR4
오픈 소스 React 프로젝트 아이디어 목록: https://www.reddit.com/r/reactjs/?f=flair_name%3A%22Project%20Ideas%22
언어 이면의 메타언어: https://www.youtube.com/watch?v=_0T5OSSzxms
울트라러닝: https://www.scotthyoung.com/blog/ultralearning/
Joe Previte: https://twitter.com/jsjoeio
삼단논법: https://en.wikipedia.org/wiki/List_of_valid_argument_forms
세컨드 브레인 구축하기: https://praxis.fortelabs.co/5-steps-to-build-a-second-brain-7eddbae5af95/
마이클 닐슨(Michael Nielsen)은 장기 기억의 용량에 대해 과장된 주장을 하는 것으로 유명합니다: http://augmentingcognition.com/ltm.html
Anki: https://apps.ankiweb.net/
Mike White: https://twitter.com/myquite/status/1215340113468755968#m
분해하고 재구성하기: https://observer.com/2016/12/the-benjamin-franklin-method-how-to-actually-be-a-better-writer/
간극(The Gap): https://jamesclear.com/ira-glass-failure
파인만 기법: https://fs.blog/2012/04/feynman-technique/
먼저 이해하고, 그다음에 이해받으라: https://www.franklincovey.com/the-7-habits/habit-5.html
스틸맨 논증(Steel-manning): https://lifehacker.com/utilize-the-steel-man-tactic-to-argue-more-effectivel-1632402742
Andrew Chen의 글 더 보기: https://twitter.com/andrewchen/status/1190721336252829696
허수아비 논법: https://en.wikipedia.org/wiki/Straw_man
배우는 법 배우기: https://css-tricks.com/learning-to-learn/
배우는 법 배우기: https://ladybug.dev/learning-to-learn
두뇌 프로그래밍: 세 단계로 익히는 학습의 기술: https://www.bitnative.com/2013/12/14/programming-your-brain-the-art-of-learning-in-three-steps/
엔지니어를 위한 리더십 라이브러리: https://leadership-library.dev/The-Leadership-Library-for-Engineers-c3a6bf9482a74fffa5b8c0e85ea5014a
자주 곱씹어 보는 프로그래밍 에세이: https://www.benkuhn.net/progessays/
시대를 타지 않는 웹 개발 글: https://css-tricks.com/timeless-web-dev-articles/

A.31 전술: 디자인 팁

Sarah Drasner: https://frontendmasters.com/courses/design-for-developers/designer-vs-developer/
Bootstrap: https://getbootstrap.com/
Foundation: https://get.foundation/sites/docs/
Blaze UI: https://www.blazeui.com/
PatternFly: https://www.patternfly.org/v4/documentation/
UIKit: https://getuikit.com/docs/introduction
Weightless: https://weightless.dev/elements/checkbox
ReactStrap: https://reactstrap.github.io/
Material-UI: https://material-ui.com/
Spectre.css: https://picturepan2.github.io/spectre/getting-started/installation.html
PureCSS: https://purecss.io/
LitCSS: https://ajusa.github.io/lit/
ScreenCSS: https://screencss.com/
MVPCSS: https://andybrewer.github.io/mvp/
Drop-in Minimal CSS 저장소: https://github.com/dohliam/dropin-minimal-css
PaperCSS: https://www.getpapercss.com/
TerminalCSS: https://terminalcss.xyz/
NES.css: https://nostalgic-css.github.io/NES.css/
98.css: https://github.com/jdan/98.css
Nanoreset: https://github.com/tiaanduplessis/nanoreset
Destyle: https://nicolas-cusan.github.io/destyle.css/
Andy Bell: https://hankchizljaw.com/wrote/a-modern-css-reset/
Normalize.css: http://necolas.github.io/normalize.css/
XKCD 스타일 차트: https://timqian.com/chart.xkcd/
그래픽: https://roughjs.com/
Creative Tim: https://creative-tim.com
Tailwind UI: https://tailwindui.com/components
마진 상쇄(margin collapsing): https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Box_Model/Mastering_margin_collapsing
단방향 마진 선언: https://csswizardry.com/2012/06/single-direction-margin-declarations/
CSSLayout: https://csslayout.io/patterns
Every Layout: https://every-layout.dev/
홀리 그레일(Holy Grail): https://csslayout.io/patterns/holy-grail
훨씬 쉽게 할 수 있습니다: https://css-tricks.com/international-box-sizing-awareness-day/
Sarah Drasner의 개발자를 위한 디자인(Design for Developers) 워크숍을 확인하십시오: https://github.com/sdras/design-for-developers/blob/master/slides-pdf/Des4Dev2.pdf
시스템 폰트 스택: https://css-tricks.com/snippets/css/system-font-stack/
Canva의 Font Combinations 앱: https://www.canva.com/font-combinations/
Google Fonts: https://fonts.google.com/
Freight Text: https://fonts.adobe.com/fonts/freight-text
Proxima Soft: https://fonts.adobe.com/fonts/proxima-soft
손글씨 글꼴: https://www.urbanfonts.com/fonts/handwritten-fonts.htm
Freight Sans: https://fonts.adobe.com/fonts/freight-sans
font-size: calc(1rem + 2px + ((100vw - 550px) / 250)): https://twitter.com/Kikobeats/status/1093620157912616966
Adobe Color: https://color.adobe.com/create
Coolors: https://coolors.co/
FlatUI: https://flatuicolors.com/
접근성 가이드라인 충족: https://webaim.org/resources/contrastchecker/
다크 모드: https://darkmodedesign.xyz/
WebGradients: https://webgradients.com
UI Gradients: https://uigradients.com/#Petrichor
그레이디언트 애니메이터: https://www.gradient-animator.com/
더 많은 CSS: https://leaverou.github.io/css3patterns/
테셀레이션 아이콘: http://www.heropatterns.com/
은은한 텍스처: https://www.transparenttextures.com/
Hero Generator: https://hero-generator.netlify.app/
Unsplash: http://unsplash.com/
Pexels: https://pexels.com
FontAwesome: https://fontawesome.com/
Shape.so: http://shape.so/
Streamline Icons: https://streamlineicons.com/
The Noun Project: https://thenounproject.com/
CSS.GG: https://css.gg/
Undraw: https://undraw.co/
Humaaans: https://www.humaaans.com/
Ouch!: https://icons8.com/ouch/
LottieFiles: https://lottiefiles.com/
Canva: https://www.canva.com/
Snappa: https://snappa.com/
Svgator: https://www.svgator.com/
Greensock: https://greensock.com/
CSSFX: https://cssfx.netlify.com/
SpinKit: https://tobiasahlin.com/spinkit/
Animista: http://animista.net
Animate.css: https://animate.style/
Animoto: https://animoto.com/
Biteable: https://biteable.com/
Powtoon: https://powtoon.com
Josh W. Comeau의 useSound: https://joshwcomeau.com/react/announcing-use-sound-react-hook/
React-Rewards: https://github.com/thedevelobear/react-rewards
Processing: http://processingjs.org/
D3: https://d3js.org/
Three.js: https://threejs.org/
react-three-fiber: https://github.com/react-spring/react-three-fiber
코나미 코드: https://github.com/snaptortoise/konami-js
GenieJS: https://github.com/kentcdodds/genie
Clippy.js: https://www.smore.com/clippy-js
Windows: https://winmine-exe.now.sh/
iPod: https://www.reddit.com/r/reactjs/comments/ek181n/i_built_an_ipod_classic_using_react_hooks_styled/
디자인을 꼼수로 잘하는 7가지 실용적인 팁: https://medium.com/refactoring-ui/7-practical-tips-for-cheating-at-design-40c736799886
Refactoring UI: http://refactoringui.com/
멋진 UI를 만들기 위한 7가지 규칙: https://medium.com/@erikdkennedy/7-rules-for-creating-gorgeous-ui-part-1-559d4e805cda
Learn UI Design: https://learnui.design/
개발자를 위한 디자인 Frontend Masters 워크숍: https://frontendmasters.com/courses/design-for-developers/
저장소: https://github.com/sdras/design-for-developers
Degreeless Design: https://www.degreeless.design/#basics
Tregg Frank: https://twitter.com/treggify
Dribbble: https://dribbble.com/
CollectUI: https://collectui.com/
Codrops: https://tympanus.net/codrops/2019/06/04/inspirational-websites-roundup-5/
spark-joy 저장소: https://github.com/sw-yx/spark-joy

A.32 전술: 램프셰이딩

다섯 살 아이에게 설명하듯 설명해 주시겠습니까?: https://www.dictionary.com/e/slang/eli5/
“간단하게 설명할 수 없다면 충분히 이해하지 못한 것입니다”: https://www.passiton.com/inspirational-quotes/3363-if-you-cant-explain-it-simply-you-dont
네 가지 성향(Four Tendencies): https://gretchenrubin.com/2015/01/ta-da-the-launch-of-my-quiz-on-the-four-tendencies-learn-about-yourself/
램프셰이딩: https://tvtropes.org/pmwiki/pmwiki.php/Main/LampshadeHanging
소프트 파워: https://en.wikipedia.org/wiki/Soft_power
8 마일의 마지막 배틀: https://www.youtube.com/watch?v=sHE0wmgljco
서비스형 바보 같은 질문(Stupid Questions as a Service): https://twitter.com/swyx/status/1096645037788618752
가장 유명한 대표 사례: https://github.com/getify/You-Dont-Know-JS
React TypeScript 치트시트: https://github.com/typescript-cheatsheets/react-typescript-cheatsheet/
전환(Turn)과 마지막 프레스티지(Prestige)에 앞선 확인(Pledge): https://www.goodreads.com/quotes/91029-every-great-magic-trick-consists-of-three-parts-or-acts
제가 라이브코딩 발표를 구성하는 방식이 정확히 이렇습니다: https://www.youtube.com/watch?v=KJP1E-Y-xyo
트위터에서 트롤을 막아내기 위해 램프셰이딩을 능숙하게 활용하는 이 여성의 사례입니다: https://twitter.com/Nicolemens/status/1229610008167383040

A.33 전술: 콘퍼런스 CFP

논문 모집(Call for Papers): https://speaking.io/plan/writing-a-cfp/
Charity Majors: https://twitter.com/mipsytipsy/status/912103246017294336
2017년 12월: https://www.swyx.io/speaking/contributing-to-react/
2018년 8월: https://www.swyx.io/speaking/react-not-reactive/
약 250명 규모의 지역 커뮤니티 콘퍼런스: https://www.youtube.com/watch?v=DD6KTAGrj3E
약 4천 명 규모의 더 큰 콘퍼런스: https://www.swyx.io/speaking/jamstack-skeptic-allthingsopen/
영국: https://www.swyx.io/speaking/react-from-scratch/
스웨덴: https://www.swyx.io/talks/star-apps/
인도: https://www.swyx.io/speaking/serverless-graphql/
싱가포르: https://www.swyx.io/speaking/react-hooks/
하와이: https://www.swyx.io/speaking/babel-macros/
Hacker News에서: https://news.ycombinator.com/item?id=21858866
GitNation: https://gitnation.org/
임베디드 JS 발표: https://www.youtube.com/watch?v=3HLRwcVqgFE
크리에이티브 코딩 강연: https://www.youtube.com/watch?v=v2Au9Rlj6XM
또 다른 크리에이티브 코딩 강연: https://www.youtube.com/watch?v=nC5q5JxLjnY
또 다른 또 다른 크리에이티브 코딩 발표: https://www.youtube.com/watch?v=GqsdiMc49yM
디자인 요소를 손쉽게 더하는 방법: https://github.com/sw-yx/spark-joy/
가장 활발한 GitHub 저장소는 무엇입니까: https://github.com/mikeal/daily
패키지 다운로드로 보는 메가트렌드: https://npmcharts.com/
회사 리더들(여러분이 일하는 회사의 리더든, 뉴스에 등장하는 유명한 리더든)은 어떤 흥미로운 일을 하고 있습니까: https://css-tricks.com/star-apps-a-new-generation-of-front-end-tooling-for-development-workflows/
다이애나 스미스(Diana Smith)는 CSS 아트로 경력을 쌓았습니다: https://www.vice.com/en_us/article/9kgx7p/painting-made-with-code-html-pure-css-browser-art-diana-smith
가면 증후군: https://www.youtube.com/watch?v=Yk53eWIu7Nw
원격 근무: https://www.youtube.com/watch?v=61ji5L3GMeI
비영리 단체나 정부 기관: https://www.youtube.com/watch?v=S1E6C8O7fk0
학교 시스템: https://www.youtube.com/watch?v=2p4YunDAzsk
박물관: https://www.youtube.com/watch?v=AGtDAO_a9Mk
에어비앤비: https://www.youtube.com/watch?v=P-J9Eg7hJwE0
Millie Macdonald의 사례입니다: https://www.youtube.com/watch?v=K4cHUDDBwyM
Dan Abramov: https://www.youtube.com/watch?v=xsSnOQynTHs
Ryan Dahl: https://www.youtube.com/watch?v=EeYvFl7li9E
GraphQL의 에러 처리: https://www.youtube.com/watch?v=A5-H6MtTvqk
Vue에서의 입력 마스킹: https://www.youtube.com/watch?v=FDqKAlrUm0k
정적 사이트를 동적으로: https://vimeo.com/174172567
웹 A/V 아티스트 되기: https://www.youtube.com/watch?v=Lby6fk5gC4k
공을 튕기는 14가지 방법: https://awesometalks.party/video/cjqxy36f70xbp0147o7q2zj5x
닌자 거북이로 배우는 색채 이론: https://www.youtube.com/watch?v=NdKAUXAvt8E
휘몰아치듯 빠르게 살펴보는 TypeScript 입문: https://awesometalks.party/video/cjqwi7sn2123t0199yvtfosfa
Mark Erikson: https://www.youtube.com/watch?v=zWsXFn5-xDU
Ben Ilegbodu: http://www.benmvp.com/slides/2019/reactathon/react-eco.html
Sarah Drasner: https://www.youtube.com/watch?v=COAVmST41Q0
Evan You: https://www.youtube.com/watch?v=7_ZzayG45Mk&list=PUa1zuotKU4Weuw_fLRnPv0A&index=28
Sacha Greif: https://www.youtube.com/watch?v=FZw1j_tTSag
Tara Manicsic: https://www.youtube.com/watch?v=1_hHxra0Lf4
알고리즘: https://www.youtube.com/watch?v=panKf9hzUfQ
자료 구조: https://www.youtube.com/watch?v=Wo0qiGPSV-s
상태 머신: https://www.youtube.com/watch?v=tpNmPKjPSFQ
코루틴: https://www.youtube.com/watch?v=1_hHxra0Lf4
JS 이벤트 루프: https://www.youtube.com/watch?v=8aGhZQkoFbQ
시각 디자인: https://www.youtube.com/watch?v=hlI6xGfBjkQ
게임 프로그래밍 기법: https://www.youtube.com/watch?v=QX0eauXBKwc
프레젠테이션 도구로서의 IDE: https://staltz.com/your-ide-as-a-presentation-tool.html
제 최고의 발표는 라이브 코딩 발표입니다: https://www.swyx.io/speaking/react-hooks/
100% 라이브 코딩으로 진행되는 컨퍼런스 개최: https://bradfrost.com/blog/post/lets-make-a-design-system-live-coding-at-smashing-conf/
React Live: https://reactlive.nl/
Docker 교회의 이단: https://www.youtube.com/watch?v=RB6MvSEaMKI&feature=emb_title
GraphQL에 반대하는 이유: https://www.youtube.com/watch?v=djKPtyXhaNE
앱의 TTI를 6초에서 1초로 줄인 Jake와 Surma: https://www.youtube.com/watch?v=fWc3Zu6A3Ws
Sasha Aickin이 React SSR을 1025ms에서 5ms로 단축한 사례: https://www.youtube.com/watch?v=PnpfGy7q96U
다시는 HoC를 작성하지 마십시오: https://www.youtube.com/watch?v=BcVAq3YFiuc
다시는 HoC를 작성하지 마십시오: https://www.youtube.com/watch?v=BcVAq3YFiuc
오픈 소스의 어려운 부분: https://www.youtube.com/watch?v=o_4EX4dPppA
성공이란 무엇인가?: https://www.youtube.com/watch?v=uGlzRt-FYto
Simple Made Easy: https://www.youtube.com/watch?v=34_L7t7fD_U
이 발표에 이름을 붙이는 것조차 어렵습니다: https://www.youtube.com/watch?v=JuI6NUbEzDw&feature=emb_title
이 기묘한 비법 하나로 webpack 빌드 시간을 20%나 줄였습니다: https://twitter.com/swyx/status/1218173290579136512
제가 CFP를 작성하는 방법을 담은 12분짜리 영상: https://www.youtube.com/watch?v=gCroOiPRfw0
채택된 발표, 대기 중인 발표, 거절된(폐기된) 발표의 제목과 초록은 모두 제 사이트에서 보실 수 있습니다: https://github.com/sw-yx/swyxdotio/tree/master/content/
저의 첫 CFP(React Rally에 채택됨): https://twitter.com/swyx/status/1112513571315830784
나의 첫 JSConf CFP(JSConf Hawaii에 채택됨): https://twitter.com/swyx/status/1178059565805555713
React Rally 나쁜 예시 발표 제안서: https://speak.reactrally.com/events/react-rally-2019
David Khourshid의 React Rally CFP: https://docs.google.com/document/d/1uT4aimBXzLmSH7rOxnOYGX1iyHw76mKrs5jnwq3TWrg/edit?usp=sharing
Devon Lindsey의 React Rally CFP: https://docs.google.com/document/d/1qm33pkoy1T2gUiQm9SfEjKU8tXXPPLMaoKNM5U23LOY/edit?usp=sharing
Will Larson이 모은 CFP 예시의 보고: https://lethain.com/cfp-examples/
트윗 스레드: https://mobile.twitter.com/lethain/status/1221128652194103296
CFP를 찾는 방법: https://philna.sh/blog/2020/01/29/how-to-find-cfps-for-developer-conferences
Peggy Rayzis: https://twitter.com/peggyrayzis/status/1220034800830091265
기술 발표 준비하기: https://overreacted.io/preparing-for-tech-talk-part-1-motivation/
CFPLand 발표 가이드: https://www.cfpland.com/guides/speaking/
CFPLand의 Karl Hughes가 알려 주는 발표를 시작하는 방법: https://www.codewithjason.com/rails-with-jason-podcast/karl-hughes/

A.34 전술: 미장플라스 글쓰기

미장플라스: https://en.wikipedia.org/wiki/Mise_en_place
워크숍하기: https://en.wikipedia.org/wiki/Workshop_production
무엇을 말할지 말하고, 말하고, 방금 말한 것을 다시 말하십시오: https://www.inc.com/john-baldoni/deliver-a-great-speech-aristotle-three-tips.html
Maggie Appleton은 보이지 않는 것을 시각화하는 방법에 대해 훌륭한 아이디어를 가지고 있습니다: https://illustrated.dev/drawinginvisibles1
세컨드 브레인: https://www.buildingasecondbrain.com/
스카이스크래퍼: http://blog.exitbee.com/skyscraper-content-business-can-use-rapid-growth/
헤밍웨이: http://www.hemingwayapp.com/
디지털 가든의 살아 있는 문서: https://www.swyx.io/writing/digital-garden-tos/

A.35 전술: 사이드 프로젝트

Apprenticeship Patterns: https://www.oreilly.com/library/view/apprenticeship-patterns/9780596806842/ch05s03.html
Kent의 프로젝트: https://github.com/kentcdodds/bookshelf
Adam의 프로젝트: https://github.com/arackaf/booklist
Vincent Prouillet는 이렇게 말합니다: https://www.softwaresessions.com/episodes/creating-static-sites-in-rust-with-vincent-prouillet/
X를 밑바닥부터 직접 만들기: https://github.com/danistefanovic/build-your-own-x
Inferno.js: https://github.com/infernojs/inferno
Pinterest PWA를 만든 Zack Argyle: https://medium.com/pinterest-engineering/a-one-year-pwa-retrospective-f4a2f4129e05
Gmail, Chromecast, 그리고 AdSense: https://twitter.com/roxinekee_/status/1247895314150744065
BugCrowd와 HackerOne에서 버그 바운티 받기: https://danielmiessler.com/blog/build-successful-infosec-career/#bounty
xkcd의 Randall Munroe: https://xkcd.com/
작업 자동화에 얼마나 많은 시간을 투자해야 하는지: https://xkcd.com/1205/
Pieter Levels급 인디 해커: https://www.indiehackers.com/podcast/043-pieter-levels-of-nomad-list
Taylor Otwell: https://twitter.com/mijustin/status/1118143652943945728?lang=en
Mike Perham: https://www.indiehackers.com/podcast/016-mike-perham-of-sidekiq
앤 로르: https://www.indiehackers.com/podcast/133-quick-chat-with-anne-laure-le-cunff
그의 사이드 프로젝트 Unsplash: https://www.freecodecamp.org/news/the-unsplash-formula-how-crew-went-from-almost-broke-to-getting-5-million-visitors-ec4db8e7d6cd/
직무 발명 소유권 계약: https://www.joelonsoftware.com/2016/12/09/developers-side-projects/
Reilly Chase: https://twitter.com/_rchase_/status/1214534938441273344
Ideaswatch: https://ideaswatch.com/
그의 회사 CEO도 이제는 자랑스러운 고객입니다: https://twitter.com/nathanbarry/status/1247893869045276681
오픈 소스 라이브러리가 조금 형편없어도 괜찮습니다: https://news.ycombinator.com/item?id=23208779
그가 MIT 챌린지를 어떻게 소개하는지 봅시다: https://www.scotthyoung.com/blog/2013/07/09/side-project/
Codecations(코드케이션): https://thoughtbot.com/blog/you-should-take-a-codecation
Ryan Singer: https://twitter.com/rjs/status/650875194345697280
우선순위 정하기에 관한 Sarah Drasner의 시대를 초월한 글: https://css-tricks.com/prioritizing/
팀 페리스: https://www.youtube.com/watch?v=wCPbPMRNnvk
Jennifer Dewalt: https://jenniferdewalt.com/
Jessica Hische: http://www.dailydropcap.com/
니클라스 괴케: https://fourminutebooks.com/
케이시 나이스탯(Casey Neistat)은 550일 동안 매일 브이로그를 올렸습니다: https://campfirelabs.co/blog/2019/1/8/the-art-of-pitching-how-i-got-published-in-the-atlantic
케이트 빙어먼: https://www.katebingamanburt.com/daily-purchase-drawings
미셸 폴러: http://100dayswithoutfear.com/
지아 장(Jia Jiang): http://rejectiontherapy.com/100-days-of-rejection-therapy/
Megan Gebhart: https://www.amazon.com/52-Cups-Coffee-Megan-Gebhart/dp/150060206X
Pieter Levels: https://levels.io/12-startups-12-months/
Shooting Unicorns 듀오: https://medium.com/shooting-unicorns/were-shipping-12-passion-projects-in-12-months-74903671cd4d
실패한 MMORPG에서 파생된 프로젝트: https://techcrunch.com/2019/05/30/the-slack-origin-story/
아타리 직원의 사이드 프로젝트: https://www.acquired.fm/episodes/atari-with-nolan-bushnell

A.36 전술: 트위터

학술 조사: https://www.slideshare.net/mastorey/how-developers-stay-current-using-twitter
수천 개: https://twitter.com/EricVBailey/status/932994955693494272
Tracy Lee: https://twitter.com/ladyleet/status/985018157994831872?lang=en
http://jsjoe.io/: http://jsjoe.io/
도움 요청하기: https://www.addictioncenter.com/drugs/social-media-addiction/
강아지 평가: https://twitter.com/dog_rates
학술 연구: https://danco.substack.com/p/can-twitter-save-science
K-pop: https://www.diggitmagazine.com/articles/k-pop-fandom-twitter
Siraj Raval 같은 경우: https://vicki.substack.com/p/the-curse-of-being-big-on-the-internet
팔로워를 돈으로 살 때: https://www.nytimes.com/interactive/2018/01/27/technology/social-media-bots.html
Seth Godin이라면 ’당신의 부족 찾기(Finding your Tribe)’라고 부를 만한 것: https://www.samuelthomasdavies.com/book-summaries/business/tribes/
소리굽쇠를 두드리고 누가 공명하는지 지켜보기.: https://twitter.com/kevinakwok/status/998382426270318593
제가 결심했던 어느 주말: https://twitter.com/swyx/status/1179261731304022017
글로벌 콘퍼런스: https://twitter.com/sveltesociety
Naval Ravikant: https://twitter.com/naval/status/855865123973382144
가면 증후군 슬롯머신: https://twitter.com/Jayphen/status/1257340806777667584
이것을 시간순 피드로 전환할 수 있습니다: https://help.twitter.com/en/using-twitter/twitter-timeline
트위터 리스트: https://help.twitter.com/en/using-twitter/twitter-lists
알림 켜기: https://www.businessinsider.sg/how-to-turn-on-twitter-notifications?r=US&IR=T
Tweetdeck: https://tweetdeck.twitter.com/
뭐라도 만드십시오, 분란을 일으키지는 마십시오: https://twitter.com/swyx/status/1206795334686396417
Daniel Vassallo의 말입니다: https://twitter.com/dvassallo/status/1255931424823099392
Samantha Ming: https://twitter.com/samantha_ming/status/1256653618159075328
Steve Schoger: https://twitter.com/steveschoger/status/1186330420671057921
배운 것들을 목록으로 만드십시오: https://twitter.com/rafrasenberg/status/1272043097208377344
Daniel Vassallo의 몇 가지 조언: https://twitter.com/dvassallo/status/1250976216258998273
누구나 트위터 오디언스를 만들 수 있습니다: https://gumroad.com/l/twitter-audience
Bianca Ciotti의 분류 체계: https://twitter.com/BiancaCiotti/status/1237477855379853313
Wendy’s: https://twitter.com/wendys
유쾌함: https://twitter.com/BiancaCiotti/status/1237477857762267136
GitHub: https://twitter.com/github
트랜잭션형: https://twitter.com/BiancaCiotti/status/1237477859024703493
다음과 같은 크롬 확장 프로그램입니다: https://github.com/round/Twitter-Links-beta/
Visakan Veerasamy: https://twitter.com/visakanv/status/1040450987754811392
흥미로운 인용구를 공유하십시오: https://twitter.com/swyx/status/1256322600097079296
읽은 책의 페이지를 스크린샷으로 찍어 공유하십시오: https://twitter.com/swyx/status/1018618475311521793
놀라운 데모 영상: https://twitter.com/swyx/status/1254402262857736192
Google AMP: https://blog.hubspot.com/marketing/google-amp
제텔카스텐 또는 메멕스: https://twitter.com/Conaw/status/1129806786477772801
결과가 따를 수 있습니다: https://www.nytimes.com/2015/02/15/magazine/how-one-stupid-tweet-ruined-justine-saccos-life.html
팀 페리스는 다음과 같이 말합니다: https://www.maxim.com/maxim-man/8-rules-for-haters-tools-for-titans-2016-12
허수아비 논법: https://en.wikipedia.org/wiki/Straw_man
반론의 위계: https://en.wikipedia.org/wiki/Paul_Graham_(programmer
긴장을 완화할 수 있습니다: https://devonzuegel.com/post/the-silence-is-deafening
비폭력 대화: https://en.wikipedia.org/wiki/Nonviolent_Communication
맨스플레인하지 마십시오: https://twitter.com/kimgoodwin/status/1020029572266438657
리플라이 가이(Reply Guy)의 아홉 가지 유형에 관한 이 스레드: https://twitter.com/sbarolo/status/1037052674158604289
차가운 미디어: https://alexdanco.com/2019/10/17/the-audio-revolution/
반대할 권리: https://wincent.com/blog/on-the-right-to-disagree
포의 법칙: https://en.wikipedia.org/wiki/Poe%27s_law
여러분에게는 표현의 자유가 있지만, 그 권리가 비판이나 그에 따른 결과로부터 여러분을 보호해 주지는 않습니다: https://xkcd.com/1357/
『트위터 사용을 위한 Holloway 가이드』: https://www.holloway.com/g/using-twitter
Daniel Vassallo의 누구나 트위터 오디언스를 구축할 수 있다(Everyone Can Build a Twitter Audience): https://gumroad.com/l/twitter-audience/indiehackers

A.37 전술: 자기 자신을 마케팅하기

최근 설문 조사: https://zellwk.com/blog/build-your-developer-brand/
95%보다 나아지는 것은 그리 어렵지 않습니다: https://danluu.com/p95-skill/
당신이 되는 일에서는 아무도 당신과 경쟁할 수 없습니다: https://nav.al/competition-authenticity
이미 이렇게 한 사례가 있습니다: https://uibreakfast.com/169-building-your-brand-with-austin-church/
자신의 데이터 시각화를 인쇄해 명함으로 사용했습니다: https://twitter.com/sxywu/status/877357398054141952
보랏빛 소(Purple Cow): https://www.amazon.com/Purple-Cow-New-Transform-Remarkable/dp/1591843170
개구리 커밋(Kermit the Frog)과 패밀리 가이(Family Guy)의 스튜이 목소리를 내 달라는 요청을 받은 Seth McFarlane: https://www.youtube.com/watch?v=AP_aom1IgqI
여기: https://twitter.com/AdamRackis/status/1254543828981293056
여기: https://twitter.com/laurieontech/status/1254118781875630080
제 스크롤바를 기억하십시오: https://swyx.io/writing/scrollbar-shenanigans
Daniel Miessler: https://danielmiessler.com/blog/build-successful-infosec-career/
깃발을 꽂으십시오: https://krebsonsecurity.com/2018/06/plant-your-flag-mark-your-territory/
나만의 배트 시그널: https://andrewchen.co/professional-blogging/
The Points Guy: https://thepointsguy.com/
The RideShare Guy: https://therideshareguy.com/
“How I Met Your Mother”(국내 방영명 「내가 그녀를 만났을 때」)에서 바니 스틴슨이 자랑하는 것을 들어 보십시오: https://www.youtube.com/watch?v=BHpBVFFsL8U
훌륭한 Patrick McKenzie 기조연설: https://microconf.gen.co/patrick-mckenzie/
Charity Majors: https://twitter.com/mipsytipsy/status/1247006442265198595
가용성 편향: https://whatis.techtarget.com/definition/availability-bias
Cory House는 문의가 15배 증가했습니다: https://www.youtube.com/watch?v=Y4wnbkatj20&feature=youtu.be&t=1311
블로그를 더 많이 쓰셔야 합니다: https://www.youtube.com/watch?v=SAiSRuX4iW8
스티브 예기(Steve Yegge): https://sites.google.com/site/steveyegge2/you-should-write-blogs
CSS Tricks: https://css-tricks.com/
자랑 문서(Brag Document): https://jvns.ca/blog/brag-documents/
상대방에게 돌아가는 이득: http://www.salesprogress.com/coaching-leadership/bid/96324/WIFT-What-s-In-It-For-Them
구글 매출의 97%가 거쳐 가는 백엔드 결제 코드를 작성했습니다: https://kalzumeus.com/2011/10/28/dont-call-yourself-a-programmer/
FizzBuzz: https://blog.codinghorror.com/why-cant-programmers-program/
저는 /r/reactjs에서 바로 그렇게 했습니다: https://www.swyx.io/writing/react-survey-2019/
Major League Hacking: https://mlh.io/
처음부터 직접 만드는 X(Build Your Own X from Scratch): https://github.com/danistefanovic/build-your-own-x
신뢰의 속도(the Speed of Trust): https://www.speedoftrust.com/
하겠다고 말한 것을 그저 실제로 해내기만 해도 눈에 띄게 됩니다: https://twitter.com/swyx/status/1193467826310238208
인바운드 마케팅: https://www.hubspot.com/inbound-marketing
퍼미션 마케팅: https://seths.blog/2008/01/permission-mark/
Zack Argyle은 해커톤 프로젝트를 바탕으로 Pinterest의 CEO를 설득해 Pinterest를 PWA로 전환했습니다: https://twitter.com/swyx/status/1128141051406032898
엄청난 비즈니스 효과: https://medium.com/dev-channel/a-pinterest-progressive-web-app-performance-case-study-3bd6ed2e6154
Google: https://www.blog.google/topics/inside-google/talks-google-shared/
Etsy: https://www.etsy.com/codeascraft/talks
Dropbox에서 JavaScript 길드를 시작했습니다: https://dropbox.tech/frontend/what-we-learned-at-our-first-js-guild-summit
린치핀: https://www.amazon.com/gp/product/1591844096/
여기: https://deanyeong.com/reading-note/linchpin/
가난하고 유명한 것보다 부유하고 알려지지 않은 편이 낫습니다: https://twitter.com/naval/status/1041513555961438208?lang=en
Troy Hunt의 커리어 조언 강연: https://www.software-engineering-unlocked.com/developer-security-troy-hunt/
Wes Bos: https://twitter.com/wesbos
Web Smith: https://twitter.com/2pminc
댄 아브라모프(Dan Abramov)의 사례입니다: https://www.software-engineering-unlocked.com/episode-13-bad-tests-dan-abramov/
레일 라운즈(Leil Lowndes)의 『How to Talk To Anyone』(한국어판: 『사람을 얻는 기술』): https://www.amazon.com/How-Talk-Anyone-Success-Relationships/dp/1511305169
책 공동 집필: https://www.amazon.com/Traction-Startup-Achieve-Explosive-Customer/dp/1591848369
Blake Masters와 Peter Thiel: https://en.wikipedia.org/wiki/Zero_to_One
Ben Casnocha와 Reid Hoffman: https://casnocha.com/reid-hoffman-lessons
그들이 내려놓은 것을 집어 들기: https://www.swyx.io/writing/learn-in-public-hack/
fetch 유행시키기: https://www.youtube.com/watch?v=Pubd-spHN-0
보이지 않는 것들조차도: https://illustrated.dev/drawinginvisibles1
특히 보이지 않는 것들은 더욱 그렇습니다: https://www.youtube.com/watch?v=MQGe9zxlRdk
Excalidraw: https://excalidraw.com/
두 단어: https://www.swyx.io/writing/two-words/
Farnam Street: http://www.farnamstreetblog.com/
The Waiter’s Pad: https://thewaiterspad.com/
flawless app의 Marketing for 엔지니어 저장소: https://github.com/LisaDziuba/Marketing-for-Engineers

A.38 개념: Big L 표기법

무한 학습자: https://www.sachinrekhi.com/how-to-be-an-infinite-learner
빅 오 표기법: https://en.wikipedia.org/wiki/Big_O_notation
던바의 수: https://en.wikipedia.org/wiki/Dunbar%27s_number
메트커프 스케일링: https://en.wikipedia.org/wiki/Metcalfe%27s_law
리드의 법칙: https://www.swyx.io/writing/eponymous-laws#business-of-tech
당신의 인생을 어떻게 평가할 것인가?: https://hbr.org/2010/07/how-will-you-measure-your-life

A.39 개념: 프렌드캐처

드림캐처: https://legomenon.com/dreamcatcher-meaning-legend-history-origins.html
Patrick McKenzie: https://twitter.com/search?q=from%3Apatio11%20friend-catcher&src=typed_query
Patrick의 어머니의 말을 빌리자면: https://youtu.be/PtmUJye7t4c?t=744
호혜성은 무기화된 카르마입니다: https://www.influenceatwork.com/principles-of-persuasion/
레버리지: https://www.youtube.com/watch?v=GtyWqj2ESiQ
자기 자신을 상품화하기: https://nav.al/productize-yourself
Patrick의 연봉 협상 블로그 글: https://kalzumeus.com/2012/01/23/salary-negotiation/
프런트엔드 클라이언트에서 JWT를 다루는 최고의 가이드(GraphQL): https://blog.hasura.io/best-practices-of-using-jwt-with-graphql/
Lin Clark의 WebAssembly 입문: https://hacks.mozilla.org/2017/02/a-cartoon-intro-to-webassembly/
공개적으로 배우기: https://www.swyx.io/writing/learn-in-public/
Kissmetrics 무료 도구: https://kissmetrics.com/growth-tools/ab-significance-test/
조시 코프먼이 엄선한 최고의 비즈니스 도서 목록: https://personalmba.com/best-business-books/
Sindre Sorhus의 Awesome 리스트: https://github.com/sindresorhus/awesome
제 (예전) Concurrent React 노트: https://github.com/sw-yx/concurrent-react-notes
제 설렘을 주는 디자인 도구 저장소: https://github.com/sw-yx/spark-joy/
Alex DeBrie의 DynamoDB 가이드: https://www.dynamodbguide.com/
Amy Hoy의 Ruby on Rails 치트시트: http://www.slash7.com/cheats/rails_files_cheatsheet.pdf
제 React TypeScript 치트시트: https://github.com/typescript-cheatsheets/react
Steve Schoger의 디자인 트윗: https://twitter.com/i/events/994601867987619840
Samantha Ming의 팁: https://twitter.com/samantha_ming/media?lang=en
Wes Bos의 개발 팁: https://twitter.com/search?q=from%3Awesbos%20%F0%9F%94%A5&src=typed_query
콘텐츠 마케팅 전략에 관한 Patrick의 글: https://training.kalzumeus.com/newsletters/archive/content-marketing-strategy
Microconf 2018에서 한 Patrick의 발표: https://youtu.be/PtmUJye7t4c?t=822

A.40 개념: 행운 만들기

행운의 표면적: https://www.codusoperandi.com/posts/increasing-your-luck-surface-area
숀 머피(Sean Murphy): https://www.skmurphy.com/blog/2019/04/03/increase-your-luck-surface-area-to-get-more-customers/
Patrick McKenzie: https://www.perell.com/podcast/patrick-mckenzie-internet-famous
고정 마인드셋 대 성장 마인드셋: https://www.brainpickings.org/2014/01/29/carol-dweck-mindset/
마크 앤드리슨(Marc Andreesen): https://pmarchive.com/luck_and_the_entrepreneur.html
Naval과 Nivi: https://twitter.com/nivi/status/1094940675353784320?lang=en
Naval은 다음과 같이 요약합니다: https://twitter.com/naval/status/1093981014920052736
찰스 케터링: https://due.com/blog/keep-going-charles-f-kettering/
데릭 시버스(Derek Sivers): https://sive.rs/extremex
잔카를로 로타: http://themattheweffect.org/tag/richard-feynman/
석유 탐사 업계에서 빌려 온 표현입니다: https://en.wikipedia.org/wiki/Prospecting

A.41 피날레:

Dan Gilbert: https://www.youtube.com/watch?v=XNbaR54Gpj4&feature=youtu.be
CascadiaJS 2020에서 강연으로 발표했습니다: https://www.youtube.com/watch?v=D-Sj6jo4o1I
저에게 버그 리포트를 보내 주십시오: https://twitter.com/swyx
켄트 벡: https://www.jorgemanrubia.com/2019/09/19/programming-quotes-that-blew-my-mind/
아주 작은 습관의 힘(Atomic Habits): https://www.amazon.com/Atomic-Habits-Proven-Build-Break/dp/0735211299
습관의 힘(The Power of Habit): https://charlesduhigg.com/the-power-of-habit/
성공하는 사람들의 7가지 습관: https://www.goodreads.com/book/show/36072.The_7_Habits_of_Highly_Effective_People?ac=1&from_search=true&qid=BD2xhTaw8s&rank=1
James Clear: https://twitter.com/jamesclear/status/952316052599427072
우리는 왜 잠을 자야 할까(Why We Sleep): https://en.wikipedia.org/wiki/Why_We_Sleep
빌 게이츠: https://www.gatesnotes.com/Books/Why-We-Sleep
Pieter Levels: https://levels.io/rsi/
Scott Hanselman은 이렇게 말합니다: https://twitter.com/shanselman/status/1256499721029316608
반복성 긴장 장애(RSI): https://en.wikipedia.org/wiki/Repetitive_strain_injury
제가 정리한 RSI 관련 자료 모음: https://www.swyx.io/rsi-tips/
일련의 캐시: https://en.wikipedia.org/wiki/CPU_cache
RAM: https://en.wikipedia.org/wiki/Random-access_memory
망각 곡선: https://en.wikipedia.org/wiki/Forgetting_curve
컨텍스트 스위칭: https://whatis.techtarget.com/definition/context-switch
“세컨드 브레인” 구축하기: https://fortelabs.co/blog/basboverview/
멧커프의 법칙: https://en.wikipedia.org/wiki/Metcalfe%27s_law
초집중(Indistractable): https://www.nirandfar.com/indistractable/
뽀모도로 기법: https://en.wikipedia.org/wiki/Pomodoro_Technique
업무 환경이 자신의 생산성과 만족도에 미치는 영향: https://www.microsoft.com/en-us/research/publication/the-effect-of-work-environments-on-productivity-and-satisfaction-of-software-engineers/
쏟아지는 일 완벽하게 해내는 법(Getting Things Done): https://gettingthingsdone.com/
개인 생산성 가이드: https://pmarchive.com/guide_to_personal_productivity.html
2020년 업데이트: https://www.theobservereffect.org/marc.html
NASA는 위험을 평가하는 데 이 매트릭스를 사용합니다: https://nesslabs.com/nasa-risk-matrix
크로노타입: https://en.wikipedia.org/wiki/Chronotype
자신이 어느 유형인지 알아보기: https://www.cake.co/conversations/85qgS1V/the-power-of-when-or-what-s-your-chronotype-dolphin-lion-bear-or-wolf
언제 할 것인가: 쫓기지 않고 시간을 지배하는 타이밍의 과학적 비밀: https://www.goodreads.com/book/show/35412097-when
Sarah Drasner는 한 주의 시작을 회의에 할애합니다: https://css-tricks.com/prioritizing/
메이커의 일정, 매니저의 일정: http://www.paulgraham.com/makersschedule.html
번아웃으로 가는 길은 컨텍스트 스위칭으로 포장되어 있습니다: http://sophieshepherd.com/2017/06/14/learning-to-be-chill.html
이 주제에 관한 Dan Pink의 책: https://www.danpink.com/drive./
pid 0: https://www.quora.com/How-can-an-operating-system-be-reactive-in-the-low-level-and-not-requiring-a-main-loop-considering-they-are-already-event-based
아놀드 슈워제네거: https://www.goodreads.com/book/show/31823677-tools-of-titans
Algorithms to Live By(알고리즘, 인생을 계산하다): https://www.goodreads.com/book/show/25666050-algorithms-to-live-by
제임스 클리어(James Clear): https://twitter.com/jamesclear/status/1048612840615997441
배우는 법을 배우기: https://max2c.com/learning-how-to-learn/
일과 삶의 균형: http://katemats.com/letter-on-importance-of-work-life-balance/
무시하십시오: http://janjanjan.uk/2018/05/18/constant-learning-commitment-determination/
행복해지는 법을 배우십시오: https://www.coursera.org/learn/the-science-of-well-being
저에게 트윗하십시오: https://twitter.com/swyx
책: https://twitter.com/Coding_Career
책 커뮤니티 포럼: https://codingcareer.circle.so/