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-tech-debt.en https://www.youngju.dev/blog/architecture/2026-08-15-guide-tech-debt.en This guide covers the step before persuasion: finding where technical debt actually lives and attaching a number to it. It uses Fowler quadrants to recover the original meaning of the metaphor, filters out things that are not debt, locates hotspots by change frequency and complexity, observes interest through DORA metrics, and sets out how to maintain a debt list, a repayment plan, and a decision not to repay. Sat, 15 Aug 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) 기술부채리팩터링코드품질tech-debtdorahotspot-analysis https://www.youngju.dev/blog/architecture/2026-08-15-guide-tech-debt.ja https://www.youngju.dev/blog/architecture/2026-08-15-guide-tech-debt.ja 技術的負債を説得する前の段階、つまりどこにあるかを見つけ出し、数字を付ける方法を扱います。Fowler の四象限で比喩の本来の意味を整理し、負債でないものを除外し、変更頻度と複雑度でホットスポットを探し、DORA 指標で利息を観測し、負債リストと返済計画を維持する手順、そして返さないと決める方法までまとめます。 Sat, 15 Aug 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) 기술부채리팩터링코드품질tech-debtdorahotspot-analysis https://www.youngju.dev/blog/architecture/2026-08-15-guide-tech-debt https://www.youngju.dev/blog/architecture/2026-08-15-guide-tech-debt 기술 부채를 설득하기 전 단계, 즉 어디에 있는지 찾아내고 숫자를 붙이는 방법을 다룹니다. Fowler의 사분면으로 은유의 원래 뜻을 정리하고, 부채가 아닌 것을 걸러 내고, 변경 빈도와 복잡도로 핫스팟을 찾고, DORA 지표로 이자를 관측하고, 부채 목록과 상환 계획을 유지하는 절차, 그리고 갚지 않기로 결정하는 방법까지 정리합니다. Sat, 15 Aug 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) 기술부채리팩터링코드품질tech-debtdorahotspot-analysis