https://www.youngju.dev/blog 천천히 올바르게. AI Researcher & DevOps Engineer Youngju's blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, and data engineering — plus mindset essays on confidence, routines, health, and sport psychology. ko fjvbn2003@gmail.com (Youngju Kim) fjvbn2003@gmail.com (Youngju Kim) Sat, 15 Aug 2026 00:00:00 GMT https://www.youngju.dev/blog/architecture/2026-08-15-guide-refactoring.en https://www.youngju.dev/blog/architecture/2026-08-15-guide-refactoring.en This guide is about how to refactor safely, not when refactoring pays. Starting from the definition of refactoring, it walks through building a safety net with characterization tests, introducing seams into code you cannot touch, changing interfaces with parallel change, and cutting a large change into reversible pieces. It also covers how to verify automated refactorings and codemods, and how to decide when to stop. Sat, 15 Aug 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) 리팩터링레거시코드테스트refactoringcharacterization-testcodemodparallel-change https://www.youngju.dev/blog/architecture/2026-08-15-guide-refactoring.ja https://www.youngju.dev/blog/architecture/2026-08-15-guide-refactoring.ja リファクタリングを「いつやるか」ではなく「どう安全にやるか」から扱います。定義の確認から始め、特性化テストで安全網を作り、触れないコードに継ぎ目を入れ、並行変更でインターフェースを差し替え、大きな変更を戻せる断片へ切り分ける手順を順番に整理します。自動リファクタリングとコードモッドの検証方法、そして止めどきを決める基準まで含みます。 Sat, 15 Aug 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) 리팩터링레거시코드테스트refactoringcharacterization-testcodemodparallel-change https://www.youngju.dev/blog/architecture/2026-08-15-guide-refactoring https://www.youngju.dev/blog/architecture/2026-08-15-guide-refactoring 리팩터링을 언제 하느냐가 아니라 어떻게 안전하게 하느냐를 다룹니다. 리팩터링의 정의에서 출발해 특성화 테스트로 안전망을 만들고, 손댈 수 없는 코드에 접합부를 내고, 병렬 변경으로 인터페이스를 바꾸고, 큰 변경을 되돌릴 수 있는 조각으로 자르는 절차를 순서대로 정리합니다. 자동 리팩터링과 코드모드의 검증 방법, 그리고 멈출 때를 정하는 기준까지 포함합니다. Sat, 15 Aug 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) 리팩터링레거시코드테스트refactoringcharacterization-testcodemodparallel-change https://www.youngju.dev/blog/architecture/2026-08-15-guide-testing-strategy.en https://www.youngju.dev/blog/architecture/2026-08-15-guide-testing-strategy.en Instead of picking a winner between the test pyramid and the testing trophy, this post decomposes the argument into the axes it actually turns on, so a team can derive its own ratio. It covers the definition of a unit, the four-part cost function, how far to take mocking, what to do with coverage numbers, using defect distribution data, and the operational rules for slow and flaky tests. Sat, 15 Aug 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) 테스트아키텍처testingtest-pyramidcoveragemocking https://www.youngju.dev/blog/architecture/2026-08-15-guide-testing-strategy.ja https://www.youngju.dev/blog/architecture/2026-08-15-guide-testing-strategy.ja テストピラミッドとテスティングトロフィーのどちらが正しいかを選ぶのではなく、その論争を実際の軸に分解して、チームが自分の比率を自分で決める方法を整理します。単位の定義、コスト関数、モックの使用範囲、カバレッジの数字、欠陥分布のデータ、遅く壊れやすいテストの運用規則までを判断基準中心に扱います。 Sat, 15 Aug 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) 테스트아키텍처testingtest-pyramidcoveragemocking https://www.youngju.dev/blog/architecture/2026-08-15-guide-testing-strategy https://www.youngju.dev/blog/architecture/2026-08-15-guide-testing-strategy 테스트 피라미드와 테스팅 트로피 중 무엇이 맞는지 고르는 대신, 그 논쟁을 실제 축으로 분해해 팀이 자기 비율을 스스로 정하는 방법을 정리합니다. 단위의 정의, 비용 함수, 목 사용 범위, 커버리지 숫자, 결함 분포 데이터, 느리고 깨지는 테스트의 운영 규칙까지 결정 기준 중심으로 다룹니다. Sat, 15 Aug 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) 테스트아키텍처testingtest-pyramidcoveragemocking