<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:image="http://www.google.com/schemas/sitemap-image/1.1">

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/vscode-python-interpreter-not-showing/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-vscode-python-interpreter-not-showing/vscode-python-interpreter-hero.png</image:loc>
      <image:title>VS Code Python Interpreter가 보이지 않을 때 해결 방법</image:title>
      <image:caption>VS Code에서 Python interpreter가 보이지 않을 때 Python extension, workspace folder, virtual environment 위치, manual path 선택, terminal 환경을 확인합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/maven-dependency-not-found/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-maven-dependency-not-found/maven-dependency-not-found-hero.png</image:loc>
      <image:title>Maven dependency not found 오류 해결 방법</image:title>
      <image:caption>Maven dependency not found 오류를 groupId, artifactId, version, repository, local cache, mirror, credential, dependency tree 순서로 해결합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-unsupported-class-file-major-version/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-java-unsupported-class-file-major-version/java-class-file-version-hero.png</image:loc>
      <image:title>Unsupported Class File Major Version 해결: Java JDK 버전 불일치 고치기</image:title>
      <image:caption>Unsupported class file major version 오류를 Java runtime, compiler, Gradle/Maven toolchain, target release 버전 정렬로 해결합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/gradle-build-failed/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-gradle-build-failed/gradle-build-failed-hero.png</image:loc>
      <image:title>Gradle build failed 해결 체크리스트</image:title>
      <image:caption>Gradle build failed 오류를 첫 실패 task, --stacktrace, Gradle wrapper, Java version, dependency resolution, test report 순서로 디버깅합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-gh006-protected-branch/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-git-gh006-protected-branch/git-gh006-protected-branch-hero.png</image:loc>
      <image:title>GH006 Protected Branch Hook Declined 오류 해결 방법</image:title>
      <image:caption>GitHub GH006 protected branch hook declined 오류를 feature branch, pull request, required checks, review approval, branch protection rule 순서로 해결합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/vscode-python-interpreter-not-showing/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-vscode-python-interpreter-not-showing/vscode-python-interpreter-hero.png</image:loc>
      <image:title>VS Code Python Interpreter Not Showing: How to Find and Select the Right Environment</image:title>
      <image:caption>Fix VS Code Python interpreter not showing by checking the Python extension, workspace folder, virtual environment location, manual interpreter path, and terminal environment.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/maven-dependency-not-found/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-maven-dependency-not-found/maven-dependency-not-found-hero.png</image:loc>
      <image:title>Maven Dependency Not Found: How to Fix Could Not Resolve Artifact</image:title>
      <image:caption>Fix Maven dependency not found errors by checking groupId, artifactId, version, repositories, local cache, mirrors, credentials, and dependency trees.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-unsupported-class-file-major-version/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-java-unsupported-class-file-major-version/java-class-file-version-hero.png</image:loc>
      <image:title>Unsupported Class File Major Version: How to Fix Java JDK Mismatch</image:title>
      <image:caption>Fix Unsupported class file major version by matching the Java runtime, compiler, Gradle or Maven toolchain, and target release used by the project.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/gradle-build-failed/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-gradle-build-failed/gradle-build-failed-hero.png</image:loc>
      <image:title>Gradle Build Failed: A Practical Debugging Checklist for Java Projects</image:title>
      <image:caption>Debug Gradle build failed errors by reading the first failing task, using --stacktrace, checking the wrapper, dependencies, Java version, tests, and cache.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-gh006-protected-branch/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-git-gh006-protected-branch/git-gh006-protected-branch-hero.png</image:loc>
      <image:title>Fix GH006 Protected Branch Hook Declined: Why GitHub Blocks Your Push</image:title>
      <image:caption>Fix GitHub GH006 protected branch hook declined by using a pull request, passing required checks, getting review approval, or changing branch protection rules.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/docker-daemon-not-running/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-docker-daemon-not-running/docker-daemon-not-running-hero.png</image:loc>
      <image:title>Docker daemon not running 오류 해결 방법</image:title>
      <image:caption>Cannot connect to the Docker daemon 오류를 Docker Desktop 또는 Docker service 실행, socket 권한, Docker context, DOCKER_HOST 점검 순서로 해결합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/docker-daemon-not-running/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-docker-daemon-not-running/docker-daemon-not-running-hero.png</image:loc>
      <image:title>Docker Daemon Not Running: How to Fix Cannot Connect to the Docker Daemon</image:title>
      <image:caption>Fix Docker daemon not running by checking Docker Desktop or the Docker service, verifying the socket, restarting the engine, and confirming permissions.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/spring-boot-port-8080-already-in-use/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-spring-boot-port-8080-already-in-use/spring-boot-port-8080-hero.png</image:loc>
      <image:title>Spring Boot port 8080 already in use 해결 방법</image:title>
      <image:caption>Spring Boot port 8080 already in use 오류를 포트 점유 프로세스 확인, 안전한 종료, server.port 변경, Docker/IDE 세션 점검 순서로 해결합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/spring-boot-port-8080-already-in-use/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-spring-boot-port-8080-already-in-use/spring-boot-port-8080-hero.png</image:loc>
      <image:title>Spring Boot Port 8080 Already in Use: How to Find the Process and Change the Port</image:title>
      <image:caption>Fix Spring Boot port 8080 already in use by finding the process using the port, stopping it safely, or changing server.port in application properties.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-fatal-authentication-failed/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-git-fatal-authentication-failed/git-authentication-failed-hero.png</image:loc>
      <image:title>Git fatal: Authentication failed 오류 해결 방법</image:title>
      <image:caption>Git fatal: Authentication failed 오류를 remote URL, HTTPS token, SSH key, credential cache, repository 권한 순서로 점검해 해결합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-fatal-authentication-failed/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-git-fatal-authentication-failed/git-authentication-failed-hero.png</image:loc>
      <image:title>How to Fix Git fatal: Authentication failed for HTTPS Remotes</image:title>
      <image:caption>Fix Git fatal: Authentication failed by checking the remote URL, replacing password authentication with a token or SSH key, clearing stale credentials, and testing push access.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/github-pages-jekyll-build-failed/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-github-pages-jekyll-build-failed/github-pages-jekyll-build-failed-hero.png</image:loc>
      <image:title>GitHub Pages Jekyll build failed 해결 방법</image:title>
      <image:caption>GitHub Pages Jekyll build failed 오류를 Pages workflow log, _config.yml YAML, front matter date, include, plugin, Sass, local Jekyll build 기준으로 해결하는 방법입니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/github-pages-jekyll-build-failed/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-github-pages-jekyll-build-failed/github-pages-jekyll-build-failed-hero.png</image:loc>
      <image:title>Fix GitHub Pages Jekyll Build Failed</image:title>
      <image:caption>Fix GitHub Pages Jekyll build failed errors by checking Pages workflow logs, _config.yml YAML, front matter dates, includes, plugins, Sass, and local Jekyll builds.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/image-labeling-project-plan/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-image-labeling-project-plan/hero.png</image:loc>
      <image:title>이미지 라벨링 프로젝트 계획서: 수집, 라벨링, 검수, 학습을 한 흐름으로 묶기</image:title>
      <image:caption>이미지 라벨링 프로젝트는 라벨링 화면에서 시작하지 않고 목표 정의, 데이터 수집, 기준 문서, 검수, 학습 피드백 루프로 설계해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/github-actions-build-failed/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-github-actions-build-failed/github-actions-build-failed-hero.png</image:loc>
      <image:title>GitHub Actions build failed 해결 방법</image:title>
      <image:caption>GitHub Actions build failed 오류를 실패한 step log, workflow YAML, dependency install command, runner version, secret, branch trigger 기준으로 해결하는 방법입니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/image-labeling-project-plan/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-image-labeling-project-plan/hero.png</image:loc>
      <image:title>Image Labeling Project Plan: Connect Collection, Annotation, QA, and Training</image:title>
      <image:caption>An image labeling project should start before the labeling screen, with objective, collection, instructions, QA, and training feedback designed as one loop.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/github-actions-build-failed/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-github-actions-build-failed/github-actions-build-failed-hero.png</image:loc>
      <image:title>How to Fix GitHub Actions Build Failed</image:title>
      <image:caption>Fix GitHub Actions build failed errors by reading the failed step log, checking workflow YAML, dependency install commands, runner versions, secrets, and branch triggers.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/ai-procurement-vendor-evaluation/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-procurement-vendor-evaluation/hero.png</image:loc>
      <image:title>AI Vendor Evaluation: 데모보다 데이터, 보안, 탈출 비용 묻기</image:title>
      <image:caption>AI 벤더 평가는 멋진 데모보다 데이터 처리, 모델 변경, 보안 통제, 로그, 계약 종료 시 이전 비용을 확인해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/ai-procurement-vendor-evaluation/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-procurement-vendor-evaluation/hero.png</image:loc>
      <image:title>AI Vendor Evaluation: Ask About Data, Security, and Exit Cost</image:title>
      <image:caption>AI vendor evaluation should check data handling, model changes, security controls, logs, and exit cost before demo polish.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/economic-calendar-for-households/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-economic-calendar-for-households/hero.png</image:loc>
      <image:title>가계를 위한 경제 캘린더: CPI, 고용, 금리, 환율 발표일 정리</image:title>
      <image:caption>경제 캘린더를 만들면 물가, 고용, 금리, 환율 발표가 대출, 예산, 환전, 소비 계획에 주는 영향을 미리 점검할 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/economic-calendar-for-households/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-economic-calendar-for-households/hero.png</image:loc>
      <image:title>Economic Calendar for Households: CPI, Jobs, Rates, and Exchange Rates</image:title>
      <image:caption>A household economic calendar helps connect CPI, jobs, rate decisions, and exchange-rate moves to loans, budgets, travel money, and spending plans.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/browser-based-labeling-pros-cons/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-browser-based-labeling-pros-cons/hero.png</image:loc>
      <image:title>브라우저 기반 라벨링 도구 장단점: 설치 없음과 파일 접근 권한 사이의 균형</image:title>
      <image:caption>브라우저 기반 라벨링은 설치 부담을 줄이지만 파일 접근 권한, 브라우저 지원, 저장 위치, 대용량 작업 기준을 확인해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/browser-based-labeling-pros-cons/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-browser-based-labeling-pros-cons/hero.png</image:loc>
      <image:title>Browser-Based Labeling Tools: Balance No Install with File Access Control</image:title>
      <image:caption>Browser-based labeling reduces installation friction, but file permissions, browser support, save location, and large-batch limits must be checked.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/nist-ai-rmf-team-checklist/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-nist-ai-rmf-team-checklist/hero.png</image:loc>
      <image:title>NIST AI RMF Team Checklist: 거버넌스를 문서가 아니라 운영 루틴으로 만들기</image:title>
      <image:caption>NIST AI RMF는 AI 리스크를 지도화, 측정, 관리, 거버넌스 루틴으로 나눠 팀 운영에 적용하기 좋다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/nist-ai-rmf-team-checklist/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-nist-ai-rmf-team-checklist/hero.png</image:loc>
      <image:title>NIST AI RMF Team Checklist: Turn Governance into Operating Routines</image:title>
      <image:caption>The NIST AI RMF helps teams translate AI risk into mapping, measuring, managing, and governance routines.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/global-dollar-liquidity-basics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-global-dollar-liquidity-basics/hero.png</image:loc>
      <image:title>달러 유동성 기초: 미국 금리가 세계 금융여건에 미치는 영향</image:title>
      <image:caption>달러 금리와 유동성은 신흥국 환율, 외채 비용, 원자재 가격, 글로벌 투자심리에 영향을 줄 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/global-dollar-liquidity-basics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-global-dollar-liquidity-basics/hero.png</image:loc>
      <image:title>Global Dollar Liquidity: How U.S. Rates Shape Financial Conditions</image:title>
      <image:caption>Dollar rates and liquidity can influence emerging-market currencies, external debt costs, commodity prices, and global risk appetite.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/dataset-handoff-for-training/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-dataset-handoff-for-training/hero.png</image:loc>
      <image:title>라벨링 팀에서 학습 팀으로 데이터 넘기기: handoff 문서에 들어갈 것</image:title>
      <image:caption>데이터셋 handoff는 압축 파일 전달이 아니라 버전, 클래스 규칙, 분할 방식, 알려진 한계, 검수 결과를 함께 넘기는 과정이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/dataset-handoff-for-training/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-dataset-handoff-for-training/hero.png</image:loc>
      <image:title>Dataset Handoff for Training Teams: What to Include in the Handoff Document</image:title>
      <image:caption>Dataset handoff is not just sending a zip file; it should include version, class rules, split method, known limits, and QA results.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/typescript-tsconfig-paths-not-working/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-typescript-tsconfig-paths-not-working/typescript-tsconfig-paths-not-working-hero.png</image:loc>
      <image:title>tsconfig paths가 동작하지 않을 때 해결 방법</image:title>
      <image:caption>tsconfig paths가 동작하지 않을 때 baseUrl, paths pattern, 실제 tsconfig, Vite alias, test runner alias, Node runtime resolution을 확인하는 방법입니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/small-business-break-even-inflation/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-small-business-break-even-inflation/hero.png</image:loc>
      <image:title>소상공인 손익분기점과 물가: 매출보다 마진을 먼저 지키기</image:title>
      <image:caption>물가와 임대료, 인건비, 원재료비가 오르면 매출이 늘어도 손익분기점이 올라 실제 이익은 줄 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/labeler-onboarding-checklist/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-labeler-onboarding-checklist/hero.png</image:loc>
      <image:title>라벨러 온보딩 체크리스트: 첫날부터 같은 기준으로 작업하게 만들기</image:title>
      <image:caption>새 라벨러는 도구 사용법보다 클래스 기준, 예외 처리, 저장 규칙, 질문 경로를 먼저 익혀야 재작업을 줄일 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/eu-ai-act-business-checklist/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-eu-ai-act-business-checklist/hero.png</image:loc>
      <image:title>EU AI Act Business Checklist: 유럽 고객이 없어도 볼 이유</image:title>
      <image:caption>EU AI Act는 유럽 사업자만의 문제가 아니라 글로벌 고객, 공급망, 벤더 계약, 제품 문서 요구로 번질 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/typescript-tsconfig-paths-not-working/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-typescript-tsconfig-paths-not-working/typescript-tsconfig-paths-not-working-hero.png</image:loc>
      <image:title>tsconfig Paths Not Working: How to Fix Path Aliases</image:title>
      <image:caption>Fix tsconfig paths not working by checking baseUrl, paths patterns, active tsconfig files, Vite aliases, test runner aliases, and Node runtime resolution.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/small-business-break-even-inflation/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-small-business-break-even-inflation/hero.png</image:loc>
      <image:title>Small Business Break-Even and Inflation: Protect Margin Before Revenue</image:title>
      <image:caption>When rent, wages, and input costs rise, higher sales can still leave a small business with less profit because break-even moves up.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/labeler-onboarding-checklist/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-labeler-onboarding-checklist/hero.png</image:loc>
      <image:title>Labeler Onboarding Checklist: Start New Annotators with the Same Standard</image:title>
      <image:caption>New labelers need class rules, edge-case handling, save rules, and question paths before tool speed, otherwise rework increases.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/eu-ai-act-business-checklist/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-eu-ai-act-business-checklist/hero.png</image:loc>
      <image:title>EU AI Act Business Checklist: Why Non-EU Teams Should Watch It</image:title>
      <image:caption>The EU AI Act can affect global customers, supply chains, vendor contracts, and product documentation beyond EU-only teams.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/ai-copyright-training-data-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-copyright-training-data-risk/hero.png</image:loc>
      <image:title>AI Copyright와 Training Data Risk: 생성물보다 입력 자료 기록부터</image:title>
      <image:caption>AI 저작권 리스크는 생성물만 보는 것이 아니라 입력 자료의 권리, 사용 목적, 보관, 공개 범위를 함께 관리해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/ai-copyright-training-data-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-copyright-training-data-risk/hero.png</image:loc>
      <image:title>AI Copyright and Training Data Risk: Track Inputs Before Outputs</image:title>
      <image:caption>AI copyright risk requires managing input rights, purpose, retention, and publication scope, not only the generated output.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/household-balance-sheet-basics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-household-balance-sheet-basics/hero.png</image:loc>
      <image:title>가계 재무상태표: 소득보다 자산, 부채, 유동성을 함께 보기</image:title>
      <image:caption>가계의 경제 안전성은 월소득뿐 아니라 현금, 예금, 투자자산, 부채, 보험, 유동성의 조합으로 결정된다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/household-balance-sheet-basics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-household-balance-sheet-basics/hero.png</image:loc>
      <image:title>Household Balance Sheet Basics: Assets, Debt, and Liquidity</image:title>
      <image:caption>Household resilience depends on cash, deposits, investments, debt, insurance, and liquidity, not only monthly income.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/qa-before-yolo-training/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-qa-before-yolo-training/hero.png</image:loc>
      <image:title>YOLO 학습 전 QA 루틴: 데이터 오류를 모델 문제로 착각하지 않기</image:title>
      <image:caption>YOLO 학습 전 QA는 라벨 누락, 클래스 순서 오류, 이미지 손상, 분할 누수, 극단적 박스를 먼저 잡아 모델 실험 시간을 아낀다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/qa-before-yolo-training/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-qa-before-yolo-training/hero.png</image:loc>
      <image:title>QA Before YOLO Training: Do Not Mistake Data Errors for Model Problems</image:title>
      <image:caption>QA before YOLO training catches missing labels, class-order mistakes, corrupt images, split leakage, and extreme boxes before model time is wasted.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/ai-health-information-triage-limits/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-health-information-triage-limits/hero.png</image:loc>
      <image:title>AI Health Information Triage 한계: 증상 설명과 진단을 분리하기</image:title>
      <image:caption>건강 정보 AI는 질문 정리와 일반 정보 안내에는 도움이 되지만 진단, 치료, 복용량 판단은 의료진 확인이 필요하다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/ai-health-information-triage-limits/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-health-information-triage-limits/hero.png</image:loc>
      <image:title>AI Health Information Triage Limits: Separate Symptom Explanation from Diagnosis</image:title>
      <image:caption>Health-information AI can organize questions and general information, but diagnosis, treatment, and dosage decisions require medical professionals.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/nominal-vs-real-gdp/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-nominal-vs-real-gdp/hero.png</image:loc>
      <image:title>명목 GDP와 실질 GDP: 성장과 물가 효과를 분리하기</image:title>
      <image:caption>명목 GDP는 현재 가격 기준 규모를 보여 주고 실질 GDP는 물가 효과를 제거해 생산량 변화를 보려는 지표다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/nominal-vs-real-gdp/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-nominal-vs-real-gdp/hero.png</image:loc>
      <image:title>Nominal vs Real GDP: Separate Growth from Price Effects</image:title>
      <image:caption>Nominal GDP measures output at current prices, while real GDP adjusts for inflation to estimate changes in production volume.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/edge-case-gallery-dataset/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-edge-case-gallery-dataset/hero.png</image:loc>
      <image:title>Edge Case Gallery 만들기: 애매한 라벨 기준을 이미지로 고정하는 법</image:title>
      <image:caption>Edge case gallery는 애매한 객체, 가림, 작은 물체, 클래스 혼동 사례를 모아 라벨러와 검수자가 같은 기준을 보게 하는 자료다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/edge-case-gallery-dataset/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-edge-case-gallery-dataset/hero.png</image:loc>
      <image:title>Build an Edge Case Gallery: Freeze Ambiguous Label Rules with Images</image:title>
      <image:caption>An edge-case gallery collects ambiguous objects, occlusion, small objects, and class confusion examples so labelers and reviewers share one standard.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/typescript-property-does-not-exist/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-typescript-property-does-not-exist/typescript-property-does-not-exist-hero.png</image:loc>
      <image:title>TypeScript Property does not exist on type 오류 해결 방법</image:title>
      <image:caption>TypeScript Property does not exist on type 오류를 object type, API response type, union narrowing, nullable DOM value, unsafe any cast 기준으로 해결하는 방법입니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/label-format-migration-plan/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-label-format-migration-plan/hero.png</image:loc>
      <image:title>라벨 포맷 전환 계획: YOLO, COCO, CVAT 사이를 오갈 때 지킬 기준</image:title>
      <image:caption>라벨 포맷 전환은 단순 변환 명령이 아니라 좌표 체계, 클래스 ID, 메타데이터, 지원하지 않는 속성 손실을 점검하는 마이그레이션이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/core-vs-headline-inflation/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-core-vs-headline-inflation/hero.png</image:loc>
      <image:title>근원물가와 헤드라인 물가: 에너지·식품 변동을 따로 보는 이유</image:title>
      <image:caption>헤드라인 물가는 전체 생활비 압력을 보여 주고 근원물가는 일시적 에너지·식품 변동을 제외한 추세를 보려는 지표다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/ai-legal-contract-review-limits/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-legal-contract-review-limits/hero.png</image:loc>
      <image:title>AI Contract Review 한계: 조항 요약과 법률 판단을 분리하기</image:title>
      <image:caption>계약서 AI는 조항 요약, 누락 탐지, 질문 목록에는 유용하지만 법률 판단과 협상 책임을 대신할 수 없다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/typescript-property-does-not-exist/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-typescript-property-does-not-exist/typescript-property-does-not-exist-hero.png</image:loc>
      <image:title>Fix Property Does Not Exist on Type</image:title>
      <image:caption>Fix TypeScript Property does not exist on type errors by correcting object types, API response types, union narrowing, nullable DOM values, and unsafe any casts.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/label-format-migration-plan/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-label-format-migration-plan/hero.png</image:loc>
      <image:title>Label Format Migration Plan: Move Between YOLO, COCO, and CVAT Safely</image:title>
      <image:caption>Label format migration is not just a conversion command; coordinate systems, class IDs, metadata, and unsupported attributes must be checked.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/core-vs-headline-inflation/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-core-vs-headline-inflation/hero.png</image:loc>
      <image:title>Core vs Headline Inflation: Why Food and Energy Are Read Separately</image:title>
      <image:caption>Headline inflation shows broad cost pressure, while core inflation tries to reveal trend pressure excluding volatile food and energy.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/ai-legal-contract-review-limits/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-legal-contract-review-limits/hero.png</image:loc>
      <image:title>AI Contract Review Limits: Separate Clause Summary from Legal Judgment</image:title>
      <image:caption>Contract-review AI can summarize clauses, flag omissions, and draft questions, but it cannot replace legal judgment or negotiation responsibility.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/ai-hr-screening-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-hr-screening-risk/hero.png</image:loc>
      <image:title>AI HR Screening Risk: 채용 자동화에서 설명 가능성과 차별 위험 보기</image:title>
      <image:caption>채용 AI는 속도보다 평가 기준, 데이터 편향, 설명 가능성, 이의제기 경로를 먼저 갖춰야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/ai-hr-screening-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-hr-screening-risk/hero.png</image:loc>
      <image:title>AI HR Screening Risk: Watch Explainability and Discrimination</image:title>
      <image:caption>Hiring AI needs criteria, bias checks, explainability, and appeal paths before speed.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/consumer-sentiment-economic-signal/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-consumer-sentiment-economic-signal/hero.png</image:loc>
      <image:title>소비심리 지표 읽기: 기분과 실제 소비를 구분하기</image:title>
      <image:caption>소비심리는 가계가 느끼는 불안을 보여 주지만 실제 소비, 소득, 고용, 물가와 함께 봐야 해석이 정확하다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/consumer-sentiment-economic-signal/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-consumer-sentiment-economic-signal/hero.png</image:loc>
      <image:title>Consumer Sentiment as an Economic Signal: Separate Mood from Spending</image:title>
      <image:caption>Consumer sentiment shows household anxiety, but it should be read with actual spending, income, jobs, and inflation.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/exporting-yolo-training-ready/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-exporting-yolo-training-ready/hero.png</image:loc>
      <image:title>YOLO 학습 준비 export 체크리스트: 라벨링 끝난 뒤 바로 훈련하지 말아야 하는 이유</image:title>
      <image:caption>라벨링이 끝나도 학습 전에는 폴더 구조, 클래스 순서, 빈 라벨, 손상 이미지, 검증 샘플을 확인해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/exporting-yolo-training-ready/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-exporting-yolo-training-ready/hero.png</image:loc>
      <image:title>YOLO Training-Ready Export Checklist: Do Not Train Immediately After Labeling</image:title>
      <image:caption>After labeling, training should wait until folder structure, class order, empty labels, corrupt images, and validation samples are checked.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/ai-education-study-tutor/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-education-study-tutor/hero.png</image:loc>
      <image:title>AI Study Tutor 설계: 정답 대신 힌트, 회상, 오답 분석</image:title>
      <image:caption>AI 튜터는 정답을 바로 주기보다 힌트 단계, 능동 회상, 오답 원인, 다음 복습 계획을 만드는 데 강점을 둬야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/ai-education-study-tutor/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-education-study-tutor/hero.png</image:loc>
      <image:title>AI Study Tutor Design: Hints, Recall, and Mistake Analysis</image:title>
      <image:caption>AI tutors are strongest when they guide hints, active recall, mistake causes, and next review plans instead of giving answers immediately.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/learning-with-ai-safely/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-learning-with-ai-safely/hero.png</image:loc>
      <image:title>AI로 공부할 때 주의점: 답을 받기보다 질문과 피드백에 쓰기</image:title>
      <image:caption>AI 학습 도구는 정답을 바로 받는 용도보다 회상 질문 만들기, 설명 점검, 힌트 단계, 오답 분석에 쓸 때 학습 루프를 해치지 않는다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/deposit-insurance-bank-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-deposit-insurance-bank-risk/hero.png</image:loc>
      <image:title>예금자보호와 은행 리스크: 금리보다 안전 한도를 먼저 확인하기</image:title>
      <image:caption>예금 선택에서는 높은 금리뿐 아니라 예금자보호 대상, 한도, 계좌 소유 구조, 만기 유동성을 확인해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/learning-with-ai-safely/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-learning-with-ai-safely/hero.png</image:loc>
      <image:title>Learning with AI Safely: Use It for Questions and Feedback</image:title>
      <image:caption>AI study tools are more useful for recall prompts, explanation checks, staged hints, and mistake analysis than for instant answers.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/deposit-insurance-bank-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-deposit-insurance-bank-risk/hero.png</image:loc>
      <image:title>Deposit Insurance and Bank Risk: Check Safety Limits Before Yield</image:title>
      <image:caption>Deposit decisions should consider insurance coverage, limits, account ownership, and maturity liquidity alongside yield.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/augmentation-label-safety/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-augmentation-label-safety/hero.png</image:loc>
      <image:title>데이터 증강 전 라벨 안전성: 회전, 자르기, 뒤집기가 박스를 망가뜨리지 않게 하기</image:title>
      <image:caption>데이터 증강은 모델 일반화에 도움이 될 수 있지만 회전, 자르기, 확대가 라벨 박스와 클래스 의미를 깨지 않는지 확인해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/augmentation-label-safety/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-augmentation-label-safety/hero.png</image:loc>
      <image:title>Label Safety Before Data Augmentation: Keep Boxes Valid After Crop and Flip</image:title>
      <image:caption>Data augmentation can help generalization, but rotation, cropping, and scaling must not break boxes or class meaning.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/typescript-cannot-find-name/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-typescript-cannot-find-name/typescript-cannot-find-name-hero.png</image:loc>
      <image:title>TypeScript Cannot find name 오류 해결 방법</image:title>
      <image:caption>TypeScript TS2304 Cannot find name 오류를 import, type package, tsconfig lib와 types 설정, global name, 실제 config 기준으로 해결하는 방법입니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/privacy-local-labeling/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-privacy-local-labeling/hero.png</image:loc>
      <image:title>민감한 이미지 라벨링과 로컬 우선 작업: 업로드 전에 확인할 보안 기준</image:title>
      <image:caption>민감한 이미지 라벨링은 업로드 편의성보다 접근 권한, 저장 위치, 삭제 기준, 익명화 가능성을 먼저 확인해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/exam-day-checklist/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-exam-day-checklist/hero.png</image:loc>
      <image:title>시험 당일 체크리스트: 새 공부보다 실수 방지에 집중하기</image:title>
      <image:caption>시험 당일에는 새로운 범위를 무리하게 넣기보다 준비물, 시간, 쉬운 문제, 검토 순서, 컨디션을 확인하는 것이 안전하다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/emergency-budget-job-loss/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-emergency-budget-job-loss/hero.png</image:loc>
      <image:title>실직 대비 비상 예산: 평상시 예산과 위기 예산을 나누기</image:title>
      <image:caption>실직 가능성에 대비하려면 평상시 예산과 별도로 필수비, 중단 가능한 지출, 현금화 순서, 지원 제도를 정리해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/ai-sales-research-workflow/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-sales-research-workflow/hero.png</image:loc>
      <image:title>AI Sales Research Workflow: 리드 점수보다 근거와 최신성 확인</image:title>
      <image:caption>영업 리서치 AI는 리드 점수보다 출처 날짜, 회사 변화, 담당자 근거, 연락 금지 조건을 먼저 확인해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/typescript-cannot-find-name/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-typescript-cannot-find-name/typescript-cannot-find-name-hero.png</image:loc>
      <image:title>Fix TypeScript Cannot Find Name</image:title>
      <image:caption>Fix TS2304 Cannot find name in TypeScript by checking imports, type packages, tsconfig lib and types settings, globals, and the correct project config.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/privacy-local-labeling/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-privacy-local-labeling/hero.png</image:loc>
      <image:title>Sensitive Image Labeling and Local-First Work: Security Checks Before Uploads</image:title>
      <image:caption>Sensitive image labeling should check access rights, storage location, deletion rules, and anonymization before upload convenience.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/exam-day-checklist/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-exam-day-checklist/hero.png</image:loc>
      <image:title>Exam Day Checklist: Prevent Mistakes Instead of Adding New Study</image:title>
      <image:caption>On exam day, checking materials, timing, easy items, review order, and condition is safer than forcing new material.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/emergency-budget-job-loss/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-emergency-budget-job-loss/hero.png</image:loc>
      <image:title>Emergency Budget for Job Loss: Separate Normal and Crisis Spending</image:title>
      <image:caption>A job-loss budget separates essential costs, pausable spending, cash drawdown order, and support programs from the normal budget.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/ai-sales-research-workflow/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-sales-research-workflow/hero.png</image:loc>
      <image:title>AI Sales Research Workflow: Check Evidence and Freshness</image:title>
      <image:caption>Sales research AI should check source dates, company changes, contact evidence, and do-not-contact rules before scoring leads.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/ai-customer-support-knowledge-base/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-customer-support-knowledge-base/hero.png</image:loc>
      <image:title>AI Customer Support Knowledge Base: 답변 자동화보다 근거 연결</image:title>
      <image:caption>고객지원 AI는 빠른 답변보다 정책 문서, 계정 상태, 예외 조건, 상담원 승인 경로를 정확히 연결해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/ai-customer-support-knowledge-base/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-customer-support-knowledge-base/hero.png</image:loc>
      <image:title>AI Customer Support Knowledge Base: Connect Answers to Evidence</image:title>
      <image:caption>Customer-support AI must connect policy documents, account state, exceptions, and agent approval paths before it speeds up replies.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/trade-tariff-household-prices/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-trade-tariff-household-prices/hero.png</image:loc>
      <image:title>관세와 생활물가: 무역정책이 소비자 가격으로 오는 경로</image:title>
      <image:caption>관세는 수입업체 비용, 환율, 유통마진, 대체재 가격을 거쳐 소비자 가격과 기업 선택에 영향을 준다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/habit-stack-study-routine/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-habit-stack-study-routine/hero.png</image:loc>
      <image:title>공부 습관 쌓기: 큰 목표보다 시작 신호와 첫 10분</image:title>
      <image:caption>공부 습관은 의욕이 아니라 같은 시간, 같은 시작 신호, 첫 10분 과제, 완료 기록을 반복할 때 유지되기 쉽다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/trade-tariff-household-prices/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-trade-tariff-household-prices/hero.png</image:loc>
      <image:title>Tariffs and Household Prices: How Trade Policy Reaches Consumers</image:title>
      <image:caption>Tariffs affect consumer prices through importer costs, exchange rates, margins, substitutes, and business sourcing decisions.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/habit-stack-study-routine/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-habit-stack-study-routine/hero.png</image:loc>
      <image:title>Habit Stack Study Routine: Start Signal and First Ten Minutes</image:title>
      <image:caption>A study habit is easier to keep when time, start signal, first ten-minute task, and completion log repeat.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/annotation-cost-estimation/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-annotation-cost-estimation/hero.png</image:loc>
      <image:title>이미지 라벨링 비용 산정: 장당 시간이 아니라 재작업률까지 계산하기</image:title>
      <image:caption>라벨링 비용은 이미지 수와 장당 시간만으로 끝나지 않으며 지침 작성, 검수, 재작업, 포맷 변환, 데이터 정리 시간을 포함해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/annotation-cost-estimation/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-annotation-cost-estimation/hero.png</image:loc>
      <image:title>Annotation Cost Estimation: Count Rework, Not Only Time Per Image</image:title>
      <image:caption>Annotation cost is not only image count times time per image; instructions, QA, rework, conversion, and cleanup should be included.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/voice-realtime-ai-use-cases/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-voice-realtime-ai-use-cases/hero.png</image:loc>
      <image:title>Voice와 Realtime AI Use Cases: 빠른 응답보다 중단 규칙이 먼저다</image:title>
      <image:caption>실시간 음성 AI는 지연시간이 낮을수록 유용하지만 결제, 의료, 법률, 신원확인 같은 상황에서는 중단 규칙이 더 중요하다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/voice-realtime-ai-use-cases/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-voice-realtime-ai-use-cases/hero.png</image:loc>
      <image:title>Voice and Realtime AI Use Cases: Stop Rules Before Speed</image:title>
      <image:caption>Realtime voice AI benefits from low latency, but stop rules matter more in payment, medical, legal, or identity contexts.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/spaced-review-for-coding/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-spaced-review-for-coding/hero.png</image:loc>
      <image:title>코딩 개념 Spaced Review: 문법을 프로젝트 안에서 다시 쓰기</image:title>
      <image:caption>코딩 개념 복습은 플래시카드만이 아니라 며칠 뒤 작은 기능을 다시 구현해 문법과 사용 맥락을 함께 확인하는 방식이 좋다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/global-growth-forecast-how-to-read/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-global-growth-forecast-how-to-read/hero.png</image:loc>
      <image:title>세계 성장률 전망 읽기: IMF·OECD·World Bank 숫자가 다른 이유</image:title>
      <image:caption>세계 성장률 전망은 기관별 기준일, 국가 범위, 환율 기준, 위험 가정이 달라 숫자가 서로 다를 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/spaced-review-for-coding/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-spaced-review-for-coding/hero.png</image:loc>
      <image:title>Spaced Review for Coding Concepts: Reuse Syntax in Projects</image:title>
      <image:caption>Coding review works well when a concept is reused in a small feature days later, combining syntax with context.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/global-growth-forecast-how-to-read/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-global-growth-forecast-how-to-read/hero.png</image:loc>
      <image:title>How to Read Global Growth Forecasts from IMF, OECD, and World Bank</image:title>
      <image:caption>Global growth forecasts differ because institutions use different cut-off dates, country coverage, exchange-rate assumptions, and risk scenarios.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/model-error-analysis-labeling/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-model-error-analysis-labeling/hero.png</image:loc>
      <image:title>모델 오류 분석으로 라벨링 개선하기: 오탐과 미탐을 다음 작업으로 바꾸기</image:title>
      <image:caption>모델 오류 분석은 성능표를 보는 데서 끝나지 않고 오탐, 미탐, 클래스 혼동 이미지를 다음 라벨링 작업으로 바꾸는 과정이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/model-error-analysis-labeling/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-model-error-analysis-labeling/hero.png</image:loc>
      <image:title>Improve Labeling with Model Error Analysis: Turn FP and FN into Next Work</image:title>
      <image:caption>Model error analysis should turn false positives, false negatives, and class confusion images into the next labeling tasks.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/reading-comprehension-prompts/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-reading-comprehension-prompts/hero.png</image:loc>
      <image:title>독해력 질문 프롬프트: 글을 읽고 주장, 근거, 반례를 찾기</image:title>
      <image:caption>독해력은 문장을 많이 읽는 것만으로 늘지 않고 주장, 근거, 전제, 반례를 질문으로 확인할 때 깊어진다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/node-cannot-find-module/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-node-cannot-find-module/node-cannot-find-module-hero.png</image:loc>
      <image:title>Node.js Cannot find module 오류 해결 방법</image:title>
      <image:caption>Node.js Cannot find module 오류를 패키지 설치, 상대 경로, 실행 위치, CommonJS와 ESM 문법, package exports 기준으로 해결하는 방법입니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/multimodal-ai-workflow/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-multimodal-ai-workflow/hero.png</image:loc>
      <image:title>Multimodal AI Workflow: 텍스트, 이미지, 음성을 한 번에 믿지 않기</image:title>
      <image:caption>멀티모달 AI는 입력이 풍부해질수록 오류 경로도 늘어나므로 텍스트, 이미지, 음성의 검증 기준을 따로 둬야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/inflation-expectations-guide/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-inflation-expectations-guide/hero.png</image:loc>
      <image:title>기대 인플레이션 읽기: 사람들이 믿는 물가가 실제 물가에 미치는 영향</image:title>
      <image:caption>기대 인플레이션은 임금 협상, 가격 책정, 중앙은행 신뢰, 장기 금리에 영향을 주는 중요한 경제 신호다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/dataset-folder-structure/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-dataset-folder-structure/hero.png</image:loc>
      <image:title>객체 탐지 데이터셋 폴더 구조: images와 labels를 안전하게 맞추기</image:title>
      <image:caption>객체 탐지 데이터셋은 이미지와 라벨의 상대 위치가 맞아야 하며 train, val, test 폴더가 서로 섞이지 않아야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/reading-comprehension-prompts/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-reading-comprehension-prompts/hero.png</image:loc>
      <image:title>Reading Comprehension Prompts: Find Claims, Evidence, and Counterexamples</image:title>
      <image:caption>Reading comprehension deepens when claims, evidence, assumptions, and counterexamples are checked with prompts.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/node-cannot-find-module/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-node-cannot-find-module/node-cannot-find-module-hero.png</image:loc>
      <image:title>Fix Cannot Find Module in Node.js</image:title>
      <image:caption>Fix Node.js Cannot find module errors by checking missing packages, relative paths, working directory, CommonJS and ESM syntax, and package export paths.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/multimodal-ai-workflow/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-multimodal-ai-workflow/hero.png</image:loc>
      <image:title>Multimodal AI Workflow: Verify Text, Image, and Audio Separately</image:title>
      <image:caption>Multimodal AI adds value and error paths, so text, image, and audio need separate verification rules.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/inflation-expectations-guide/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-inflation-expectations-guide/hero.png</image:loc>
      <image:title>Inflation Expectations: Why Beliefs About Prices Matter</image:title>
      <image:caption>Inflation expectations influence wage bargaining, price setting, central-bank credibility, and long-term interest rates.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/dataset-folder-structure/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-dataset-folder-structure/hero.png</image:loc>
      <image:title>Object Detection Dataset Folder Structure: Keep Images and Labels Aligned</image:title>
      <image:caption>An object detection dataset needs aligned image and label paths, and train, val, and test folders must not be mixed.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/ai-content-provenance-watermark/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-content-provenance-watermark/hero.png</image:loc>
      <image:title>AI Content Provenance: 워터마크보다 제작 경로와 검토 기록 남기기</image:title>
      <image:caption>AI 콘텐츠 신뢰성은 워터마크 하나보다 생성 도구, 원본 자료, 편집자, 검토 날짜를 함께 기록할 때 높아진다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/ai-content-provenance-watermark/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-content-provenance-watermark/hero.png</image:loc>
      <image:title>AI Content Provenance: Keep Creation Path and Review Records</image:title>
      <image:caption>AI content trust improves when generation tool, source material, editor, and review date are recorded together.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/research-note-citation-system/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-research-note-citation-system/hero.png</image:loc>
      <image:title>리서치 노트와 출처 관리: 복붙보다 요약과 인용 기준</image:title>
      <image:caption>리서치 노트는 자료를 복사해 모으는 공간이 아니라 핵심 주장, 내 말 요약, 출처, 사용할 위치를 함께 남기는 시스템이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/productivity-wage-growth/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-productivity-wage-growth/hero.png</image:loc>
      <image:title>생산성과 임금: 경제가 좋아져도 임금이 늦게 움직이는 이유</image:title>
      <image:caption>생산성 증가는 장기 임금 여력을 높일 수 있지만 산업 구조, 협상력, 물가, 고용 형태에 따라 체감 속도가 달라진다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/research-note-citation-system/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-research-note-citation-system/hero.png</image:loc>
      <image:title>Research Note and Citation System: Summarize Before Quoting</image:title>
      <image:caption>A research note system records the claim, your paraphrase, source, and planned use instead of collecting copied text.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/productivity-wage-growth/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-productivity-wage-growth/hero.png</image:loc>
      <image:title>Productivity and Wages: Why Pay Can Lag a Better Economy</image:title>
      <image:caption>Productivity growth can support wages over time, but industry structure, bargaining power, inflation, and job type shape the pass-through.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/label-version-control/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-label-version-control/hero.png</image:loc>
      <image:title>라벨 버전 관리: 데이터셋 v1, v2를 되돌릴 수 있게 만드는 방법</image:title>
      <image:caption>라벨 버전 관리는 모델 실험을 재현하기 위해 이미지, 라벨, 클래스 파일, 지침서를 같은 버전으로 묶어 보관하는 작업이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/label-version-control/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-label-version-control/hero.png</image:loc>
      <image:title>Label Version Control: Make Dataset v1 and v2 Reversible</image:title>
      <image:caption>Label version control keeps images, labels, class files, and instructions tied to one version so model experiments can be reproduced.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/llm-security-prompt-injection/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-llm-security-prompt-injection/hero.png</image:loc>
      <image:title>LLM Prompt Injection 대응: 지시문보다 권한과 데이터 경계를 먼저 막기</image:title>
      <image:caption>프롬프트 인젝션은 문장 필터만으로 막기 어렵고 도구 권한, 검색 자료, 출력 처리, 승인 흐름을 함께 제한해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/llm-security-prompt-injection/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-llm-security-prompt-injection/hero.png</image:loc>
      <image:title>LLM Prompt Injection Defense: Bound Permissions and Data First</image:title>
      <image:caption>Prompt injection cannot be solved by text filters alone; tool permissions, retrieved data, output handling, and approvals must be bounded.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/supply-chain-shock-inflation/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-supply-chain-shock-inflation/hero.png</image:loc>
      <image:title>공급망 충격과 물가: 운임, 재고, 대체 공급처를 같이 보기</image:title>
      <image:caption>공급망 충격은 운임, 배송 지연, 재고 비용, 대체 공급처 비용을 통해 소비자 가격으로 이어질 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/metacognition-study-log/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-metacognition-study-log/hero.png</image:loc>
      <image:title>Metacognition 공부 로그: 안다고 느낀 것과 실제 회상을 비교하기</image:title>
      <image:caption>메타인지 공부 로그는 자신감 점수와 실제 회상 점수를 비교해 착각한 단원과 과신한 문제를 찾는 기록이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/supply-chain-shock-inflation/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-supply-chain-shock-inflation/hero.png</image:loc>
      <image:title>Supply Chain Shocks and Inflation: Freight, Inventories, and Substitutes</image:title>
      <image:caption>Supply-chain shocks can move into consumer prices through freight, delays, inventory costs, and expensive substitute suppliers.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/metacognition-study-log/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-metacognition-study-log/hero.png</image:loc>
      <image:title>Metacognition Study Log: Compare Confidence with Recall</image:title>
      <image:caption>A metacognition log compares confidence with actual recall so overconfident topics and weak units become visible.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/rotated-bounding-box-decision/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-rotated-bounding-box-decision/hero.png</image:loc>
      <image:title>Rotated Bounding Box가 필요한 경우: 기울어진 객체를 일반 박스로 충분히 표현할 수 있을까</image:title>
      <image:caption>기울어진 물체가 많은 데이터셋에서는 일반 박스가 배경을 많이 포함할 수 있으므로 OBB 지원 여부와 학습 목표를 먼저 확인해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/rotated-bounding-box-decision/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-rotated-bounding-box-decision/hero.png</image:loc>
      <image:title>When Rotated Bounding Boxes Matter: Are Regular Boxes Enough?</image:title>
      <image:caption>Datasets with many angled objects may include too much background in regular boxes, so OBB support and the training objective should be checked first.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/study-group-rules/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-study-group-rules/hero.png</image:loc>
      <image:title>스터디 그룹 규칙: 친목보다 문제 풀이와 피드백을 남기기</image:title>
      <image:caption>스터디 그룹은 모이는 횟수보다 각자 풀어온 문제, 설명, 피드백, 다음 과제가 남을 때 학습 효과가 커진다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/segmentation-vs-detection-labels/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-segmentation-vs-detection-labels/hero.png</image:loc>
      <image:title>Segmentation과 Detection 라벨 선택: 박스가 충분한지 마스크가 필요한지 판단하기</image:title>
      <image:caption>객체 탐지 박스와 세그멘테이션 마스크는 비용과 활용 목적이 다르므로 라벨링 전에 모델 목표와 필요한 정밀도를 분리해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-npm-err-eresolve/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-javascript-npm-err-eresolve/javascript-npm-err-eresolve-hero.png</image:loc>
      <image:title>npm ERR! ERESOLVE 오류 해결 방법</image:title>
      <image:caption>npm ERR ERESOLVE 오류를 peer dependency 충돌 확인, 패키지 버전 정렬, lockfile 갱신, legacy-peer-deps 임시 사용 기준으로 해결하는 방법입니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/credit-card-interest-minimum-payment/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-credit-card-interest-minimum-payment/hero.png</image:loc>
      <image:title>신용카드 이자와 최소결제: 잔액이 오래 남는 구조 이해하기</image:title>
      <image:caption>최소결제만 반복하면 원금이 천천히 줄고 이자가 누적되어 작은 소비도 장기 부채가 될 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/ai-data-privacy-redaction/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-data-privacy-redaction/hero.png</image:loc>
      <image:title>AI Data Privacy Redaction: 프롬프트에 넣기 전 줄여야 할 개인정보</image:title>
      <image:caption>AI 입력 데이터는 보내기 전에 목적, 최소 필요 정보, 식별자, 보관 기간을 기준으로 줄여야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/study-group-rules/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-study-group-rules/hero.png</image:loc>
      <image:title>Study Group Rules: Leave Problem Solving and Feedback</image:title>
      <image:caption>A study group works when it leaves solved problems, explanations, feedback, and next tasks, not only attendance.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/segmentation-vs-detection-labels/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-segmentation-vs-detection-labels/hero.png</image:loc>
      <image:title>Segmentation vs Detection Labels: Decide Whether Boxes Are Enough</image:title>
      <image:caption>Detection boxes and segmentation masks have different costs and use cases, so model objective and required precision should be separated before labeling.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-npm-err-eresolve/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-javascript-npm-err-eresolve/javascript-npm-err-eresolve-hero.png</image:loc>
      <image:title>How to Fix npm ERR ERESOLVE</image:title>
      <image:caption>Fix npm ERR ERESOLVE by identifying the peer dependency conflict, aligning package versions, refreshing the lockfile, and using legacy-peer-deps only when needed.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/credit-card-interest-minimum-payment/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-credit-card-interest-minimum-payment/hero.png</image:loc>
      <image:title>Credit Card Interest and Minimum Payments: Why Balances Last</image:title>
      <image:caption>Repeated minimum payments reduce principal slowly and let interest accumulate, turning small purchases into long-lasting debt.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/ai-data-privacy-redaction/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-data-privacy-redaction/hero.png</image:loc>
      <image:title>AI Data Privacy Redaction: Reduce Sensitive Data Before Prompting</image:title>
      <image:caption>AI input data should be reduced before prompting based on purpose, minimum necessary fields, identifiers, and retention period.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/ai-workflow-cost-control/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-workflow-cost-control/hero.png</image:loc>
      <image:title>AI Workflow Cost Control: 토큰보다 재시도, 검색, 검토 비용을 함께 보기</image:title>
      <image:caption>AI 비용 관리는 토큰 단가보다 재시도 횟수, 검색 저장소, 도구 호출, 사람 검토 시간이 누적될 때 중요해진다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/ai-workflow-cost-control/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-workflow-cost-control/hero.png</image:loc>
      <image:title>AI Workflow Cost Control: Track Retries, Retrieval, and Review</image:title>
      <image:caption>AI cost control depends on retries, retrieval storage, tool calls, and review time, not only token price.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/mortgage-rate-rent-affordability/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-mortgage-rate-rent-affordability/hero.png</image:loc>
      <image:title>주택담보대출 금리와 임대료: 집값보다 월 부담액 먼저 계산하기</image:title>
      <image:caption>주거비 판단은 집값, 전세금, 월세만이 아니라 금리, 보증금 기회비용, 관리비, 소득 안정성을 함께 계산해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/distraction-audit-study/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-distraction-audit-study/hero.png</image:loc>
      <image:title>공부 방해요인 감사: 의지보다 환경과 트리거를 고치기</image:title>
      <image:caption>방해요인 감사는 집중 실패를 의지 문제로 끝내지 않고 알림, 장소, 도구, 시작 조건을 바꾸는 절차다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/mortgage-rate-rent-affordability/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-mortgage-rate-rent-affordability/hero.png</image:loc>
      <image:title>Mortgage Rates and Rent Affordability: Calculate Monthly Burden First</image:title>
      <image:caption>Housing affordability depends on price, rent, rates, deposit opportunity cost, fees, and income stability together.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/distraction-audit-study/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-distraction-audit-study/hero.png</image:loc>
      <image:title>Study Distraction Audit: Fix Environment and Triggers Before Willpower</image:title>
      <image:caption>A distraction audit turns focus failure into changes to notifications, place, tools, and start conditions.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/video-frame-extraction-labeling/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-video-frame-extraction-labeling/hero.png</image:loc>
      <image:title>비디오 프레임 라벨링: 너무 많은 비슷한 장면을 줄이는 추출 기준</image:title>
      <image:caption>비디오에서 프레임을 추출할 때는 시간 간격, 장면 변화, 객체 다양성, 중복 제거 기준을 정해야 라벨링 비용을 줄일 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/video-frame-extraction-labeling/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-video-frame-extraction-labeling/hero.png</image:loc>
      <image:title>Video Frame Labeling: Extract Frames Without Flooding the Dataset</image:title>
      <image:caption>When extracting frames from video, time interval, scene change, object diversity, and duplicate cleanup rules reduce labeling cost.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/ai-agent-human-in-loop/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-agent-human-in-loop/hero.png</image:loc>
      <image:title>Human-in-the-Loop AI: 사람 검토를 병목이 아니라 안전장치로 설계하기</image:title>
      <image:caption>사람 검토는 모든 결과를 다시 읽는 일이 아니라 위험도에 따라 승인, 샘플링, 예외 처리로 나누는 통제 장치다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/ai-agent-human-in-loop/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-agent-human-in-loop/hero.png</image:loc>
      <image:title>Human-in-the-Loop AI: Design Review as a Safety Control</image:title>
      <image:caption>Human review should be a risk-based control with approval, sampling, and exception handling, not rereading every output.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/sleep-study-performance/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-sleep-study-performance/hero.png</image:loc>
      <image:title>수면과 공부 성과: 밤샘보다 기억과 집중을 보호하기</image:title>
      <image:caption>수면은 학습과 기억, 집중에 영향을 주므로 시험 전 밤샘은 단기 공부 시간을 늘려도 다음 날 수행을 해칠 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/savings-rate-real-interest-rate/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-savings-rate-real-interest-rate/hero.png</image:loc>
      <image:title>저축금리와 실질금리: 예금 이자가 물가를 이기는지 확인하기</image:title>
      <image:caption>예금금리가 높아 보여도 세금과 물가를 빼면 실제 구매력 증가가 작거나 마이너스일 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/sleep-study-performance/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-sleep-study-performance/hero.png</image:loc>
      <image:title>Sleep and Study Performance: Protect Memory and Attention</image:title>
      <image:caption>Sleep affects learning, memory, and attention, so all-nighters can add study time while weakening next-day performance.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/savings-rate-real-interest-rate/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-savings-rate-real-interest-rate/hero.png</image:loc>
      <image:title>Savings Rates and Real Interest: Check Whether Interest Beats Inflation</image:title>
      <image:caption>A high deposit rate can still produce little or negative purchasing-power growth after taxes and inflation.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/prelabeling-human-review/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-prelabeling-human-review/hero.png</image:loc>
      <image:title>Pre-labeling과 사람 검수: 자동 라벨을 그대로 믿지 않는 워크플로우</image:title>
      <image:caption>모델이 미리 그린 박스는 속도를 높일 수 있지만 클래스 혼동, 작은 객체 누락, 과신 오류를 사람이 검수해야 학습 데이터로 쓸 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/prelabeling-human-review/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-prelabeling-human-review/hero.png</image:loc>
      <image:title>Pre-Labeling and Human Review: Do Not Trust Auto Labels Without QA</image:title>
      <image:caption>Model-generated boxes can speed up work, but class confusion, missed small objects, and overconfident mistakes need human QA before training use.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/retrieval-vector-store-governance/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-retrieval-vector-store-governance/hero.png</image:loc>
      <image:title>Retrieval과 Vector Store 거버넌스: 문서 수집보다 삭제와 버전 관리</image:title>
      <image:caption>벡터 저장소는 문서를 많이 넣는 것보다 소스 버전, 삭제 지연, 접근권한, 검색 품질을 관리할 때 신뢰할 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-externally-managed-environment/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-python-externally-managed-environment/python-externally-managed-environment-hero.png</image:loc>
      <image:title>Python externally-managed-environment 오류 해결 방법</image:title>
      <image:caption>Python externally-managed-environment 오류를 시스템 Python을 건드리지 않고 가상환경, pipx, package manager로 안전하게 해결하는 방법입니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/exam-time-management/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-exam-time-management/hero.png</image:loc>
      <image:title>시험 시간 관리: 어려운 문제보다 시간 손실 지점을 먼저 찾기</image:title>
      <image:caption>시험 시간 관리는 빨리 푸는 요령이 아니라 문제별 제한 시간, 넘길 기준, 재검토 순서를 미리 정하는 전략이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/dollar-won-exchange-rate-checklist/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-dollar-won-exchange-rate-checklist/hero.png</image:loc>
      <image:title>원달러 환율 체크리스트: 뉴스 한 줄보다 금리차, 유가, 수지를 같이 보기</image:title>
      <image:caption>원달러 환율은 금리차, 에너지 가격, 수출입, 위험선호, 외국인 자금 흐름이 동시에 반영되는 가격이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/active-learning-labeling-loop/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-active-learning-labeling-loop/hero.png</image:loc>
      <image:title>Active Learning 라벨링 루프: 모델이 어려워한 이미지부터 다시 라벨링하기</image:title>
      <image:caption>Active learning은 모든 이미지를 같은 순서로 라벨링하지 않고 모델의 낮은 확신, 오탐, 미탐 샘플을 우선 검수하는 반복 루프다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/retrieval-vector-store-governance/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-retrieval-vector-store-governance/hero.png</image:loc>
      <image:title>Retrieval and Vector Store Governance: Version and Delete, Not Only Upload</image:title>
      <image:caption>Vector stores become trustworthy when source versions, deletion lag, access rights, and search quality are managed.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-externally-managed-environment/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-python-externally-managed-environment/python-externally-managed-environment-hero.png</image:loc>
      <image:title>How to Fix externally-managed-environment in Python</image:title>
      <image:caption>Fix Python&apos;s externally-managed-environment error safely by using a virtual environment, pipx, or the system package manager instead of breaking system Python.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/exam-time-management/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-exam-time-management/hero.png</image:loc>
      <image:title>Exam Time Management: Find Where Time Leaks Before Hard Problems</image:title>
      <image:caption>Exam timing is not a speed trick; it sets per-question limits, skip rules, and review order before the test.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/dollar-won-exchange-rate-checklist/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-dollar-won-exchange-rate-checklist/hero.png</image:loc>
      <image:title>Dollar-Won Exchange Rate Checklist: Rates, Oil, and External Balance</image:title>
      <image:caption>The dollar-won rate reflects rate differentials, energy prices, trade flows, risk appetite, and foreign capital movements together.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/active-learning-labeling-loop/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-active-learning-labeling-loop/hero.png</image:loc>
      <image:title>Active Learning Labeling Loop: Relabel the Images Your Model Finds Hard</image:title>
      <image:caption>Active learning avoids labeling every image in order; it prioritizes low-confidence, false-positive, and false-negative samples for review.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/ai-evals-scorecard/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-evals-scorecard/hero.png</image:loc>
      <image:title>AI Evals Scorecard: 데모가 아니라 회귀 테스트로 품질을 관리하기</image:title>
      <image:caption>AI 평가는 데모 질문 몇 개가 아니라 기준 데이터, 평가자, 실패 유형, 릴리스 차단 기준을 가진 회귀 테스트여야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/ai-evals-scorecard/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-evals-scorecard/hero.png</image:loc>
      <image:title>AI Evals Scorecard: Manage Quality with Regression Tests</image:title>
      <image:caption>AI evaluation should be a regression test with benchmark data, graders, failure types, and release gates, not a few demo prompts.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/flashcard-quality-rules/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-flashcard-quality-rules/hero.png</image:loc>
      <image:title>Flashcard 품질 규칙: 카드 수보다 한 카드 한 질문</image:title>
      <image:caption>Flashcard는 많이 만드는 것보다 한 카드에 하나의 질문, 짧은 답, 문맥, 실패 기록을 유지할 때 복습 효율이 높다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/fiscal-deficit-public-debt/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-fiscal-deficit-public-debt/hero.png</image:loc>
      <image:title>재정적자와 국가채무: 좋은 지출과 지속가능성을 같이 보기</image:title>
      <image:caption>재정적자는 경기 충격을 완충할 수 있지만 이자비용, 성장률, 세입 기반, 고령화 지출과 함께 봐야 지속가능성을 판단할 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/flashcard-quality-rules/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-flashcard-quality-rules/hero.png</image:loc>
      <image:title>Flashcard Quality Rules: One Card, One Question</image:title>
      <image:caption>Flashcards work better when each card keeps one question, a short answer, context, and failure history.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/fiscal-deficit-public-debt/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-fiscal-deficit-public-debt/hero.png</image:loc>
      <image:title>Fiscal Deficits and Public Debt: Read Support and Sustainability Together</image:title>
      <image:caption>Fiscal deficits can cushion shocks, but sustainability depends on interest costs, growth, revenue base, and aging-related spending.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/class-imbalance-dataset/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-class-imbalance-dataset/hero.png</image:loc>
      <image:title>클래스 불균형 데이터셋: 많이 찍힌 클래스만 잘 맞는 문제 줄이기</image:title>
      <image:caption>클래스 불균형은 흔한 객체만 잘 맞는 모델을 만들 수 있으므로 라벨링 단계에서 빈도, 난이도, 검증 표본을 함께 관리해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/class-imbalance-dataset/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-class-imbalance-dataset/hero.png</image:loc>
      <image:title>Class Imbalance in Datasets: Reduce Models That Only Learn Frequent Classes</image:title>
      <image:caption>Class imbalance can produce models that work only for frequent objects, so frequency, difficulty, and validation samples must be tracked during labeling.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/structured-outputs-json-schema/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-structured-outputs-json-schema/hero.png</image:loc>
      <image:title>Structured Outputs와 JSON Schema: 파싱 성공보다 의미 검증이 중요하다</image:title>
      <image:caption>구조화 출력은 JSON 파싱 실패를 줄여 주지만 값의 의미, 누락 필드, 업무 규칙 위반은 별도 검증해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/structured-outputs-json-schema/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-structured-outputs-json-schema/hero.png</image:loc>
      <image:title>Structured Outputs and JSON Schema: Validate Meaning, Not Only Parsing</image:title>
      <image:caption>Structured outputs reduce parsing failures, but meaning, missing fields, and business-rule violations still need validation.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/semiconductor-cycle-korea-economy/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-semiconductor-cycle-korea-economy/hero.png</image:loc>
      <image:title>반도체 경기와 한국 경제: 수출 호황이 모두에게 같지 않은 이유</image:title>
      <image:caption>반도체 수출은 한국 성장률을 끌어올릴 수 있지만 고용, 내수, 중소기업, 지역경제로 전달되는 속도는 다르다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/language-shadowing-routine/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-language-shadowing-routine/hero.png</image:loc>
      <image:title>Language Shadowing 루틴: 따라 말하기를 녹음과 피드백으로 바꾸기</image:title>
      <image:caption>Shadowing은 그냥 따라 말하는 시간이 아니라 원본, 내 녹음, 차이 표시, 재녹음이 반복될 때 발음과 리듬을 점검할 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/semiconductor-cycle-korea-economy/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-semiconductor-cycle-korea-economy/hero.png</image:loc>
      <image:title>Semiconductor Cycle and Korea: Why Export Booms Feel Uneven</image:title>
      <image:caption>Semiconductor exports can lift Korean growth, but the pass-through to jobs, domestic demand, SMEs, and regions can be uneven.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/language-shadowing-routine/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-language-shadowing-routine/hero.png</image:loc>
      <image:title>Language Shadowing Routine: Turn Repetition into Recorded Feedback</image:title>
      <image:caption>Shadowing becomes useful when the original, your recording, gap notes, and rerecording form a feedback loop.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/duplicate-image-cleanup/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-duplicate-image-cleanup/hero.png</image:loc>
      <image:title>중복 이미지 정리: 라벨링 전에 near-duplicate를 줄여야 하는 이유</image:title>
      <image:caption>중복 이미지는 라벨링 비용을 늘리고 검증 점수를 부풀릴 수 있으므로 작업 전 파일명, 해시, 시각적 유사도를 기준으로 정리해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/duplicate-image-cleanup/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-duplicate-image-cleanup/hero.png</image:loc>
      <image:title>Duplicate Image Cleanup: Why Near-Duplicates Should Be Reduced Before Labeling</image:title>
      <image:caption>Duplicate images increase labeling cost and can inflate validation scores, so filenames, hashes, and visual similarity should be checked before labeling.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-command-not-found-windows/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-python-command-not-found-windows/python-command-not-found-windows-hero.png</image:loc>
      <image:title>Windows에서 python 명령어가 안 될 때 해결 방법</image:title>
      <image:caption>Windows에서 python 명령어가 안 될 때 py launcher, PATH, App Execution Alias, 현재 Python 설치 경로를 확인해 해결하는 방법입니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/project-based-learning-portfolio/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-project-based-learning-portfolio/hero.png</image:loc>
      <image:title>프로젝트 기반 공부 포트폴리오: 결과물과 회고를 함께 남기기</image:title>
      <image:caption>프로젝트 공부는 완성작만 올리는 것이 아니라 문제 정의, 구현 결정, 막힌 지점, 다음 개선을 함께 남길 때 포트폴리오가 된다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/openai-responses-api-guide/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-openai-responses-api-guide/hero.png</image:loc>
      <image:title>OpenAI Responses API 실무 가이드: 입력, 도구, 구조화 출력을 한 흐름으로 보기</image:title>
      <image:caption>Responses API는 모델 응답, 도구 호출, 구조화 출력, 멀티모달 입력을 하나의 워크플로우로 설계할 때 이해하기 쉽다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/oil-price-import-inflation/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-oil-price-import-inflation/hero.png</image:loc>
      <image:title>유가와 수입물가: 국제유가가 전기요금과 장바구니까지 오는 경로</image:title>
      <image:caption>유가 상승은 원유 수입액, 정제비, 전기·가스요금, 운송비, 식품가격을 거쳐 생활비로 번질 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/negative-images-for-detection/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-negative-images-for-detection/hero.png</image:loc>
      <image:title>객체가 없는 이미지도 필요한 이유: YOLO negative sample 설계</image:title>
      <image:caption>객체가 없는 이미지는 모델이 배경을 객체로 착각하는 문제를 줄이는 데 도움이 되며, 실제 배포 환경의 배경을 반영해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-command-not-found-windows/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-python-command-not-found-windows/python-command-not-found-windows-hero.png</image:loc>
      <image:title>Python Command Not Found on Windows: How to Fix It</image:title>
      <image:caption>Fix python command not found on Windows by checking the py launcher, PATH, App Execution Aliases, and the active Python installation.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/project-based-learning-portfolio/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-project-based-learning-portfolio/hero.png</image:loc>
      <image:title>Project-Based Learning Portfolio: Keep Output and Reflection Together</image:title>
      <image:caption>Project-based study becomes a portfolio when the problem, implementation decisions, blockers, and next improvements are recorded.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/openai-responses-api-guide/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-openai-responses-api-guide/hero.png</image:loc>
      <image:title>OpenAI Responses API Practical Guide: Inputs, Tools, and Structured Outputs</image:title>
      <image:caption>The Responses API is easier to understand when model output, tools, structured output, and multimodal input are designed as one workflow.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/oil-price-import-inflation/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-oil-price-import-inflation/hero.png</image:loc>
      <image:title>Oil Prices and Import Inflation: From Crude Markets to Household Bills</image:title>
      <image:caption>Higher oil prices can pass through crude imports, refining, power and gas bills, transport costs, and food prices.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/negative-images-for-detection/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-negative-images-for-detection/hero.png</image:loc>
      <image:title>Why Object Detection Needs Negative Images: Design YOLO Negative Samples</image:title>
      <image:caption>Negative images help reduce false positives by teaching the model real deployment backgrounds where target objects are absent.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/local-llm-vs-cloud-llm/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-local-llm-vs-cloud-llm/hero.png</image:loc>
      <image:title>Local LLM vs Cloud LLM: 비용보다 데이터, 지연시간, 운영 책임 먼저 보기</image:title>
      <image:caption>로컬 LLM과 클라우드 LLM 선택은 가격 비교가 아니라 데이터 민감도, 지연시간, 품질, 운영 책임의 균형이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/local-llm-vs-cloud-llm/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-local-llm-vs-cloud-llm/hero.png</image:loc>
      <image:title>Local LLM vs Cloud LLM: Compare Data, Latency, and Operations First</image:title>
      <image:caption>Choosing local or cloud LLMs is a balance of data sensitivity, latency, quality, and operating responsibility, not only price.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/current-account-trade-balance/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-current-account-trade-balance/hero.png</image:loc>
      <image:title>경상수지와 무역수지: 수출이 좋아도 환율이 흔들릴 수 있는 이유</image:title>
      <image:caption>무역수지는 상품 수출입만 보지만 경상수지는 서비스, 소득, 이전까지 포함해 외화 흐름을 더 넓게 보여 준다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/coding-kata-deliberate-practice/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-coding-kata-deliberate-practice/hero.png</image:loc>
      <image:title>Coding Kata 루틴: 같은 문제를 다르게 풀어 패턴을 익히기</image:title>
      <image:caption>Coding kata는 문제 수를 늘리는 훈련이 아니라 같은 작은 문제를 조건, 시간, 가독성 기준을 바꿔 반복하는 연습이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/current-account-trade-balance/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-current-account-trade-balance/hero.png</image:loc>
      <image:title>Current Account and Trade Balance: Why Exports Do Not Explain Everything</image:title>
      <image:caption>The trade balance tracks goods and services trade, while the current account adds income and transfers to show broader external flows.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/coding-kata-deliberate-practice/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-coding-kata-deliberate-practice/hero.png</image:loc>
      <image:title>Coding Kata Routine: Solve the Same Problem in Better Ways</image:title>
      <image:caption>A coding kata is not about many problems; it repeats a small problem with different constraints, time limits, and readability goals.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/occlusion-truncation-labeling/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-occlusion-truncation-labeling/hero.png</image:loc>
      <image:title>가림과 잘림 객체 라벨링: occlusion, truncation 기준을 문서화하기</image:title>
      <image:caption>가려진 객체와 화면 밖으로 잘린 객체는 프로젝트마다 다르게 처리되므로 라벨링 전에 포함 기준과 박스 범위를 문서화해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/occlusion-truncation-labeling/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-occlusion-truncation-labeling/hero.png</image:loc>
      <image:title>Occlusion and Truncation Labeling: Document Edge-Case Rules</image:title>
      <image:caption>Occluded and truncated objects are handled differently by project, so include rules and box extent must be documented before labeling.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/ai-tools-function-calling/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-tools-function-calling/hero.png</image:loc>
      <image:title>AI Tool Calling vs Function Calling: 모델 출력과 실제 실행을 분리하기</image:title>
      <image:caption>도구 호출은 모델이 외부 시스템과 연결되는 지점이므로 스키마, 권한, 검증, 실행 로그를 함께 설계해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/ai-tools-function-calling/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-tools-function-calling/hero.png</image:loc>
      <image:title>AI Tool Calling vs Function Calling: Separate Model Output from Execution</image:title>
      <image:caption>Tool calling connects a model to external systems, so schema, permissions, validation, and logs must be designed together.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/writing-revision-study-loop/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-writing-revision-study-loop/hero.png</image:loc>
      <image:title>글쓰기 공부 루프: 초안, 피드백, 재작성으로 실력 만들기</image:title>
      <image:caption>글쓰기 실력은 좋은 문장 읽기만으로 늘지 않고 초안, 기준표, 피드백, 재작성 기록이 반복될 때 개선된다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/household-debt-service-ratio/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-household-debt-service-ratio/hero.png</image:loc>
      <image:title>가계부채 부담 읽기: 대출 잔액보다 월 상환액이 먼저다</image:title>
      <image:caption>가계부채 위험은 총잔액만이 아니라 소득 대비 원리금 상환액, 변동금리 비중, 만기 구조로 판단해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/writing-revision-study-loop/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-writing-revision-study-loop/hero.png</image:loc>
      <image:title>Writing Revision Study Loop: Draft, Feedback, Rewrite</image:title>
      <image:caption>Writing improves when drafting, criteria, feedback, and revision records repeat, not from reading good prose alone.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/household-debt-service-ratio/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-household-debt-service-ratio/hero.png</image:loc>
      <image:title>Household Debt Burden: Monthly Payments Matter Before Balances</image:title>
      <image:caption>Household debt risk depends on payments relative to income, variable-rate exposure, and maturity structure, not only total balances.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/small-object-labeling/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-small-object-labeling/hero.png</image:loc>
      <image:title>작은 객체 라벨링 기준: 보이는 물체와 학습 가능한 물체를 구분하기</image:title>
      <image:caption>작은 객체는 박스 오차가 모델 학습에 크게 작용하므로 최소 픽셀 크기, 확대 기준, 제외 기준을 먼저 정해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/small-object-labeling/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-small-object-labeling/hero.png</image:loc>
      <image:title>Small Object Labeling Rules: Separate Visible Objects from Learnable Objects</image:title>
      <image:caption>Small objects are sensitive to box error, so minimum pixel size, zoom rules, and exclusion rules should be decided before labeling.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-venv-not-activating/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-python-venv-not-activating/python-venv-not-activating-hero.png</image:loc>
      <image:title>Python venv가 활성화되지 않을 때 해결 방법</image:title>
      <image:caption>Python venv 활성화 문제를 shell별 명령 확인, PowerShell 실행 정책 수정, 현재 인터프리터 경로 검증으로 해결하는 방법입니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/math-problem-solving-routine/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-math-problem-solving-routine/hero.png</image:loc>
      <image:title>수학 문제 풀이 루틴: 공식 암기보다 조건 해석 먼저</image:title>
      <image:caption>수학 공부는 공식을 더 외우는 것보다 문제 조건, 사용할 방법, 검산, 오답 원인을 일정한 순서로 남길 때 안정된다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/bond-yield-curve-basics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-bond-yield-curve-basics/hero.png</image:loc>
      <image:title>채권 금리와 수익률 곡선: 장단기 금리가 말하는 경기 기대</image:title>
      <image:caption>수익률 곡선은 단기 정책금리 기대와 장기 성장·물가·위험 프리미엄을 함께 반영한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/annotation-review-sampling/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-annotation-review-sampling/hero.png</image:loc>
      <image:title>라벨 검수 샘플링: 모든 이미지를 다시 보지 않고 품질을 잡는 법</image:title>
      <image:caption>라벨 검수는 전수 확인만 답이 아니며 클래스, 라벨러, 촬영 조건, 모델 오류 유형별로 샘플을 뽑아 반복 문제를 찾을 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/ai-meeting-notes-workflow/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-meeting-notes-workflow/hero.png</image:loc>
      <image:title>AI Meeting Notes Workflow: 회의록을 결정, 담당자, 기한으로 바꾸기</image:title>
      <image:caption>AI 회의록은 요약보다 결정 사항, 담당자, 기한, 미해결 질문을 정확히 분리할 때 업무 가치가 커진다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-venv-not-activating/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-python-venv-not-activating/python-venv-not-activating-hero.png</image:loc>
      <image:title>Python venv Not Activating: How to Fix It</image:title>
      <image:caption>Fix Python venv activation problems by using the right shell command, checking PowerShell policy, and verifying the active interpreter path.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/math-problem-solving-routine/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-math-problem-solving-routine/hero.png</image:loc>
      <image:title>Math Problem-Solving Routine: Read Conditions Before Formulas</image:title>
      <image:caption>Math study improves when conditions, method choice, checking, and error causes are recorded in a stable order.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/bond-yield-curve-basics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-bond-yield-curve-basics/hero.png</image:loc>
      <image:title>Bond Yields and the Yield Curve: What Short and Long Rates Signal</image:title>
      <image:caption>The yield curve reflects expected short rates, long-run growth, inflation, and risk premiums together.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/annotation-review-sampling/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-annotation-review-sampling/hero.png</image:loc>
      <image:title>Annotation Review Sampling: Catch Quality Issues Without Rechecking Everything</image:title>
      <image:caption>Annotation review does not require checking every image; sampling by class, labeler, capture condition, and model error can reveal repeat issues.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/ai-meeting-notes-workflow/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-meeting-notes-workflow/hero.png</image:loc>
      <image:title>AI Meeting Notes Workflow: Turn Calls into Decisions, Owners, and Deadlines</image:title>
      <image:caption>AI meeting notes are valuable when they separate decisions, owners, deadlines, and unresolved questions, not when they only summarize.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/ai-coding-agent-workflow/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-coding-agent-workflow/hero.png</image:loc>
      <image:title>AI Coding Agent Workflow: 코드 품질을 잃지 않는 에이전트 사용법</image:title>
      <image:caption>코딩 에이전트는 작은 이슈, 명확한 테스트, 좁은 diff, 리뷰 가능한 커밋 단위가 있을 때 가장 안전하다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/ai-coding-agent-workflow/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-coding-agent-workflow/hero.png</image:loc>
      <image:title>AI Coding Agent Workflow: Use Agents Without Losing Code Quality</image:title>
      <image:caption>Coding agents are safest with small issues, clear tests, narrow diffs, and reviewable commit boundaries.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/lecture-review-24-hour/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-lecture-review-24-hour/hero.png</image:loc>
      <image:title>강의 후 24시간 리뷰: 잊기 전에 회상 질문 만들기</image:title>
      <image:caption>강의 직후 24시간 안에 필기를 정리하고 질문으로 바꾸면 다음 복습에서 다시 읽기보다 회상을 시작할 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/central-bank-meeting-how-to-read/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-central-bank-meeting-how-to-read/hero.png</image:loc>
      <image:title>중앙은행 회의 읽는 법: 결정문, 전망, 기자회견을 분리하기</image:title>
      <image:caption>중앙은행 회의는 금리 결정뿐 아니라 결정문 문구, 경제전망, 기자회견의 위험 균형을 함께 읽어야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/lecture-review-24-hour/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-lecture-review-24-hour/hero.png</image:loc>
      <image:title>24-Hour Lecture Review: Create Recall Questions Before Forgetting</image:title>
      <image:caption>Reviewing lecture notes within 24 hours and turning them into questions makes the next session retrieval-based.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/central-bank-meeting-how-to-read/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-central-bank-meeting-how-to-read/hero.png</image:loc>
      <image:title>How to Read a Central Bank Meeting: Statement, Projections, Press Conference</image:title>
      <image:caption>A central bank meeting includes the rate decision, statement language, projections, and the risk balance in the press conference.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/data-yaml-for-yolo/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-data-yaml-for-yolo/hero.png</image:loc>
      <image:title>YOLO data.yaml 작성법: 경로, 클래스 순서, 검증 오류 줄이기</image:title>
      <image:caption>`data.yaml`은 YOLO 학습에서 이미지 경로와 클래스 이름을 연결하는 계약서이므로 경로, 이름, 순서가 라벨 파일과 맞아야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/data-yaml-for-yolo/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-data-yaml-for-yolo/hero.png</image:loc>
      <image:title>YOLO data.yaml Guide: Paths, Class Order, and Validation Errors</image:title>
      <image:caption>`data.yaml` is the contract connecting image paths and class names in YOLO training, so paths, names, and order must match label files.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/ai-automation-roi/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-automation-roi/hero.png</image:loc>
      <image:title>AI Automation ROI: 자동화 전에 시간, 오류, 검토 비용부터 계산하기</image:title>
      <image:caption>AI 자동화 ROI는 절약 시간만이 아니라 검토 시간, 오류 비용, 재작업, 보안 통제 비용까지 함께 계산해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/ai-automation-roi/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-automation-roi/hero.png</image:loc>
      <image:title>AI Automation ROI: Count Time, Errors, and Review Cost First</image:title>
      <image:caption>AI automation ROI must include review time, error cost, rework, and security controls, not only saved hours.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/unemployment-rate-labor-market/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-unemployment-rate-labor-market/hero.png</image:loc>
      <image:title>실업률과 노동시장: 낮은 실업률만 보면 놓치는 신호</image:title>
      <image:caption>실업률은 중요하지만 고용률, 경제활동참가율, 임금, 근로시간을 함께 봐야 노동시장 압력을 이해할 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/textbook-reading-output/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-textbook-reading-output/hero.png</image:loc>
      <image:title>교재 읽기 루틴: 밑줄보다 질문, 요약, 예제로 남기기</image:title>
      <image:caption>교재 읽기는 밑줄 개수보다 읽기 전 질문, 읽은 뒤 요약, 직접 만든 예제가 남을 때 학습으로 이어진다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/unemployment-rate-labor-market/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-unemployment-rate-labor-market/hero.png</image:loc>
      <image:title>Unemployment Rate and Labor Market Signals Beyond the Headline</image:title>
      <image:caption>The unemployment rate matters, but employment, participation, wages, and hours worked are needed to understand labor-market pressure.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/textbook-reading-output/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-textbook-reading-output/hero.png</image:loc>
      <image:title>Textbook Reading Routine: Leave Questions, Summary, and Examples</image:title>
      <image:caption>Textbook reading becomes study when it leaves pre-questions, post-reading summaries, and self-made examples.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/dataset-split-train-val-test/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-dataset-split-train-val-test/hero.png</image:loc>
      <image:title>Train, Val, Test 데이터셋 분할: 이미지 라벨링 후 누수를 막는 기준</image:title>
      <image:caption>데이터셋 분할은 단순 비율 문제가 아니라 중복 이미지, 같은 촬영 환경, 같은 객체가 서로 다른 분할로 새지 않게 막는 품질 작업이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/dataset-split-train-val-test/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-dataset-split-train-val-test/hero.png</image:loc>
      <image:title>Train, Val, Test Dataset Split: Prevent Leakage After Image Labeling</image:title>
      <image:caption>Dataset splitting is not only a ratio; it prevents duplicate images, shared capture conditions, and the same object from leaking across splits.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-no-module-named-pip/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-python-no-module-named-pip/python-no-module-named-pip-hero.png</image:loc>
      <image:title>Python No module named pip 오류 해결 방법</image:title>
      <image:caption>Python의 No module named pip 오류를 ensurepip 실행, 현재 인터프리터 확인, 가상환경 복구로 해결하는 방법입니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/labeling-instructions-template/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-labeling-instructions-template/hero.png</image:loc>
      <image:title>라벨링 지침서 템플릿: 라벨러가 같은 기준으로 박스를 그리게 만드는 법</image:title>
      <image:caption>라벨링 지침서는 클래스 설명, 포함·제외 기준, 예외 이미지, 저장 규칙, 질문 처리 방법을 한 문서로 고정해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/gdp-components-guide/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-gdp-components-guide/hero.png</image:loc>
      <image:title>GDP 구성요소 읽기: 소비, 투자, 정부, 순수출을 나눠 보기</image:title>
      <image:caption>GDP 성장률은 하나의 숫자지만 그 안에는 소비, 기업투자, 주택, 정부지출, 수출입 변화가 섞여 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/cornell-note-taking-system/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-cornell-note-taking-system/hero.png</image:loc>
      <image:title>Cornell Note Taking: 필기를 복습 질문으로 바꾸는 구조</image:title>
      <image:caption>Cornell note 방식은 필기, 단서, 요약 영역을 나누어 강의 내용을 나중에 회상 질문으로 바꾸기 쉽게 만든다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/ai-search-optimization/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-search-optimization/hero.png</image:loc>
      <image:title>AI Search Optimization: 검색엔진보다 답변엔진이 읽기 쉬운 글 구조</image:title>
      <image:caption>AI 검색에 노출되려면 글이 질문, 짧은 답, 근거, 단계, 날짜, 출처를 명확히 드러내야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-no-module-named-pip/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-python-no-module-named-pip/python-no-module-named-pip-hero.png</image:loc>
      <image:title>How to Fix No module named pip in Python</image:title>
      <image:caption>Fix Python&apos;s No module named pip error by installing pip with ensurepip, checking the active interpreter, and repairing virtual environments.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/labeling-instructions-template/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-labeling-instructions-template/hero.png</image:loc>
      <image:title>Labeling Instructions Template: Make Labelers Draw Boxes the Same Way</image:title>
      <image:caption>A labeling instruction document should freeze class definitions, include and exclude rules, edge images, save rules, and question handling.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/gdp-components-guide/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-gdp-components-guide/hero.png</image:loc>
      <image:title>GDP Components: Read Consumption, Investment, Government, and Net Exports</image:title>
      <image:caption>GDP growth is one number, but it combines consumption, business investment, housing, government spending, and trade changes.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/cornell-note-taking-system/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-cornell-note-taking-system/hero.png</image:loc>
      <image:title>Cornell Note Taking: Turn Notes into Review Questions</image:title>
      <image:caption>The Cornell note system separates notes, cues, and summary so lecture material can become review questions later.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/ai-search-optimization/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-search-optimization/hero.png</image:loc>
      <image:title>AI Search Optimization: Structure Content for Answer Engines</image:title>
      <image:caption>AI search visibility improves when content exposes questions, short answers, evidence, steps, dates, and sources clearly.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/rag-evaluation-checklist/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-rag-evaluation-checklist/hero.png</image:loc>
      <image:title>RAG 평가 체크리스트: 검색이 맞았는지와 답변이 맞았는지를 나눠 보기</image:title>
      <image:caption>RAG 품질은 모델 답변만 보면 안 되고 검색 문서, 인용 위치, 누락 질문, 답변 충실도를 따로 측정해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/rag-evaluation-checklist/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-rag-evaluation-checklist/hero.png</image:loc>
      <image:title>RAG Evaluation Checklist: Separate Retrieval Quality from Answer Quality</image:title>
      <image:caption>RAG quality requires separate checks for retrieved documents, citation location, missing questions, and answer faithfulness.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/semester-study-calendar/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-semester-study-calendar/hero.png</image:loc>
      <image:title>학기 공부 캘린더: 시험 직전이 아니라 제출일에서 거꾸로 계획하기</image:title>
      <image:caption>학기 캘린더는 일정표가 아니라 시험, 과제, 복습, 휴식, 버퍼 시간을 거꾸로 배치하는 위험 관리 도구다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/cpi-vs-personal-inflation/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-cpi-vs-personal-inflation/hero.png</image:loc>
      <image:title>CPI와 개인 물가 차이: 공식 물가와 체감 물가가 다른 이유</image:title>
      <image:caption>CPI는 평균 소비 바구니를 추적하므로 주거, 식품, 교통 비중이 다른 개인의 체감 물가와 다를 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/semester-study-calendar/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-semester-study-calendar/hero.png</image:loc>
      <image:title>Semester Study Calendar: Plan Backward from Exams and Deadlines</image:title>
      <image:caption>A semester calendar is a risk-management tool that schedules exams, assignments, review, rest, and buffers backward.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/cpi-vs-personal-inflation/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-cpi-vs-personal-inflation/hero.png</image:loc>
      <image:title>CPI vs Personal Inflation: Why Official Inflation Feels Different</image:title>
      <image:caption>CPI tracks an average basket, so personal inflation can differ when housing, food, transport, or medical spending weights are different.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/bounding-box-quality-checklist/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-bounding-box-quality-checklist/hero.png</image:loc>
      <image:title>Bounding Box 품질 체크리스트: 느슨한 박스와 잘린 객체를 줄이는 법</image:title>
      <image:caption>박스 품질은 모델 성능의 상한을 정하므로 객체 경계, 가림, 잘림, 여백, 클래스 기준을 검수표로 반복 확인해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/bounding-box-quality-checklist/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-bounding-box-quality-checklist/hero.png</image:loc>
      <image:title>Bounding Box Quality Checklist: Reduce Loose Boxes and Cut Objects</image:title>
      <image:caption>Box quality sets a ceiling for model performance, so object borders, occlusion, truncation, padding, and class rules need repeatable review.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/prompt-engineering-checklist/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-prompt-engineering-checklist/hero.png</image:loc>
      <image:title>Prompt Engineering 체크리스트: 좋은 프롬프트보다 반복 가능한 입력 구조</image:title>
      <image:caption>프롬프트 품질은 멋진 문장보다 역할, 목적, 자료, 제약, 출력 형식이 항상 같은 순서로 들어갈 때 안정된다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/prompt-engineering-checklist/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-prompt-engineering-checklist/hero.png</image:loc>
      <image:title>Prompt Engineering Checklist: Build Repeatable Input Structure</image:title>
      <image:caption>Prompt quality improves when role, goal, context, constraints, and output format appear in a stable order.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/real-wage-purchasing-power/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-real-wage-purchasing-power/hero.png</image:loc>
      <image:title>실질임금과 구매력: 월급이 올랐는데 왜 빠듯한지 계산하기</image:title>
      <image:caption>월급 인상률이 물가 상승률보다 낮으면 명목 소득은 늘어도 실제 구매력은 줄어들 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/question-bank-system/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-question-bank-system/hero.png</image:loc>
      <image:title>질문은행 만들기: 필기노트를 회상 문제로 바꾸는 법</image:title>
      <image:caption>질문은행은 노트를 보관하는 폴더가 아니라 다음 복습 때 스스로 답해야 할 질문을 쌓는 시스템이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/real-wage-purchasing-power/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-real-wage-purchasing-power/hero.png</image:loc>
      <image:title>Real Wages and Purchasing Power: Why Raises Can Still Feel Tight</image:title>
      <image:caption>When wage growth trails inflation, nominal income can rise while actual purchasing power falls.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/question-bank-system/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-question-bank-system/hero.png</image:loc>
      <image:title>Question Bank System: Convert Notes into Recall Prompts</image:title>
      <image:caption>A question bank is not a note archive; it stores prompts you must answer in later review sessions.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/easy-labeling-yolo-dataset/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-easy-labeling-yolo-dataset/hero.png</image:loc>
      <image:title>Easy Labeling으로 YOLO 데이터셋 만들기: 이미지에서 학습 폴더까지</image:title>
      <image:caption>Easy Labeling은 브라우저에서 로컬 이미지를 열고 YOLO 박스를 저장할 수 있으므로 작은 샘플 검수부터 학습 폴더 구성까지 연결하기 좋다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/easy-labeling-yolo-dataset/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-easy-labeling-yolo-dataset/hero.png</image:loc>
      <image:title>Build a YOLO Dataset with Easy Labeling: From Images to Training Folders</image:title>
      <image:caption>Easy Labeling can open local images in the browser and save YOLO boxes, making it useful from small-sample review to training folder setup.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/recession-indicators-basics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-recession-indicators-basics/hero.png</image:loc>
      <image:title>경기 침체 지표 읽기: GDP, 고용, 소비를 한 번에 보기</image:title>
      <image:caption>경기 침체 신호는 GDP 한 줄이 아니라 고용, 실질소득, 소비, 기업투자, 금융여건이 동시에 약해지는지로 판단한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-pip-install-failed/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-python-pip-install-failed/python-pip-install-failed-hero.png</image:loc>
      <image:title>Python pip install 실패 해결 방법</image:title>
      <image:caption>pip install 실패 오류를 현재 Python 환경 확인, pip 업그레이드, 가상환경 사용, 정확한 오류 메시지 분석으로 해결하는 방법입니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/practice-test-review/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-practice-test-review/hero.png</image:loc>
      <image:title>모의고사 리뷰법: 점수보다 틀린 근거를 먼저 분해하기</image:title>
      <image:caption>모의고사는 점수 확인보다 시간 배분, 오답 원인, 찍은 문제, 헷갈린 개념을 분리할 때 다음 점수를 올린다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/local-image-labeling-workflow/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-local-image-labeling-workflow/hero.png</image:loc>
      <image:title>로컬 이미지 라벨링 워크플로우: 이미지, 클래스, 라벨, 검수 정리법</image:title>
      <image:caption>로컬 라벨링은 파일 업로드를 줄이고 민감한 이미지를 통제할 수 있지만 폴더 구조, 저장 규칙, 백업 기준을 먼저 정해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_ai_trends/ai-agent-workflow-2026/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-agent-workflow-2026/hero.png</image:loc>
      <image:title>AI Agent Workflow 2026: 자동화보다 검증 게이트 먼저 설계하기</image:title>
      <image:caption>AI 에이전트는 긴 프롬프트가 아니라 목표, 도구, 상태, 검증, 중단 규칙이 연결된 업무 시스템이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/recession-indicators-basics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-recession-indicators-basics/hero.png</image:loc>
      <image:title>Recession Indicators: Read GDP, Jobs, and Consumption Together</image:title>
      <image:caption>Recession signals are stronger when GDP, jobs, real income, consumption, investment, and financial conditions weaken together.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-pip-install-failed/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-python-pip-install-failed/python-pip-install-failed-hero.png</image:loc>
      <image:title>How to Fix pip install Failed in Python</image:title>
      <image:caption>Fix pip install failed errors by checking the active Python environment, upgrading pip, using a virtual environment, and reading the exact install error.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/practice-test-review/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-practice-test-review/hero.png</image:loc>
      <image:title>Practice Test Review: Break Down Evidence Before Chasing Scores</image:title>
      <image:caption>Practice tests improve future scores when timing, error causes, guessed items, and confused concepts are separated.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/local-image-labeling-workflow/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-local-image-labeling-workflow/hero.png</image:loc>
      <image:title>Local Image Labeling Workflow: Organize Images, Classes, Labels, and Review</image:title>
      <image:caption>Local labeling reduces uploads and keeps sensitive images under control, but folder structure, save rules, and backups must be defined first.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_ai_trends/ai-agent-workflow-2026/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-ai-agent-workflow-2026/hero.png</image:loc>
      <image:title>AI Agent Workflow 2026: Design Verification Before Automation</image:title>
      <image:caption>An AI agent is not a longer prompt; it is a work system connecting goals, tools, state, verification, and stop rules.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/interleaving-practice/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-interleaving-practice/hero.png</image:loc>
      <image:title>Interleaving Practice: 비슷한 문제를 섞어 진짜 구분력을 키우기</image:title>
      <image:caption>Interleaving은 같은 유형을 몰아서 푸는 대신 비슷한 유형을 섞어 어떤 방법을 써야 하는지 판단하는 연습이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/emergency-fund-how-much/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-emergency-fund-how-much/hero.png</image:loc>
      <image:title>비상금은 얼마가 적당할까: 3개월보다 먼저 봐야 할 생활비</image:title>
      <image:caption>비상금 목표는 몇 개월치라는 숫자보다 필수 생활비, 소득 안정성, 보험 공백, 부채 비용에 따라 달라진다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/interleaving-practice/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-interleaving-practice/hero.png</image:loc>
      <image:title>Interleaving Practice: Mix Similar Problems to Build Discrimination</image:title>
      <image:caption>Interleaving mixes similar problem types so learners practice choosing the method, not only repeating it.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/emergency-fund-how-much/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-emergency-fund-how-much/hero.png</image:loc>
      <image:title>How Much Emergency Fund Is Enough? Start With Essential Costs</image:title>
      <image:caption>Emergency fund targets depend on essential expenses, income stability, insurance gaps, and debt cost more than one fixed month rule.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/image-labeling-classes/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-image-labeling-classes/hero.png</image:loc>
      <image:title>이미지 라벨링 클래스 관리법: class name, ID, dataset consistency 지키기</image:title>
      <image:caption>클래스 관리는 모델 학습 전 가장 먼저 고정해야 하는 규칙이며, 이름보다 ID 순서와 예외 기준이 더 중요하다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/image-labeling-classes/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-image-labeling-classes/hero.png</image:loc>
      <image:title>Image Labeling Classes: Manage Names, IDs, and Dataset Consistency</image:title>
      <image:caption>Class management is the first rule to freeze before training; ID order and edge-case rules matter more than names alone.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/weekly-study-review/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-weekly-study-review/hero.png</image:loc>
      <image:title>주간 공부 회고: 공부 시간보다 회상률과 산출물 보기</image:title>
      <image:caption>주간 회고는 공부 시간을 자랑하는 기록이 아니라 무엇을 기억했고 어디서 반복 실패했는지 확인하는 점검 시간이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/household-budget-50-30-20/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-household-budget-50-30-20/hero.png</image:loc>
      <image:title>50/30/20 예산법: 규칙보다 고정비와 현금흐름 먼저 보기</image:title>
      <image:caption>50/30/20 예산법은 출발점으로 유용하지만 소득 주기, 주거비, 부채, 비상금 목표에 맞게 조정해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/weekly-study-review/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-weekly-study-review/hero.png</image:loc>
      <image:title>Weekly Study Review: Track Recall and Output, Not Only Hours</image:title>
      <image:caption>A weekly review should check what you can retrieve and where failure repeats, not only how many hours you studied.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/household-budget-50-30-20/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-household-budget-50-30-20/hero.png</image:loc>
      <image:title>50/30/20 Budget Rule: Start With Fixed Costs and Cash Flow</image:title>
      <image:caption>The 50/30/20 budget rule is a useful starting point, but it must be adjusted for pay timing, housing costs, debt, and emergency savings goals.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/coco-to-yolo-conversion/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-coco-to-yolo-conversion/hero.png</image:loc>
      <image:title>COCO to YOLO 변환 실수: 객체 탐지 라벨이 깨지는 이유</image:title>
      <image:caption>COCO JSON을 YOLO 텍스트 라벨로 바꿀 때는 좌표 원점, 폭과 높이, category ID, 이미지 파일명을 모두 다시 맞춰야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/coco-to-yolo-conversion/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-coco-to-yolo-conversion/hero.png</image:loc>
      <image:title>COCO to YOLO Conversion Mistakes: Avoid Broken Detection Labels</image:title>
      <image:caption>Converting COCO JSON to YOLO text labels requires checking coordinate origin, width and height, category IDs, and image filenames.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/yolo-label-format/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-yolo-label-format/hero.png</image:loc>
      <image:title>YOLO Label Format 읽는 법: class, center x, center y, width, height 이해하기</image:title>
      <image:caption>YOLO 라벨은 한 객체를 class ID와 정규화된 중심 좌표, 너비, 높이로 표현하므로 이미지 크기와 좌표 기준을 함께 이해해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/notion-study-dashboard/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-notion-study-dashboard/hero.png</image:loc>
      <image:title>Notion 공부 대시보드: 예쁜 화면보다 복습과 오답 흐름</image:title>
      <image:caption>공부 대시보드는 꾸미는 화면이 아니라 오늘 할 회상, 밀린 복습, 오답, 주간 성과를 한눈에 보여 주는 운영판이어야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/compound-interest-example/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-compound-interest-example/hero.png</image:loc>
      <image:title>복리 계산 예시: 수익률보다 기간과 추가 납입이 중요한 이유</image:title>
      <image:caption>복리는 이자가 다시 원금이 되는 구조이므로 수익률 하나보다 기간, 추가 납입, 세금, 물가를 함께 봐야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/yolo-label-format/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-yolo-label-format/hero.png</image:loc>
      <image:title>YOLO Label Format: Read Class, Center X, Center Y, Width, and Height</image:title>
      <image:caption>A YOLO label represents one object with a class ID and normalized center coordinates, width, and height, so image size and coordinate rules must be checked together.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/notion-study-dashboard/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-notion-study-dashboard/hero.png</image:loc>
      <image:title>Notion Study Dashboard: Track Review and Mistakes Before Design</image:title>
      <image:caption>A study dashboard should show today’s recall tasks, overdue reviews, mistakes, and weekly output before visual design.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/compound-interest-example/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-compound-interest-example/hero.png</image:loc>
      <image:title>Compound Interest Example: Time and Contributions Matter</image:title>
      <image:caption>Compound interest turns past gains into a larger base, so time, contributions, taxes, and inflation matter alongside return rate.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/etf-vs-mutual-fund/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-etf-vs-mutual-fund/hero.png</image:loc>
      <image:title>ETF와 펀드 차이: 수수료, 거래 방식, 세금을 먼저 비교하기</image:title>
      <image:caption>ETF와 펀드는 모두 분산투자 도구일 수 있지만 거래 시간, 가격 결정, 비용, 세금 처리, 운용 방식이 다르다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/english-vocabulary-system/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-english-vocabulary-system/hero.png</image:loc>
      <image:title>영어 단어 반복 시스템: 뜻 암기보다 문맥과 회상으로 남기기</image:title>
      <image:caption>단어장은 뜻을 많이 적는 곳이 아니라 예문, 직접 만든 문장, 회상 날짜, 틀린 용례를 함께 남기는 학습 시스템이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/etf-vs-mutual-fund/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-etf-vs-mutual-fund/hero.png</image:loc>
      <image:title>ETF vs Mutual Fund: Compare Fees, Trading, and Taxes First</image:title>
      <image:caption>ETFs and mutual funds can both provide diversification, but trading, pricing, fees, taxes, and management style differ.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/english-vocabulary-system/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-english-vocabulary-system/hero.png</image:loc>
      <image:title>English Vocabulary System: Learn Words Through Context and Recall</image:title>
      <image:caption>A vocabulary system should keep examples, self-made sentences, recall dates, and wrong usage, not only translated meanings.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/exchange-rate-basics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-exchange-rate-basics/hero.png</image:loc>
      <image:title>환율 기초: 원화 약세가 여행, 수입물가, 수출에 주는 영향</image:title>
      <image:caption>환율은 여행 경비뿐 아니라 에너지 수입, 식품 가격, 수출 채산성, 외화부채 부담을 동시에 움직인다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/coding-study-roadmap/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-coding-study-roadmap/hero.png</image:loc>
      <image:title>코딩 공부 로드맵: 문법, 프로젝트, 디버깅을 한 루프로 묶기</image:title>
      <image:caption>코딩 공부는 강의 시청 순서가 아니라 작은 문법 연습, 프로젝트, 디버깅 기록, 문서 읽기가 반복되는 루프다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/exchange-rate-basics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-exchange-rate-basics/hero.png</image:loc>
      <image:title>Exchange Rate Basics: Travel, Import Prices, and Exports</image:title>
      <image:caption>Exchange rates affect travel costs, imported energy, food prices, export margins, and foreign-currency debt at the same time.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/coding-study-roadmap/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-coding-study-roadmap/hero.png</image:loc>
      <image:title>Coding Study Roadmap: Connect Syntax, Projects, and Debugging</image:title>
      <image:caption>Learning to code is a loop of syntax practice, small projects, debugging records, and documentation reading, not a playlist order.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_economy/interest-rate-inflation-basics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-interest-rate-inflation-basics/hero.png</image:loc>
      <image:title>금리와 물가 기초: 중앙은행 뉴스를 생활비 언어로 읽기</image:title>
      <image:caption>금리와 물가는 대출 이자, 예금 수익, 환율, 소비 심리로 연결되므로 숫자보다 전달 경로를 먼저 이해해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/exam-mistake-note-system/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-exam-mistake-note-system/hero.png</image:loc>
      <image:title>오답노트 시스템: 틀린 문제를 다시 틀리지 않는 기록법</image:title>
      <image:caption>오답노트는 문제를 예쁘게 베끼는 노트가 아니라 오류 원인, 정답 조건, 다음 복습 질문을 남기는 시스템이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_economy/interest-rate-inflation-basics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-interest-rate-inflation-basics/hero.png</image:loc>
      <image:title>Interest Rates and Inflation: Read Central Bank News in Household Terms</image:title>
      <image:caption>Interest rates and inflation affect loan costs, savings income, exchange rates, and spending decisions, so the transmission path matters more than one headline number.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/exam-mistake-note-system/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-exam-mistake-note-system/hero.png</image:loc>
      <image:title>Exam Mistake Note System: Turn Wrong Answers into Review Tasks</image:title>
      <image:caption>A mistake note is not a copied solution; it records the error cause, correct condition, and next retrieval question.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/pomodoro-deep-work/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-pomodoro-deep-work/hero.png</image:loc>
      <image:title>Pomodoro와 Deep Work: 타이머보다 방해 차단이 먼저다</image:title>
      <image:caption>집중 루틴은 25분 타이머 자체보다 시작 조건, 방해 차단, 쉬는 시간, 완료 기록을 함께 설계할 때 효과가 커진다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/pomodoro-deep-work/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-pomodoro-deep-work/hero.png</image:loc>
      <image:title>Pomodoro and Deep Work: Block Distractions Before Timing</image:title>
      <image:caption>A focus routine works better when start conditions, distraction blocking, breaks, and completion logs are designed together.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/spaced-repetition-schedule/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-spaced-repetition-schedule/hero.png</image:loc>
      <image:title>Spaced Repetition 복습 일정: 몰아보기보다 간격을 설계하기</image:title>
      <image:caption>Spaced repetition은 같은 시간을 한 번에 쓰는 대신 며칠과 몇 주에 나누어 복습해 장기 기억을 목표로 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/spaced-repetition-schedule/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-spaced-repetition-schedule/hero.png</image:loc>
      <image:title>Spaced Repetition Schedule: Design Gaps Instead of Cramming</image:title>
      <image:caption>Spaced repetition spreads review across days and weeks so the same study time is aimed at longer-term retention.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_study/active-recall-study-method/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-active-recall-study-method/hero.png</image:loc>
      <image:title>Active Recall 공부법: 읽은 내용을 덮고 꺼내 쓰는 루틴</image:title>
      <image:caption>Active recall은 다시 읽기보다 기억에서 답을 꺼내는 과정으로, 시험과 실무 적용 모두에서 학습 상태를 더 분명히 보여 준다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_study/active-recall-study-method/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-23-active-recall-study-method/hero.png</image:loc>
      <image:title>Active Recall Study Method: Close the Book and Retrieve</image:title>
      <image:caption>Active recall replaces passive rereading with retrieval, making it clearer whether you can use knowledge in exams or real work.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/global-affairs-reading-system/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-global-affairs-reading-system/hero.svg</image:loc>
      <image:title>세계정세 읽기 시스템: 헤드라인보다 먼저 볼 5개의 축</image:title>
      <image:caption>세계정세를 꾸준히 읽으려면 사건을 외우기보다 성장, 에너지, 무역, 금융, 사회안정이라는 5개 축으로 분류하는 습관이 필요하다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/global-affairs-reading-system/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-global-affairs-reading-system/hero.svg</image:loc>
      <image:title>A Global Affairs Reading System: Five Axes to Check Before the Headline</image:title>
      <image:caption>To read global affairs consistently, classify events across growth, energy, trade, finance, and social stability instead of memorizing headlines.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/household-cost-global-issue-link/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-household-cost-global-issue-link/hero.svg</image:loc>
      <image:title>생활비와 세계정세 연결법: 유가·환율·식품가격을 한 번에 보기</image:title>
      <image:caption>세계정세는 추상적 뉴스가 아니라 유가, 환율, 식품 가격, 전기요금, 보험료를 통해 가계부에 들어온다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/household-cost-global-issue-link/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-household-cost-global-issue-link/hero.svg</image:loc>
      <image:title>Linking Household Costs to Global Affairs: Oil, FX, and Food Prices in One View</image:title>
      <image:caption>Global affairs enter household budgets through oil, exchange rates, food prices, electricity bills, and insurance premiums.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/korea-export-exposure-global-fragmentation/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-korea-export-exposure-global-fragmentation/hero.svg</image:loc>
      <image:title>한국 수출과 세계 분절화: 반도체 호황 뒤에 남는 취약점</image:title>
      <image:caption>MOTIR의 2026년 3월 수출 자료는 반도체 호황의 힘을 보여주지만, 동시에 에너지·물류·보호무역 리스크가 수출 불확실성을 키운다는 점도 드러낸다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/korea-export-exposure-global-fragmentation/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-korea-export-exposure-global-fragmentation/hero.svg</image:loc>
      <image:title>Korea&apos;s Export Exposure to Global Fragmentation: Vulnerabilities Behind the Semiconductor Boom</image:title>
      <image:caption>Korea&apos;s March 2026 export release shows the strength of the semiconductor boom, but also the way energy, logistics, and protectionism raise export uncertainty.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/election-disinformation-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-election-disinformation-risk/hero.svg</image:loc>
      <image:title>선거 허위정보와 AI: 민주주의 리스크를 읽는 실무 기준</image:title>
      <image:caption>AI 생성 콘텐츠가 늘수록 선거 리스크는 가짜뉴스 여부를 넘어 출처 확인, 배포 속도, 플랫폼 대응, 신뢰 회복 비용의 문제로 커진다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/election-disinformation-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-election-disinformation-risk/hero.svg</image:loc>
      <image:title>Election Disinformation and AI: A Practical Standard for Reading Democratic Risk</image:title>
      <image:caption>As AI-generated content spreads, election risk moves beyond fact-checking into source verification, distribution speed, platform response, and trust-repair costs.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/cyber-resilience-critical-infrastructure/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-cyber-resilience-critical-infrastructure/hero.svg</image:loc>
      <image:title>핵심 인프라 사이버 복원력: 해킹 뉴스가 생활 리스크가 되는 이유</image:title>
      <image:caption>CISA는 핵심 인프라를 전력, 통신, 물, 운송처럼 일상 기능을 지탱하는 시스템으로 본다. 사이버 리스크는 곧 서비스 중단 리스크다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/cyber-resilience-critical-infrastructure/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-cyber-resilience-critical-infrastructure/hero.svg</image:loc>
      <image:title>Cyber Resilience for Critical Infrastructure: Why Hacking News Becomes Daily-Life Risk</image:title>
      <image:caption>CISA treats critical infrastructure as the systems that sustain daily functions such as power, communications, water, and transport. Cyber risk is service-continuity risk.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/space-security-satellite-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-space-security-satellite-risk/hero.svg</image:loc>
      <image:title>우주안보와 위성 리스크: 통신·금융·군사 인프라의 공통 약점</image:title>
      <image:caption>NATO의 우주 접근은 위성이 군사뿐 아니라 통신, 위치정보, 금융, 기상, 재난 대응의 핵심 인프라가 되었음을 보여준다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/space-security-satellite-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-space-security-satellite-risk/hero.svg</image:loc>
      <image:title>Space Security and Satellite Risk: The Shared Weakness of Communications, Finance, and Defense</image:title>
      <image:caption>NATO&apos;s approach to space shows satellites have become core infrastructure for communications, positioning, finance, weather, and crisis response.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/arctic-route-geopolitics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-arctic-route-geopolitics/hero.svg</image:loc>
      <image:title>북극항로와 해운 지정학: 짧아진 길이 곧 안전한 길은 아니다</image:title>
      <image:caption>북극항로 논의는 거리 단축만이 아니라 보험, 구조 능력, 군사긴장, 환경규제, 항만 인프라의 합산 문제다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/arctic-route-geopolitics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-arctic-route-geopolitics/hero.svg</image:loc>
      <image:title>Arctic Routes and Maritime Geopolitics: A Shorter Route Is Not Always Safer</image:title>
      <image:caption>Arctic-route debates are not only about distance; they combine insurance, rescue capacity, military tension, environmental rules, and port infrastructure.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/water-security-geopolitics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-water-security-geopolitics/hero.svg</image:loc>
      <image:title>물 안보와 지정학: 식량·전력·도시가 만나는 리스크</image:title>
      <image:caption>물 부족과 홍수는 농산물 가격, 수력발전, 반도체 공정, 도시 인프라를 동시에 건드리는 복합 리스크다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/water-security-geopolitics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-water-security-geopolitics/hero.svg</image:loc>
      <image:title>Water Security and Geopolitics: Where Food, Power, and Cities Meet</image:title>
      <image:caption>Water scarcity and floods can hit food prices, hydropower, semiconductor processes, and urban infrastructure at the same time.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/green-industrial-policy-subsidies/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-green-industrial-policy-subsidies/hero.svg</image:loc>
      <image:title>녹색 산업정책과 보조금 경쟁: 기후와 보호무역의 경계</image:title>
      <image:caption>청정기술 보조금은 배출 감축을 빠르게 만들 수 있지만 무역분쟁, 예산 부담, 공급과잉 논쟁도 동시에 만든다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/green-industrial-policy-subsidies/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-green-industrial-policy-subsidies/hero.svg</image:loc>
      <image:title>Green Industrial Policy and Subsidy Competition: Where Climate Meets Protectionism</image:title>
      <image:caption>Clean-tech subsidies can accelerate decarbonisation, but they also create trade disputes, fiscal costs, and overcapacity debates.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/friend-shoring-supply-chain-cost/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-friend-shoring-supply-chain-cost/hero.svg</image:loc>
      <image:title>프렌드쇼어링의 비용: 안정적 공급망은 공짜가 아니다</image:title>
      <image:caption>공급망을 우방 중심으로 재배치하면 정치 리스크는 줄 수 있지만 중복투자, 단가 상승, 시장 분할이라는 비용이 생긴다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/friend-shoring-supply-chain-cost/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-friend-shoring-supply-chain-cost/hero.svg</image:loc>
      <image:title>The Cost of Friend-Shoring: Resilient Supply Chains Are Not Free</image:title>
      <image:caption>Moving supply chains toward trusted partners can reduce political risk, but it adds duplication, higher unit costs, and market fragmentation.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/migration-policy-labor-market/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-migration-policy-labor-market/hero.svg</image:loc>
      <image:title>이민정책과 노동시장: 인구 감소 시대의 경쟁력 변수</image:title>
      <image:caption>이민정책은 국경관리만의 문제가 아니라 돌봄, 제조, 건설, 교육, 도시주거를 동시에 바꾸는 노동시장 정책이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/migration-policy-labor-market/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-migration-policy-labor-market/hero.svg</image:loc>
      <image:title>Migration Policy and Labor Markets: A Competitiveness Variable in the Ageing Era</image:title>
      <image:caption>Migration policy is not only border control; it changes care work, manufacturing, construction, education, and urban housing at once.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/demographic-aging-fiscal-pressure/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-demographic-aging-fiscal-pressure/hero.svg</image:loc>
      <image:title>인구고령화와 재정압박: 세계가 동시에 늙을 때 생기는 문제</image:title>
      <image:caption>인구 전망은 출산율 문제가 아니라 연금, 의료, 노동공급, 이민정책, 자동화 투자의 장기 재정표다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/demographic-aging-fiscal-pressure/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-demographic-aging-fiscal-pressure/hero.svg</image:loc>
      <image:title>Demographic Ageing and Fiscal Pressure: What Happens When the World Ages Together</image:title>
      <image:caption>Population projections are not only about fertility; they are a long fiscal map for pensions, healthcare, labor supply, migration, and automation.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/stablecoins-monetary-sovereignty/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-stablecoins-monetary-sovereignty/hero.svg</image:loc>
      <image:title>스테이블코인과 통화주권: 결제 혁신 뒤에 있는 정책 질문</image:title>
      <image:caption>BIS의 차세대 통화시스템 논의는 토큰화와 스테이블코인을 기술 이슈가 아니라 중앙은행 돈, 은행예금, 국채시장 설계의 문제로 본다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/stablecoins-monetary-sovereignty/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-stablecoins-monetary-sovereignty/hero.svg</image:loc>
      <image:title>Stablecoins and Monetary Sovereignty: The Policy Questions Behind Payment Innovation</image:title>
      <image:caption>The BIS discussion of next-generation money treats tokenisation and stablecoins as questions about central bank money, bank deposits, and government bond markets.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/dollar-funding-financial-stability/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-dollar-funding-financial-stability/hero.svg</image:loc>
      <image:title>달러 유동성과 금융안정: 세계정세가 환율로 번역되는 방식</image:title>
      <image:caption>BIS는 무역 긴장, 비은행 금융, 통화시스템 변화가 금융시장 연결성을 키운다고 본다. 달러 조달비용은 그 연결성의 가장 빠른 신호다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/dollar-funding-financial-stability/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-dollar-funding-financial-stability/hero.svg</image:loc>
      <image:title>Dollar Funding and Financial Stability: How Geopolitics Gets Translated Into FX</image:title>
      <image:caption>The BIS highlights trade tensions, non-bank finance, and monetary-system change. Dollar funding costs are one of the fastest signals of that connectivity.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/sovereign-debt-stress/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-sovereign-debt-stress/hero.svg</image:loc>
      <image:title>국가부채 스트레스: 고금리 이후 개발도상국이 맞는 두 번째 충격</image:title>
      <image:caption>World Bank와 IMF 자료는 부채 문제가 단순한 재정 지표가 아니라 개발투자, 통화가치, 식량·에너지 보조금 여력을 결정한다고 말한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/sovereign-debt-stress/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-sovereign-debt-stress/hero.svg</image:loc>
      <image:title>Sovereign Debt Stress: The Second Shock After High Interest Rates</image:title>
      <image:caption>World Bank and IMF updates show sovereign debt is not just a fiscal ratio; it shapes development investment, currencies, and food and energy support.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/emissions-gap-policy-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-emissions-gap-policy-risk/hero.svg</image:loc>
      <image:title>배출격차 보고서 읽기: 기후정책은 왜 산업정책이 되었나</image:title>
      <image:caption>UNEP Emissions Gap Report는 현재 정책과 목표 사이의 간극이 탄소가격, 보조금, 무역장벽, 기술투자 논쟁으로 번지고 있음을 보여준다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/emissions-gap-policy-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-emissions-gap-policy-risk/hero.svg</image:loc>
      <image:title>Reading the Emissions Gap: Why Climate Policy Has Become Industrial Policy</image:title>
      <image:caption>UNEP&apos;s Emissions Gap Report shows how the gap between current policy and targets is becoming a fight over carbon prices, subsidies, trade rules, and technology investment.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/climate-risk-insurance-gap/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-climate-risk-insurance-gap/hero.svg</image:loc>
      <image:title>기후 리스크와 보험 공백: 재난은 왜 금융문제가 되는가</image:title>
      <image:caption>WMO와 UNEP 자료를 함께 보면 기후 리스크는 자연재해 통계가 아니라 보험료, 부동산, 지방재정, 기업공시의 문제로 이동하고 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/climate-risk-insurance-gap/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-climate-risk-insurance-gap/hero.svg</image:loc>
      <image:title>Climate Risk and the Insurance Gap: Why Disasters Become Financial Problems</image:title>
      <image:caption>Read WMO and UNEP together and climate risk shifts from weather statistics to insurance, property, local budgets, and corporate disclosure.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/forced-displacement-migration-pressure/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-forced-displacement-migration-pressure/hero.svg</image:loc>
      <image:title>강제이주와 난민 압력: 숫자 뒤의 노동·주거·정치 리스크</image:title>
      <image:caption>UNHCR 수치는 전쟁과 폭력이 이동을 만들고, 이동은 다시 노동시장, 주택, 교육, 정치 갈등으로 번진다는 사실을 보여준다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/forced-displacement-migration-pressure/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-forced-displacement-migration-pressure/hero.svg</image:loc>
      <image:title>Forced Displacement and Migration Pressure: Labor, Housing, and Political Risk Behind the Numbers</image:title>
      <image:caption>UNHCR data show how conflict and violence create displacement, which then reshapes labor markets, housing, education, and politics.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/food-security-price-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-food-security-price-risk/hero.svg</image:loc>
      <image:title>식량안보와 식품물가: 기후보다 먼저 지갑에 도착하는 세계정세</image:title>
      <image:caption>FAO SOFI 2025는 식품 가격 인플레이션이 저소득층의 건강한 식단 접근과 아동 영양에 직접 영향을 준다고 설명한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/food-security-price-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-food-security-price-risk/hero.svg</image:loc>
      <image:title>Food Security and Food Prices: The Global Issue That Reaches Wallets First</image:title>
      <image:caption>FAO&apos;s SOFI 2025 explains how food price inflation directly weakens low-income access to healthy diets and affects child nutrition.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/ukraine-reconstruction-finance/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-ukraine-reconstruction-finance/hero.svg</image:loc>
      <image:title>우크라이나 재건금융: 전쟁 이후 시장을 읽는 현실적 기준</image:title>
      <image:caption>우크라이나 재건은 원조 뉴스가 아니라 에너지, 주택, 물류, 민간자본, 제도개혁이 맞물린 장기 프로젝트다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/ukraine-reconstruction-finance/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-ukraine-reconstruction-finance/hero.svg</image:loc>
      <image:title>Ukraine Reconstruction Finance: A Realistic Framework for the Postwar Market</image:title>
      <image:caption>Ukraine reconstruction is not just aid news; it is a long project across energy, housing, logistics, private capital, and institutional reform.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/defense-spending-surge/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-defense-spending-surge/hero.svg</image:loc>
      <image:title>방위비 급증의 경제학: 안보 지출은 성장과 재정에 무엇을 남기나</image:title>
      <image:caption>SIPRI와 IMF 자료는 방위비 증가가 단기 수요를 만들 수 있지만 재정, 물가, 사회지출의 선택 문제를 남긴다는 점을 보여준다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/defense-spending-surge/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-defense-spending-surge/hero.svg</image:loc>
      <image:title>The Economics of Rising Defense Spending: Growth, Inflation, and Fiscal Trade-offs</image:title>
      <image:caption>SIPRI and IMF data show defense buildups can support short-term demand while leaving harder trade-offs for budgets, inflation, and social spending.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/nuclear-energy-comeback/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-nuclear-energy-comeback/hero.svg</image:loc>
      <image:title>원전 재부상: 에너지 안보와 전력 수요가 만든 현실적 선택지</image:title>
      <image:caption>원전은 기후정책만의 이슈가 아니라 전력망 안정성, 산업용 전력, 에너지 수입 의존도를 동시에 낮추려는 전략의 일부로 돌아오고 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/nuclear-energy-comeback/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-nuclear-energy-comeback/hero.svg</image:loc>
      <image:title>The Nuclear Energy Comeback: A Realist Response to Security and Power Demand</image:title>
      <image:caption>Nuclear power is returning not only as climate policy but as a strategy for grid stability, industrial electricity, and lower import dependence.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/energy-transition-grid-bottlenecks/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-energy-transition-grid-bottlenecks/hero.svg</image:loc>
      <image:title>에너지 전환의 병목은 발전량보다 전력망이다</image:title>
      <image:caption>재생에너지와 전기화가 늘수록 핵심 질문은 전기를 얼마나 만들 수 있느냐에서 어디로, 언제, 얼마나 안정적으로 보낼 수 있느냐로 이동한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/energy-transition-grid-bottlenecks/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-energy-transition-grid-bottlenecks/hero.svg</image:loc>
      <image:title>The Energy Transition Bottleneck Is the Grid, Not Only Generation</image:title>
      <image:caption>As renewables and electrification expand, the main question shifts from how much electricity can be generated to where and when it can be delivered reliably.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/ai-data-center-electricity-demand/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-ai-data-center-electricity-demand/hero.svg</image:loc>
      <image:title>AI 데이터센터 전력 수요: 기술주 뉴스가 전력망 뉴스가 되는 이유</image:title>
      <image:caption>IEA Electricity 2026은 전력 수요가 데이터센터, 산업, 냉방, 전기차를 통해 경제성장보다 빠르게 움직일 수 있음을 보여준다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/ai-data-center-electricity-demand/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-ai-data-center-electricity-demand/hero.svg</image:loc>
      <image:title>AI Data-Center Electricity Demand: Why Tech News Is Becoming Grid News</image:title>
      <image:caption>IEA Electricity 2026 shows electricity demand can outpace economic growth as data centres, industry, cooling, and EVs reshape the load profile.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/semiconductor-export-controls/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-semiconductor-export-controls/hero.svg</image:loc>
      <image:title>반도체 수출통제와 AI 하드웨어 경쟁의 다음 국면</image:title>
      <image:caption>AI 하드웨어 경쟁은 첨단 칩뿐 아니라 장비, 소재, 희소금속, 전력 인프라가 하나의 패키지로 움직이는 경쟁이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/semiconductor-export-controls/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-semiconductor-export-controls/hero.svg</image:loc>
      <image:title>Semiconductor Export Controls and the Next Phase of AI Hardware Competition</image:title>
      <image:caption>AI hardware competition is a bundled contest across advanced chips, tools, materials, rare minerals, and electricity infrastructure.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/critical-minerals-supply-chain/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-critical-minerals-supply-chain/hero.svg</image:loc>
      <image:title>핵심광물 공급망: 배터리와 AI 시대의 새로운 에너지 안보</image:title>
      <image:caption>IEA는 핵심광물 문제가 전기차와 재생에너지를 넘어 AI 칩, 방산, 항공우주까지 연결되는 전략 리스크라고 본다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/critical-minerals-supply-chain/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-critical-minerals-supply-chain/hero.svg</image:loc>
      <image:title>Critical Minerals Supply Chains: The New Energy Security Layer for Batteries and AI</image:title>
      <image:caption>The IEA frames critical minerals as a strategic risk that reaches beyond EVs and renewables into AI chips, defense, aerospace, and advanced manufacturing.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/red-sea-shipping-chokepoints/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-red-sea-shipping-chokepoints/hero.svg</image:loc>
      <image:title>홍해와 해상 병목: 해운 리스크가 소비자 가격으로 번지는 과정</image:title>
      <image:caption>해상 운송은 세계 상품무역의 기본 인프라이며, 특정 해협의 병목은 운송거리, 보험료, 납기, 재고비용을 동시에 올린다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/red-sea-shipping-chokepoints/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-red-sea-shipping-chokepoints/hero.svg</image:loc>
      <image:title>Red Sea and Maritime Chokepoints: How Shipping Risk Reaches Consumer Prices</image:title>
      <image:caption>Maritime transport is the base layer of goods trade, and chokepoint stress can raise sailing distance, insurance costs, delivery times, and inventory costs together.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/middle-east-energy-shock-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-middle-east-energy-shock-risk/hero.svg</image:loc>
      <image:title>중동 에너지 충격이 세계경제를 흔드는 경로</image:title>
      <image:caption>중동 충돌은 유가만의 문제가 아니라 물가 기대, 운송비, 비료 가격, 금융시장 변동성을 동시에 건드리는 복합 충격이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/middle-east-energy-shock-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-middle-east-energy-shock-risk/hero.svg</image:loc>
      <image:title>How a Middle East Energy Shock Moves Through the World Economy</image:title>
      <image:caption>A Middle East energy shock is not only about oil; it can move inflation expectations, shipping costs, fertilizer prices, and financial volatility at the same time.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/trade-fragmentation-tariff-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-trade-fragmentation-tariff-risk/hero.svg</image:loc>
      <image:title>관세와 무역 분절화 리스크: 공급망 뉴스 읽는 순서</image:title>
      <image:caption>WTO와 OECD 전망은 무역량 자체보다 정책 불확실성이 기업의 재고, 투자, 가격 결정에 누적되는 과정을 봐야 한다는 점을 보여준다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/trade-fragmentation-tariff-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-trade-fragmentation-tariff-risk/hero.svg</image:loc>
      <image:title>Tariffs and Trade Fragmentation: A Practical Reading Order for Supply-Chain News</image:title>
      <image:caption>WTO and OECD updates show that the real issue is how policy uncertainty accumulates inside inventories, investment decisions, and pricing power.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_global_affairs/global-growth-fragmentation-2026/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-global-growth-fragmentation-2026/hero.svg</image:loc>
      <image:title>2026년 세계 성장 둔화와 분절화: 숫자보다 중요한 해석법</image:title>
      <image:caption>IMF와 World Bank 전망을 함께 놓고 보면 2026년 세계경제의 핵심은 경기침체 여부보다 낮은 성장, 높은 불확실성, 정책 신뢰의 동시 관리다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_global_affairs/global-growth-fragmentation-2026/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-22-global-growth-fragmentation-2026/hero.svg</image:loc>
      <image:title>Global Growth and Fragmentation in 2026: How to Read the New Baseline</image:title>
      <image:caption>Read IMF and World Bank projections together and the central issue is not a single recession call, but the combined pressure of slower growth, uncertainty, and policy credibility.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/security-checkup-monthly-routine/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-security-checkup-monthly-routine/hero.svg</image:loc>
      <image:title>월간 보안 점검 루틴: 30분으로 계정과 기기를 정리하는 법</image:title>
      <image:caption>보안은 큰 결심보다 반복 가능한 월간 루틴이 강하다. 계정, 기기, 백업, 결제 알림을 30분 안에 점검하는 방식이면 충분하다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/security-checkup-monthly-routine/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-security-checkup-monthly-routine/hero.svg</image:loc>
      <image:title>Monthly Security Checkup: A 30-Minute Routine for Accounts and Devices</image:title>
      <image:caption>Security improves through repeatable monthly routines. A 30-minute review of accounts, devices, backups, and payment alerts is enough to reduce many risks.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/domain-email-spoofing-dmarc/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-domain-email-spoofing-dmarc/hero.svg</image:loc>
      <image:title>도메인 이메일 사칭 막기: SPF, DKIM, DMARC를 실무적으로 이해하기</image:title>
      <image:caption>SPF, DKIM, DMARC는 이메일을 완벽히 안전하게 만들지는 않지만 내 도메인을 사칭한 메일을 줄이고 탐지하는 기본 장치다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/domain-email-spoofing-dmarc/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-domain-email-spoofing-dmarc/hero.svg</image:loc>
      <image:title>Stopping Domain Email Spoofing: A Practical View of SPF, DKIM, and DMARC</image:title>
      <image:caption>SPF, DKIM, and DMARC do not make email perfect, but they reduce and detect mail that spoofs your domain.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/invoice-payment-fraud/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-invoice-payment-fraud/hero.svg</image:loc>
      <image:title>송금 계좌 변경 사기: 거래처 메일을 믿기 전 확인할 절차</image:title>
      <image:caption>거래처 계좌 변경 사기는 이메일 한 통으로 자금을 빼내므로 결제 전 별도 연락, 이중승인, 변경 이력 기록이 필요하다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/invoice-payment-fraud/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-invoice-payment-fraud/hero.svg</image:loc>
      <image:title>Invoice Payment Fraud: Verify Vendor Bank Changes Before Trusting Email</image:title>
      <image:caption>Vendor bank-change fraud can move money with one email, so separate verification, dual approval, and change records are essential.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/employee-phishing-drill/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-employee-phishing-drill/hero.svg</image:loc>
      <image:title>직원 피싱 훈련 설계: 속인 사람 찾기가 아니라 신고 루틴 만들기</image:title>
      <image:caption>피싱 훈련의 목적은 누가 속았는지 공개하는 것이 아니라 의심 메일을 빠르게 신고하고 같은 피해를 줄이는 조직 루틴을 만드는 것이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/employee-phishing-drill/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-employee-phishing-drill/hero.svg</image:loc>
      <image:title>Employee Phishing Drills: Build Reporting Habits, Not Blame</image:title>
      <image:caption>The goal of phishing drills is not public blame. It is a fast reporting habit that reduces repeat harm across the organization.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/small-business-cyber-baseline/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-small-business-cyber-baseline/hero.svg</image:loc>
      <image:title>소상공인 보안 기준선: 돈을 많이 쓰기 전 먼저 할 10가지</image:title>
      <image:caption>소상공인 보안은 비싼 솔루션보다 이메일 MFA, 백업, 업데이트, 결제 권한 분리, 직원 피싱 교육 같은 기본선이 먼저다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/small-business-cyber-baseline/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-small-business-cyber-baseline/hero.svg</image:loc>
      <image:title>Small Business Cyber Baseline: Ten Things to Do Before Buying More Tools</image:title>
      <image:caption>Small business security starts with email MFA, backups, updates, payment separation, and phishing training before expensive tools.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/elderly-scam-prevention/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-elderly-scam-prevention/hero.svg</image:loc>
      <image:title>부모님 디지털 사기 예방: 대신 설정보다 함께 확인하는 루틴</image:title>
      <image:caption>부모님 보안은 자녀가 대신 설정하는 것보다 낯선 전화, 문자, 앱 설치, 송금 요청을 함께 확인하는 약속이 더 오래간다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/elderly-scam-prevention/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-elderly-scam-prevention/hero.svg</image:loc>
      <image:title>Digital Scam Prevention for Older Adults: Build a Shared Check Routine</image:title>
      <image:caption>Security for older adults lasts longer when families build a shared check routine for calls, texts, app installs, and transfer requests.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/child-online-safety-family-device/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-child-online-safety-family-device/hero.svg</image:loc>
      <image:title>아이 온라인 안전 설정: 차단보다 대화와 기기 규칙이 먼저다</image:title>
      <image:caption>아이 기기 보안은 차단앱 하나로 끝나지 않는다. 결제, 위치, 사진 공유, 낯선 대화, 계정 복구를 가족 규칙으로 정해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/child-online-safety-family-device/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-child-online-safety-family-device/hero.svg</image:loc>
      <image:title>Child Online Safety Settings: Rules and Conversation Before Blocking</image:title>
      <image:caption>Children&apos;s device safety is not solved by one blocking app. Payments, location, photo sharing, stranger chats, and account recovery need family rules.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/smart-home-iot-security/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-smart-home-iot-security/hero.svg</image:loc>
      <image:title>스마트홈 IoT 보안: 카메라와 가전을 별도 네트워크에 두는 이유</image:title>
      <image:caption>IoT 기기는 편리하지만 업데이트 수명, 기본 비밀번호, 클라우드 계정 보안이 약하면 집 안 네트워크의 약한 고리가 된다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/smart-home-iot-security/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-smart-home-iot-security/hero.svg</image:loc>
      <image:title>Smart Home IoT Security: Why Cameras and Appliances Need Separation</image:title>
      <image:caption>IoT devices are convenient, but weak update lifecycles, default passwords, and cloud-account security can make them the weakest link at home.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/home-router-security/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-home-router-security/hero.svg</image:loc>
      <image:title>가정용 공유기 보안: 와이파이 이름보다 관리자 페이지가 먼저다</image:title>
      <image:caption>가정용 공유기는 집 안 모든 기기의 관문이므로 관리자 비밀번호, 펌웨어, 원격관리, 게스트 네트워크를 우선 점검해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/home-router-security/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-home-router-security/hero.svg</image:loc>
      <image:title>Home Router Security: Admin Settings Matter More Than the Wi-Fi Name</image:title>
      <image:caption>A home router is the gateway for every device, so admin passwords, firmware, remote management, and guest networks come first.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/cloud-drive-sharing-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-cloud-drive-sharing-risk/hero.svg</image:loc>
      <image:title>클라우드 드라이브 공유 보안: 링크 하나가 전체 폴더가 되지 않게 하기</image:title>
      <image:caption>클라우드 공유는 편리하지만 링크 공개 범위, 편집 권한, 만료일, 외부 공유 알림을 관리하지 않으면 자료 유출로 이어진다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/cloud-drive-sharing-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-cloud-drive-sharing-risk/hero.svg</image:loc>
      <image:title>Cloud Drive Sharing Security: Keep One Link From Becoming the Whole Folder</image:title>
      <image:caption>Cloud sharing is useful, but unmanaged link visibility, edit rights, expiry dates, and external sharing alerts can create data exposure.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/qr-code-quishing/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-qr-code-quishing/hero.svg</image:loc>
      <image:title>QR코드 피싱 대응: 스캔하기 전 주소와 맥락 확인하기</image:title>
      <image:caption>QR코드는 편리하지만 사용자가 주소를 보지 않고 스캔하기 쉬워 가짜 결제, 가짜 주차요금, 가짜 로그인 페이지로 이어질 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/qr-code-quishing/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-qr-code-quishing/hero.svg</image:loc>
      <image:title>QR Code Phishing: Check the Destination and Context Before Scanning</image:title>
      <image:caption>QR codes are convenient, but they make it easy to skip URL checking, leading to fake payments, fake parking fees, or fake login pages.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/marketplace-secondhand-scam/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-marketplace-secondhand-scam/hero.svg</image:loc>
      <image:title>중고거래 사기 예방: 안전결제와 직거래보다 중요한 기록 남기기</image:title>
      <image:caption>중고거래에서는 빠른 거래보다 대화 기록, 결제 경로, 판매자 평판, 물품 확인 절차를 남기는 것이 사후 대응력을 높인다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/marketplace-secondhand-scam/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-marketplace-secondhand-scam/hero.svg</image:loc>
      <image:title>Secondhand Marketplace Scam Prevention: Records Matter More Than Speed</image:title>
      <image:caption>In secondhand marketplaces, keeping chat records, payment trails, seller reputation, and item-verification steps improves your response options.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/shopping-scam-red-flags/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-shopping-scam-red-flags/hero.svg</image:loc>
      <image:title>온라인 쇼핑 사기 신호: 최저가보다 먼저 볼 7가지</image:title>
      <image:caption>온라인 쇼핑 사기는 가격보다 결제 방식, 사업자 정보, 환불 정책, 후기 패턴, 도메인 이력이 먼저 말해준다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/shopping-scam-red-flags/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-shopping-scam-red-flags/hero.svg</image:loc>
      <image:title>Online Shopping Scam Red Flags: Seven Checks Before the Lowest Price</image:title>
      <image:caption>Shopping scams show up in payment method, seller identity, refund policy, review patterns, and domain behavior before price alone tells the story.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/privacy-settings-social-media/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-privacy-settings-social-media/hero.svg</image:loc>
      <image:title>SNS 개인정보 설정: 공개 범위를 줄이면 사기도 줄어든다</image:title>
      <image:caption>SNS 공개 정보는 단순한 사생활 문제가 아니라 가족 사칭, 생일 기반 인증 추측, 위치 추적, 맞춤형 피싱의 재료가 된다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/privacy-settings-social-media/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-privacy-settings-social-media/hero.svg</image:loc>
      <image:title>Social Media Privacy Settings: Less Exposure Means Fewer Scam Angles</image:title>
      <image:caption>Public social media details are not just privacy trivia; they fuel impersonation, birthday-based guessing, location tracking, and tailored phishing.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/data-breach-password-rotation/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-data-breach-password-rotation/hero.svg</image:loc>
      <image:title>개인정보 유출 후 비밀번호 변경 순서: 모든 계정을 한 번에 바꾸지 말 것</image:title>
      <image:caption>유출 소식을 들으면 모든 계정을 무작정 바꾸기보다 이메일, 금융, 같은 비밀번호를 쓴 계정부터 우선순위를 정해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/data-breach-password-rotation/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-data-breach-password-rotation/hero.svg</image:loc>
      <image:title>Password Rotation After a Breach: Do Not Change Every Account at Random</image:title>
      <image:caption>After a breach notice, prioritize email, financial accounts, and reused-password accounts instead of randomly changing everything.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/identity-theft-response/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-identity-theft-response/hero.svg</image:loc>
      <image:title>개인정보 도용 대응 순서: 유출을 알게 된 날 해야 할 일</image:title>
      <image:caption>개인정보 도용은 한 번의 신고로 끝나지 않는다. 계정 잠금, 비밀번호 변경, 결제수단 점검, 공식 신고 기록을 동시에 남겨야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/identity-theft-response/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-identity-theft-response/hero.svg</image:loc>
      <image:title>Identity Theft Response Order: What to Do the Day You Learn About Exposure</image:title>
      <image:caption>Identity theft response is not one report. It requires account locks, password changes, payment review, and official records at the same time.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/ransomware-first-hour/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-ransomware-first-hour/hero.svg</image:loc>
      <image:title>랜섬웨어 의심 첫 1시간: 전원, 네트워크, 신고 순서</image:title>
      <image:caption>랜섬웨어가 의심될 때는 당황해서 파일을 지우기보다 네트워크 분리, 증거 보존, 내부 연락, 신고 채널 확인 순서가 중요하다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/ransomware-first-hour/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-ransomware-first-hour/hero.svg</image:loc>
      <image:title>The First Hour of Suspected Ransomware: Power, Network, and Reporting Order</image:title>
      <image:caption>When ransomware is suspected, the first priority is network isolation, evidence preservation, internal escalation, and reporting paths, not random cleanup.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/backup-3-2-1-ransomware/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-backup-3-2-1-ransomware/hero.svg</image:loc>
      <image:title>랜섬웨어 대비 3-2-1 백업: 복구 가능한 백업인지 확인하는 법</image:title>
      <image:caption>백업은 파일을 복사했다는 사실보다 랜섬웨어 이후 실제로 복구할 수 있는지, 오프라인·불변 백업이 있는지가 핵심이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/backup-3-2-1-ransomware/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-backup-3-2-1-ransomware/hero.svg</image:loc>
      <image:title>3-2-1 Backup for Ransomware: How to Know Whether You Can Really Recover</image:title>
      <image:caption>Backup quality is about recoverability after ransomware, not just copied files. Offline or immutable copies matter.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/software-update-routine/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-software-update-routine/hero.svg</image:loc>
      <image:title>보안 업데이트 루틴: 미루지 않아도 되는 현실적인 패치 습관</image:title>
      <image:caption>업데이트는 귀찮은 팝업이 아니라 이미 알려진 취약점을 닫는 가장 비용 효율적인 보안 행동이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/software-update-routine/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-software-update-routine/hero.svg</image:loc>
      <image:title>Software Update Routine: A Realistic Patch Habit You Can Keep</image:title>
      <image:caption>Updates are not just annoying prompts; they are one of the lowest-cost ways to close known vulnerabilities.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/browser-extension-security/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-browser-extension-security/hero.svg</image:loc>
      <image:title>브라우저 확장 프로그램 보안: 편리함이 계정 탈취로 바뀌는 지점</image:title>
      <image:caption>브라우저 확장 프로그램은 웹페이지와 로그인 상태에 접근할 수 있으므로 설치 수보다 권한, 개발자 신뢰, 업데이트 이력을 봐야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/browser-extension-security/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-browser-extension-security/hero.svg</image:loc>
      <image:title>Browser Extension Security: Where Convenience Turns Into Account Risk</image:title>
      <image:caption>Browser extensions can access pages and sessions, so permissions, developer trust, and update history matter more than install count alone.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/public-wifi-vpn-real-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-public-wifi-vpn-real-risk/hero.svg</image:loc>
      <image:title>공용 와이파이와 VPN: 실제로 위험한 순간과 안전한 사용법</image:title>
      <image:caption>공용 와이파이는 무조건 금지보다 네트워크 이름 확인, HTTPS, 자동연결 해제, 민감 작업 회피가 현실적인 방어선이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/public-wifi-vpn-real-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-public-wifi-vpn-real-risk/hero.svg</image:loc>
      <image:title>Public Wi-Fi and VPNs: The Real Risk Moments and Safer Use</image:title>
      <image:caption>Public Wi-Fi is best handled with network-name verification, HTTPS, disabled auto-join, and avoiding sensitive tasks rather than vague fear.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/smartphone-security-checklist/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-smartphone-security-checklist/hero.svg</image:loc>
      <image:title>스마트폰 보안 체크리스트: 앱 권한과 잠금화면부터 점검하기</image:title>
      <image:caption>스마트폰은 인증기기, 결제수단, 사진 저장소, 업무 알림창이므로 앱 권한과 잠금화면이 곧 계정 보안의 출발점이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/smartphone-security-checklist/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-smartphone-security-checklist/hero.svg</image:loc>
      <image:title>Smartphone Security Checklist: Start With App Permissions and Lock Screen</image:title>
      <image:caption>A phone is an authenticator, wallet, photo archive, and work notification center, so permissions and lock screen settings are account security basics.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/email-account-security-baseline/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-email-account-security-baseline/hero.svg</image:loc>
      <image:title>이메일 계정 보안 기준선: 모든 계정의 열쇠를 먼저 지키기</image:title>
      <image:caption>이메일은 비밀번호 재설정과 알림을 받는 중심 계정이므로 다른 계정보다 먼저 긴 비밀번호, MFA, 복구 경로 점검이 필요하다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/email-account-security-baseline/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-email-account-security-baseline/hero.svg</image:loc>
      <image:title>Email Account Security Baseline: Protecting the Key to Every Account</image:title>
      <image:caption>Email receives resets and alerts, so it needs long unique passwords, MFA, and recovery checks before most other accounts.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/account-recovery-lockout-plan/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-account-recovery-lockout-plan/hero.svg</image:loc>
      <image:title>계정 복구 계획: 휴대폰을 잃어버려도 잠기지 않는 구조 만들기</image:title>
      <image:caption>강한 인증은 복구 계획과 함께 설계해야 한다. 휴대폰 분실, 번호 변경, 해외 체류 같은 상황을 미리 가정해야 잠금을 피할 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/account-recovery-lockout-plan/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-account-recovery-lockout-plan/hero.svg</image:loc>
      <image:title>Account Recovery Plan: Avoiding Lockout After Losing a Phone</image:title>
      <image:caption>Strong authentication needs recovery design. Plan for lost phones, number changes, and travel before they become account lockout events.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/mfa-authenticator-vs-sms/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-mfa-authenticator-vs-sms/hero.svg</image:loc>
      <image:title>인증앱과 SMS 2단계 인증 비교: 어떤 계정부터 바꿀까</image:title>
      <image:caption>2단계 인증은 켜는 것만큼 방식 선택이 중요하다. 중요한 계정은 SMS보다 인증앱, 패스키, 보안키처럼 피싱 저항성이 높은 방식으로 옮겨야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/mfa-authenticator-vs-sms/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-mfa-authenticator-vs-sms/hero.svg</image:loc>
      <image:title>Authenticator Apps vs SMS MFA: Which Accounts to Upgrade First</image:title>
      <image:caption>Turning on MFA matters, but method choice matters too. Critical accounts should move from SMS toward authenticator apps, passkeys, or security keys.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/passkeys-vs-passwords/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-passkeys-vs-passwords/hero.svg</image:loc>
      <image:title>패스키와 비밀번호 차이: 피싱에 강한 로그인으로 바꾸는 법</image:title>
      <image:caption>패스키는 사용자가 비밀번호를 기억하지 않고도 기기 기반 인증으로 로그인하는 방식이며, 피싱 사이트에 비밀번호를 입력하는 위험을 줄인다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/passkeys-vs-passwords/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-passkeys-vs-passwords/hero.svg</image:loc>
      <image:title>Passkeys vs Passwords: Moving Toward Phishing-Resistant Sign-In</image:title>
      <image:caption>Passkeys let users sign in with device-based authentication instead of memorized passwords, reducing the risk of typing secrets into phishing sites.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/password-manager-first-setup/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-password-manager-first-setup/hero.svg</image:loc>
      <image:title>비밀번호 관리자 처음 설정하기: 실패하지 않는 도입 순서</image:title>
      <image:caption>비밀번호 관리자는 모든 계정을 한 번에 바꾸는 도구가 아니라 중요한 계정부터 긴 고유 비밀번호로 전환하는 운영 방식이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/password-manager-first-setup/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-password-manager-first-setup/hero.svg</image:loc>
      <image:title>Password Manager First Setup: A Practical Adoption Order That Sticks</image:title>
      <image:caption>A password manager is not a one-day reset project; it is an operating habit for moving critical accounts to long, unique passwords first.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/voice-phishing-family-code/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-voice-phishing-family-code/hero.svg</image:loc>
      <image:title>보이스피싱 가족 암호 만들기: 급한 전화에서 먼저 확인할 한 문장</image:title>
      <image:caption>가족 사칭 전화는 감정적으로 빠르게 몰아붙이므로 가족끼리 미리 정한 확인 질문과 송금 보류 규칙이 필요하다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/voice-phishing-family-code/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-voice-phishing-family-code/hero.svg</image:loc>
      <image:title>Family Code Words for Voice Phishing: One Sentence to Verify Urgent Calls</image:title>
      <image:caption>Impersonation calls move fast emotionally, so families need a pre-agreed verification question and a no-transfer pause rule.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/smishing-parcel-scam/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-smishing-parcel-scam/hero.svg</image:loc>
      <image:title>택배 스미싱 대응법: 운송장 링크가 왔을 때 안전하게 확인하는 순서</image:title>
      <image:caption>택배 스미싱은 일상적인 기다림을 악용하므로 문자 속 링크가 아니라 택배사 공식 앱, 주문 내역, 고객센터 경로로 확인해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/smishing-parcel-scam/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-smishing-parcel-scam/hero.svg</image:loc>
      <image:title>Parcel Smishing Response: A Safe Order for Checking Delivery Links</image:title>
      <image:caption>Parcel smishing abuses everyday delivery anxiety, so delivery status should be checked through official apps, order history, or customer support routes.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_digital_security/phishing-message-triage/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-phishing-message-triage/hero.svg</image:loc>
      <image:title>피싱 문자와 이메일 30초 판별법: 링크를 누르기 전 확인할 것</image:title>
      <image:caption>피싱은 완벽한 보안 지식보다 멈춤, 발신자 확인, 별도 경로 접속이라는 짧은 루틴이 있을 때 피해 확률이 크게 줄어든다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_digital_security/phishing-message-triage/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-21-phishing-message-triage/hero.svg</image:loc>
      <image:title>A 30-Second Phishing Triage: What to Check Before You Click</image:title>
      <image:caption>Phishing risk drops when users have a short routine: pause, verify the sender, and open the service through a trusted route instead of the message link.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/monthly-money-dashboard/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-monthly-money-dashboard/hero.svg</image:loc>
      <image:title>월간 돈 대시보드: 순자산, 현금흐름, 부채, 목표를 한 장에 보기</image:title>
      <image:caption>재무관리는 완벽한 앱보다 매달 같은 기준으로 순자산, 현금흐름, 부채, 목표 진행률을 보는 대시보드가 더 중요하다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/monthly-money-dashboard/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-monthly-money-dashboard/hero.svg</image:loc>
      <image:title>Monthly Money Dashboard: Net Worth, Cash Flow, Debt, and Goals on One Page</image:title>
      <image:caption>Personal finance improves less from a perfect app and more from a monthly dashboard for net worth, cash flow, debt, and goal progress.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/parents-support-boundaries/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-parents-support-boundaries/hero.svg</image:loc>
      <image:title>부모님 지원과 내 재무 경계: 효도와 파산을 구분하는 기준</image:title>
      <image:caption>부모님 지원은 감정만으로 결정하면 장기 재무가 무너질 수 있다. 정기 지원, 긴급 지원, 대출 보증, 의료비를 구분해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/parents-support-boundaries/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-parents-support-boundaries/hero.svg</image:loc>
      <image:title>Supporting Parents Without Breaking Your Own Financial Plan</image:title>
      <image:caption>Supporting parents can damage long-term finances if decided only emotionally. Separate regular support, emergencies, guarantees, and medical costs.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/couple-money-meeting/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-couple-money-meeting/hero.svg</image:loc>
      <image:title>부부·커플 돈 회의: 싸우지 않기 위한 월 30분 의제</image:title>
      <image:caption>커플의 돈 문제는 금액보다 기대와 역할이 달라 생긴다. 월 30분 회의로 고정비, 목표, 비상금, 개인 지출을 나누어야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/couple-money-meeting/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-couple-money-meeting/hero.svg</image:loc>
      <image:title>Couple Money Meeting: A 30-Minute Monthly Agenda That Reduces Fights</image:title>
      <image:caption>Money conflict often comes from mismatched expectations and roles, not only amounts. A monthly meeting separates bills, goals, buffers, and personal spending.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/first-paycheck-plan/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-first-paycheck-plan/hero.svg</image:loc>
      <image:title>첫 월급 사용 계획: 소비보다 자동화 구조를 먼저 만들기</image:title>
      <image:caption>첫 월급은 소비를 늘리기 전에 비상금, 고정비, 저축 자동이체, 신용 관리 습관을 만드는 가장 좋은 시점이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/first-paycheck-plan/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-first-paycheck-plan/hero.svg</image:loc>
      <image:title>First Paycheck Plan: Build Automation Before Lifestyle Inflation</image:title>
      <image:caption>The first paycheck is the best moment to build emergency cash, bill structure, automatic savings, and credit habits before lifestyle inflation.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/investment-scam-red-flags/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-investment-scam-red-flags/hero.svg</image:loc>
      <image:title>투자 사기 위험 신호: 원금보장 고수익이라는 말부터 의심하기</image:title>
      <image:caption>투자 사기는 높은 수익률보다 원금보장, 비밀 유지, 모집 보상, 등록되지 않은 상품, 출금 지연 같은 신호로 먼저 드러난다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/investment-scam-red-flags/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-investment-scam-red-flags/hero.svg</image:loc>
      <image:title>Investment Scam Red Flags: Start With Guaranteed High Returns</image:title>
      <image:caption>Investment scams reveal themselves through guaranteed returns, secrecy, recruitment rewards, unregistered products, and withdrawal delays.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/travel-fx-budget/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-travel-fx-budget/hero.svg</image:loc>
      <image:title>여행 환전 예산: 환율보다 수수료와 결제 방식을 같이 보기</image:title>
      <image:caption>해외여행 예산은 환율 한 줄보다 카드 수수료, 현금 인출 수수료, 환전 시점, 비상 결제수단을 함께 봐야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/travel-fx-budget/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-travel-fx-budget/hero.svg</image:loc>
      <image:title>Travel FX Budget: Exchange Rate, Fees, and Payment Method Together</image:title>
      <image:caption>A travel budget needs card fees, ATM fees, exchange timing, and backup payment methods, not just the headline exchange rate.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/inflation-adjusted-goals/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-inflation-adjusted-goals/hero.svg</image:loc>
      <image:title>물가를 반영한 목표금액 계산: 오늘의 1천만원은 미래에도 같지 않다</image:title>
      <image:caption>장기 목표금액은 현재 가격만으로 정하면 부족해질 수 있다. 교육비, 주거비, 은퇴 생활비는 물가와 기간을 함께 반영해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/inflation-adjusted-goals/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-inflation-adjusted-goals/hero.svg</image:loc>
      <image:title>Inflation-Adjusted Goals: Today&apos;s Amount Is Not Tomorrow&apos;s Buying Power</image:title>
      <image:caption>Long-term goals can fall short if based only on today&apos;s prices. Education, housing, and retirement needs should include inflation and time.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/retirement-contribution-order/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-retirement-contribution-order/hero.svg</image:loc>
      <image:title>은퇴저축 우선순위 세우기: 비상금, 고금리 부채, 장기투자 순서</image:title>
      <image:caption>은퇴저축은 무조건 많이 넣기보다 비상금, 고금리 부채, 세제혜택, 장기 목표를 같은 순서표에 놓고 결정해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/retirement-contribution-order/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-retirement-contribution-order/hero.svg</image:loc>
      <image:title>Retirement Contribution Order: Emergency Cash, High-Rate Debt, Then Long-Term Investing</image:title>
      <image:caption>Retirement saving should be decided with emergency cash, high-rate debt, tax benefits, and long-term goals in one priority map.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/portfolio-rebalancing-rules/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-portfolio-rebalancing-rules/hero.svg</image:loc>
      <image:title>포트폴리오 리밸런싱 규칙: 오른 자산을 파는 것이 왜 어려운가</image:title>
      <image:caption>리밸런싱은 수익률 예측이 아니라 목표 위험 수준으로 돌아가는 절차다. 미리 정한 규칙이 없으면 감정이 결정을 대신한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/portfolio-rebalancing-rules/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-portfolio-rebalancing-rules/hero.svg</image:loc>
      <image:title>Portfolio Rebalancing Rules: Why Selling Winners Feels Hard</image:title>
      <image:caption>Rebalancing is not return prediction; it is a process for returning to target risk. Without rules, emotions take over.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/target-date-fund-basics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-target-date-fund-basics/hero.svg</image:loc>
      <image:title>타깃데이트펀드 기본: 은퇴 시점에 맞춘 자동 자산배분 이해하기</image:title>
      <image:caption>타깃데이트펀드는 목표 은퇴연도에 맞춰 자산배분이 점차 보수적으로 변하도록 설계된 펀드지만 비용과 운용 방식은 상품마다 다르다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/target-date-fund-basics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-target-date-fund-basics/hero.svg</image:loc>
      <image:title>Target-Date Fund Basics: Understanding Automatic Allocation by Retirement Year</image:title>
      <image:caption>A target-date fund gradually shifts allocation toward a retirement year, but costs and glide paths vary by product.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/etf-selection-checklist/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-etf-selection-checklist/hero.svg</image:loc>
      <image:title>ETF 선택 체크리스트: 이름보다 지수, 비용, 거래량, 보유종목 보기</image:title>
      <image:caption>ETF 이름은 비슷해도 추종지수, 보유종목, 비용, 거래량, 환헤지 여부가 다르면 완전히 다른 상품이 될 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/etf-selection-checklist/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-etf-selection-checklist/hero.svg</image:loc>
      <image:title>ETF Selection Checklist: Index, Cost, Liquidity, and Holdings Before the Name</image:title>
      <image:caption>ETFs with similar names can differ sharply by index, holdings, cost, liquidity, and currency hedging.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/investment-fees-expense-ratio/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-investment-fees-expense-ratio/hero.svg</image:loc>
      <image:title>투자 수수료와 비용비율: 작아 보여도 장기 수익률을 갉아먹는 숫자</image:title>
      <image:caption>투자 수수료는 매년 작아 보여도 장기 복리에서는 수익률을 지속적으로 깎는다. 상품 비교에는 비용비율과 거래비용이 함께 필요하다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/investment-fees-expense-ratio/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-investment-fees-expense-ratio/hero.svg</image:loc>
      <image:title>Investment Fees and Expense Ratios: Small Numbers That Compound Against You</image:title>
      <image:caption>Investment fees can look small each year, but over long horizons they compound against returns. Compare expense ratios and transaction costs together.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/asset-allocation-diversification/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-asset-allocation-diversification/hero.svg</image:loc>
      <image:title>자산배분과 분산투자: 수익률보다 먼저 위험을 나누는 법</image:title>
      <image:caption>자산배분은 어떤 상품이 오를지 맞히는 일이 아니라 주식, 채권, 현금 같은 자산군을 목표와 위험에 맞게 나누는 과정이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/asset-allocation-diversification/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-asset-allocation-diversification/hero.svg</image:loc>
      <image:title>Asset Allocation and Diversification: Splitting Risk Before Chasing Return</image:title>
      <image:caption>Asset allocation is not guessing the winner; it divides stocks, bonds, cash, and other assets according to goals and risk.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/risk-tolerance-time-horizon/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-risk-tolerance-time-horizon/hero.svg</image:loc>
      <image:title>투자 위험감내도와 기간: 같은 ETF도 목표에 따라 다르게 보인다</image:title>
      <image:caption>투자 상품의 좋고 나쁨은 목표 기간과 손실 감내도에 따라 달라진다. 단기 돈과 장기 돈은 같은 위험을 가져서는 안 된다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/risk-tolerance-time-horizon/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-risk-tolerance-time-horizon/hero.svg</image:loc>
      <image:title>Risk Tolerance and Time Horizon: The Same ETF Looks Different by Goal</image:title>
      <image:caption>An investment&apos;s fit depends on time horizon and loss tolerance. Short-term money and long-term money should not carry the same risk.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/freelancer-tax-buckets/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-freelancer-tax-buckets/hero.svg</image:loc>
      <image:title>프리랜서 세금 통장 나누기: 매출과 내 돈을 분리하는 습관</image:title>
      <image:caption>프리랜서와 부업 소득자는 입금액 전체를 생활비로 보면 세금과 비용을 늦게 발견한다. 세금, 비용, 생활비 통장을 나눠야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/freelancer-tax-buckets/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-freelancer-tax-buckets/hero.svg</image:loc>
      <image:title>Freelancer Tax Buckets: Separating Revenue From Your Own Money</image:title>
      <image:caption>Freelancers and side earners should not treat gross receipts as spendable income. Separate tax, business cost, and living expense buckets.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/tax-withholding-checkup/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-tax-withholding-checkup/hero.svg</image:loc>
      <image:title>세금 원천징수 점검: 환급액보다 현금흐름을 기준으로 보기</image:title>
      <image:caption>세금 원천징수는 환급을 크게 받는 게임이 아니라 연중 현금흐름과 납부 부족 위험을 균형 있게 맞추는 과정이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/tax-withholding-checkup/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-tax-withholding-checkup/hero.svg</image:loc>
      <image:title>Tax Withholding Checkup: Read Refunds Through Cash Flow</image:title>
      <image:caption>Tax withholding is not a game of maximizing refunds; it balances year-round cash flow against underpayment risk.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/subscription-audit/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-subscription-audit/hero.svg</image:loc>
      <image:title>구독 지출 감사: 작은 자동결제가 예산을 잠식하는 방식</image:title>
      <image:caption>구독 지출은 한 건씩 보면 작지만 자동결제와 무료체험 전환이 누적되면 고정비처럼 예산을 잠식한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/subscription-audit/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-subscription-audit/hero.svg</image:loc>
      <image:title>Subscription Audit: How Small Auto-Payments Eat the Budget</image:title>
      <image:caption>Subscriptions look small one by one, but auto-payments and trial conversions can turn them into a hidden fixed-cost layer.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/insurance-deductible-buffer/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-insurance-deductible-buffer/hero.svg</image:loc>
      <image:title>보험 자기부담금과 비상금: 보험이 있어도 현금이 필요한 이유</image:title>
      <image:caption>보험은 큰 손실을 줄이지만 자기부담금, 면책기간, 보상 전 선지출 때문에 별도 현금 완충이 필요하다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/insurance-deductible-buffer/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-insurance-deductible-buffer/hero.svg</image:loc>
      <image:title>Insurance Deductibles and Cash Buffers: Why Coverage Still Needs Cash</image:title>
      <image:caption>Insurance reduces large losses, but deductibles, waiting periods, and upfront costs still require a cash buffer.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/rent-vs-buy-framework/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-rent-vs-buy-framework/hero.svg</image:loc>
      <image:title>전월세와 매수 비교 프레임: 가격 전망보다 현금흐름 먼저 보기</image:title>
      <image:caption>집을 살지 빌릴지의 판단은 가격이 오를지보다 거주 기간, 초기비용, 대출 부담, 이동성, 수리 책임을 함께 비교해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/rent-vs-buy-framework/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-rent-vs-buy-framework/hero.svg</image:loc>
      <image:title>Rent vs Buy Framework: Cash Flow Before Price Forecasts</image:title>
      <image:caption>Rent-vs-buy decisions should compare time horizon, upfront cost, debt load, mobility, and repair responsibility before price forecasts.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/mortgage-affordability-stress-test/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-mortgage-affordability-stress-test/hero.svg</image:loc>
      <image:title>주택대출 감당 가능성 테스트: 승인 가능 금액과 살 수 있는 금액은 다르다</image:title>
      <image:caption>주택대출은 승인 한도보다 이자 상승, 보험료, 세금, 수리비, 소득 공백을 견딜 수 있는지가 더 중요한 판단 기준이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/mortgage-affordability-stress-test/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-mortgage-affordability-stress-test/hero.svg</image:loc>
      <image:title>Mortgage Affordability Stress Test: Approval Amount Is Not Affordability</image:title>
      <image:caption>Mortgage affordability is less about the approval amount and more about surviving rate changes, insurance, taxes, repairs, and income gaps.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/auto-loan-total-cost/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-auto-loan-total-cost/hero.svg</image:loc>
      <image:title>자동차 대출 총비용 계산: 차값보다 기간과 보험료가 더 중요할 때</image:title>
      <image:caption>자동차 구매 예산은 차량 가격뿐 아니라 대출 기간, 금리, 보험료, 세금, 정비비, 감가상각을 함께 봐야 현실적이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/auto-loan-total-cost/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-auto-loan-total-cost/hero.svg</image:loc>
      <image:title>Auto Loan Total Cost: When Term and Insurance Matter More Than Sticker Price</image:title>
      <image:caption>A car budget needs loan term, rate, insurance, taxes, maintenance, and depreciation, not just the sticker price.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/bnpl-installment-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-bnpl-installment-risk/hero.svg</image:loc>
      <image:title>BNPL과 할부 결제 리스크: 작은 결제가 여러 개일 때 생기는 착시</image:title>
      <image:caption>BNPL과 할부는 구매 장벽을 낮추지만 여러 결제가 겹치면 실제 월 고정지출이 보이지 않게 커질 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/bnpl-installment-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-bnpl-installment-risk/hero.svg</image:loc>
      <image:title>BNPL and Installment Risk: The Illusion of Many Small Payments</image:title>
      <image:caption>BNPL and installments lower purchase friction, but stacked small payments can hide the real monthly fixed-spending load.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/loan-apr-total-cost/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-loan-apr-total-cost/hero.svg</image:loc>
      <image:title>대출 금리와 APR 차이: 월상환액보다 총비용을 먼저 계산하기</image:title>
      <image:caption>대출 비교에서는 월상환액이 작아 보이는지보다 금리, 수수료, 기간, 중도상환 조건을 합친 총비용을 봐야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/loan-apr-total-cost/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-loan-apr-total-cost/hero.svg</image:loc>
      <image:title>Interest Rate vs APR: Read Total Loan Cost Before the Monthly Payment</image:title>
      <image:caption>Loan comparison should focus on total cost across rate, fees, term, and prepayment terms, not just a smaller-looking monthly payment.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/credit-report-dispute/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-credit-report-dispute/hero.svg</image:loc>
      <image:title>신용보고서 오류 정정 순서: 증거를 모아 양쪽에 이의제기하기</image:title>
      <image:caption>신용보고서 오류는 점수를 낮출 수 있으므로 보고기관과 정보를 제공한 금융회사 양쪽에 근거 자료를 붙여 정정 요청을 해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/credit-report-dispute/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-credit-report-dispute/hero.svg</image:loc>
      <image:title>Credit Report Dispute Order: Gather Evidence and Dispute Both Sides</image:title>
      <image:caption>Credit report errors can lower scores, so disputes should include evidence and be sent to both the reporting company and the data furnisher.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/credit-score-factors/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-credit-score-factors/hero.svg</image:loc>
      <image:title>신용점수 핵심 요인: 점수보다 보고서 내용을 먼저 보기</image:title>
      <image:caption>신용점수는 하나의 숫자처럼 보이지만 실제로는 결제 이력, 한도 사용률, 계좌 기간, 신규 신청, 보고서 오류가 합쳐진 결과다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/credit-score-factors/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-credit-score-factors/hero.svg</image:loc>
      <image:title>Credit Score Factors: Read the Report Before the Number</image:title>
      <image:caption>A credit score looks like one number, but it reflects payment history, utilization, account age, new applications, and report accuracy.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/credit-card-minimum-payment-trap/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-credit-card-minimum-payment-trap/hero.svg</image:loc>
      <image:title>신용카드 최소결제의 함정: 이번 달을 넘기면 다음 달이 커진다</image:title>
      <image:caption>최소결제는 연체를 막는 임시 장치일 수 있지만 잔액과 이자를 오래 남겨 다음 달 현금흐름을 더 약하게 만들 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/credit-card-minimum-payment-trap/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-credit-card-minimum-payment-trap/hero.svg</image:loc>
      <image:title>The Minimum Payment Trap: Why Next Month Gets More Expensive</image:title>
      <image:caption>A minimum payment can prevent delinquency, but it can also leave balances and interest that weaken next month&apos;s cash flow.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/debt-avalanche-vs-snowball/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-debt-avalanche-vs-snowball/hero.svg</image:loc>
      <image:title>부채 상환 눈사태와 눈덩이 방식: 이자 절감과 지속성 사이 선택</image:title>
      <image:caption>부채 상환 전략은 수학적으로 유리한 방식과 행동적으로 지속 가능한 방식 사이에서 자신의 현금흐름에 맞게 선택해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/debt-avalanche-vs-snowball/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-debt-avalanche-vs-snowball/hero.svg</image:loc>
      <image:title>Debt Avalanche vs Snowball: Choosing Between Interest Savings and Momentum</image:title>
      <image:caption>Debt payoff strategy is a tradeoff between the mathematically efficient route and the behaviorally sustainable route.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/sinking-funds-irregular-expenses/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-sinking-funds-irregular-expenses/hero.svg</image:loc>
      <image:title>싱킹펀드로 비정기 지출 막기: 명절, 보험료, 여행비를 월별로 쪼개기</image:title>
      <image:caption>비정기 지출은 예상하지 못한 지출이 아니라 준비하지 않은 지출인 경우가 많다. 싱킹펀드는 연간 비용을 월별 저축으로 바꾼다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/sinking-funds-irregular-expenses/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-sinking-funds-irregular-expenses/hero.svg</image:loc>
      <image:title>Sinking Funds for Irregular Expenses: Turning Annual Bills Into Monthly Plans</image:title>
      <image:caption>Many irregular expenses are not surprises; they are unplanned known costs. Sinking funds convert annual bills into monthly savings.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/emergency-fund-tiers/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-emergency-fund-tiers/hero.svg</image:loc>
      <image:title>비상금 3단계 설계: 100만원, 한 달, 6개월을 나누는 이유</image:title>
      <image:caption>비상금은 하나의 숫자가 아니라 작은 사고, 소득 공백, 장기 위기를 나누어 버티게 하는 현금 완충 장치다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/emergency-fund-tiers/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-emergency-fund-tiers/hero.svg</image:loc>
      <image:title>Three Emergency Fund Tiers: Starter Cash, One Month, and Six Months</image:title>
      <image:caption>An emergency fund is not one magic number; it is a cash buffer for small shocks, income gaps, and longer emergencies.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_personal_finance/paycheck-budget-calendar/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-paycheck-budget-calendar/hero.svg</image:loc>
      <image:title>월급날 예산 캘린더 만들기: 돈이 사라지기 전에 이름 붙이기</image:title>
      <image:caption>예산은 지출을 억누르는 장부가 아니라 월급이 들어온 순간 고정비, 저축, 변동비, 예비비에 역할을 배정하는 운영표다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_personal_finance/paycheck-budget-calendar/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-20-paycheck-budget-calendar/hero.svg</image:loc>
      <image:title>Paycheck Budget Calendar: Name the Money Before It Disappears</image:title>
      <image:caption>A budget is not a punishment ledger; it is an operating calendar that assigns each paycheck to bills, savings, flexible spending, and reserves.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/family-health-records/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-family-health-records/hero.svg</image:loc>
      <image:title>가족 건강기록 정리: 병력, 약, 알레르기, 접종 기록을 찾기 쉽게</image:title>
      <image:caption>가족 건강기록은 응급상황과 진료 준비에 도움이 되며 병력, 복용약, 알레르기, 접종 기록, 가족력을 찾기 쉽게 정리해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/family-health-records/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-family-health-records/hero.svg</image:loc>
      <image:title>Family Health Records: Conditions, Medicines, Allergies, and Vaccines</image:title>
      <image:caption>Family health records help emergencies and appointments when conditions, medicines, allergies, vaccinations, and family history are easy to find.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/doctor-visit-question-list/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-doctor-visit-question-list/hero.svg</image:loc>
      <image:title>진료 전 질문 목록 만들기: 증상, 약, 목표를 짧게 정리하기</image:title>
      <image:caption>짧은 진료시간을 잘 쓰려면 증상 시작일, 악화·완화 요인, 복용약, 알레르기, 가장 궁금한 질문을 미리 정리해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/doctor-visit-question-list/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-doctor-visit-question-list/hero.svg</image:loc>
      <image:title>Doctor Visit Question List: Symptoms, Medicines, and Goals in One Page</image:title>
      <image:caption>A short medical visit works better when symptom timeline, triggers, medicines, allergies, and top questions are prepared in advance.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/fever-monitoring-basics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-fever-monitoring-basics/hero.svg</image:loc>
      <image:title>열이 날 때 기록할 것: 체온 숫자보다 나이, 증상, 지속시간</image:title>
      <image:caption>열은 체온 숫자 하나보다 나이, 동반 증상, 지속시간, 수분 섭취, 기저질환 여부를 함께 봐야 판단이 안전하다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/fever-monitoring-basics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-fever-monitoring-basics/hero.svg</image:loc>
      <image:title>Fever Monitoring Basics: Age, Symptoms, and Duration Beyond the Number</image:title>
      <image:caption>Fever should be read with age, symptoms, duration, fluid intake, and underlying conditions, not only one temperature number.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/first-aid-emergency-plan/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-first-aid-emergency-plan/hero.svg</image:loc>
      <image:title>가정 응급상황 계획: 전화번호, 약, 병력, 대피 동선을 한 곳에</image:title>
      <image:caption>응급상황에서는 기억보다 준비된 정보가 중요하므로 가족 연락처, 복용약, 병력, 알레르기, 병원, 대피 동선을 한 곳에 정리해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/first-aid-emergency-plan/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-first-aid-emergency-plan/hero.svg</image:loc>
      <image:title>Home First Aid Plan: Contacts, Medicines, Conditions, and Exit Routes</image:title>
      <image:caption>In emergencies, prepared information beats memory: contacts, medicines, conditions, allergies, hospitals, and exit routes should be organized.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/healthy-weight-non-scale/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-healthy-weight-non-scale/hero.svg</image:loc>
      <image:title>체중 관리의 비체중 지표: 숫자보다 허리, 체력, 수면, 혈압 보기</image:title>
      <image:caption>체중 관리는 체중계 숫자만으로 판단하기보다 허리둘레, 체력, 식사 패턴, 수면, 혈압, 지속 가능한 습관을 함께 봐야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/healthy-weight-non-scale/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-healthy-weight-non-scale/hero.svg</image:loc>
      <image:title>Healthy Weight Beyond the Scale: Waist, Fitness, Sleep, and Blood Pressure</image:title>
      <image:caption>Weight management should include waist, fitness, eating patterns, sleep, blood pressure, and sustainable habits, not only the scale.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/oral-health-daily-routine/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-oral-health-daily-routine/hero.svg</image:loc>
      <image:title>성인 구강건강 루틴: 칫솔질, 치실, 당 섭취, 검진을 묶어 보기</image:title>
      <image:caption>구강건강은 양치 횟수만이 아니라 치실, 당 섭취 빈도, 흡연, 정기 검진, 잇몸 출혈 같은 신호를 함께 봐야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/oral-health-daily-routine/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-oral-health-daily-routine/hero.svg</image:loc>
      <image:title>Adult Oral Health Routine: Brushing, Flossing, Sugar, and Checkups</image:title>
      <image:caption>Oral health depends on more than brushing frequency; flossing, sugar frequency, smoking, checkups, and gum bleeding matter too.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/hearing-protection-noise/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-hearing-protection-noise/hero.svg</image:loc>
      <image:title>청력 보호 습관: 이어폰 볼륨보다 노출 시간을 함께 보기</image:title>
      <image:caption>청력 손상 위험은 소리 크기뿐 아니라 노출 시간, 휴식, 귀마개 사용, 작업·공연 환경이 함께 결정한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/hearing-protection-noise/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-hearing-protection-noise/hero.svg</image:loc>
      <image:title>Hearing Protection Habits: Volume and Exposure Time Together</image:title>
      <image:caption>Hearing risk depends on loudness, exposure time, rest breaks, hearing protection, and work or concert environments together.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/sun-safety-uv-routine/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-sun-safety-uv-routine/hero.svg</image:loc>
      <image:title>자외선 안전 루틴: 선크림만이 아니라 시간과 옷까지 보기</image:title>
      <image:caption>자외선 관리는 선크림 하나로 끝나지 않으며 야외 시간, 그늘, 모자와 긴 옷, 재도포 습관을 함께 관리해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/sun-safety-uv-routine/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-sun-safety-uv-routine/hero.svg</image:loc>
      <image:title>Sun Safety Routine: Sunscreen, Timing, Clothing, and Shade</image:title>
      <image:caption>Sun protection is not only sunscreen; it includes timing, shade, hats, protective clothing, and reapplication habits.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/allergy-symptom-tracker/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-allergy-symptom-tracker/hero.svg</image:loc>
      <image:title>알레르기 증상 기록법: 계절, 음식, 약, 환경을 함께 보기</image:title>
      <image:caption>알레르기 증상은 계절, 실내 환경, 음식, 약, 반려동물, 야외활동과 연결될 수 있어 패턴 기록이 진료 상담에 도움이 된다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/allergy-symptom-tracker/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-allergy-symptom-tracker/hero.svg</image:loc>
      <image:title>Allergy Symptom Tracking: Season, Food, Medicine, and Environment Together</image:title>
      <image:caption>Allergy symptoms may connect with season, indoor environment, food, medicine, pets, or outdoor activity, so pattern tracking helps conversations with clinicians.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/depression-warning-signs/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-depression-warning-signs/hero.svg</image:loc>
      <image:title>우울 신호 점검: 기분보다 기능 변화와 안전을 먼저 보기</image:title>
      <image:caption>우울은 슬픔만이 아니라 흥미 감소, 수면·식욕 변화, 피로, 집중력 저하, 자해 생각처럼 기능과 안전의 변화로 나타날 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/depression-warning-signs/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-depression-warning-signs/hero.svg</image:loc>
      <image:title>Depression Warning Signs: Function and Safety Before Mood Labels</image:title>
      <image:caption>Depression can show up as loss of interest, sleep or appetite change, fatigue, poor concentration, or thoughts of self-harm, not only sadness.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/anxiety-seek-help/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-anxiety-seek-help/hero.svg</image:loc>
      <image:title>불안이 생활을 방해할 때: 걱정과 도움 요청 사이의 기준</image:title>
      <image:caption>불안은 누구나 느끼지만 회피, 수면 문제, 신체 증상, 일상 기능 저하가 지속되면 혼자 버티기보다 도움을 요청해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/anxiety-seek-help/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-anxiety-seek-help/hero.svg</image:loc>
      <image:title>When Anxiety Disrupts Life: A Practical Threshold for Seeking Help</image:title>
      <image:caption>Anxiety is common, but persistent avoidance, sleep problems, physical symptoms, or impaired daily function are reasons to seek support.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/stress-body-signal/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-stress-body-signal/hero.svg</image:loc>
      <image:title>스트레스 신체 신호 읽기: 피로, 수면, 식욕, 통증을 한 장에 보기</image:title>
      <image:caption>스트레스는 기분만의 문제가 아니라 수면, 식욕, 소화, 통증, 집중력 변화로 나타날 수 있어 신체 신호를 함께 봐야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/stress-body-signal/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-stress-body-signal/hero.svg</image:loc>
      <image:title>Reading Body Signals of Stress: Fatigue, Sleep, Appetite, and Pain</image:title>
      <image:caption>Stress is not only a mood issue; it can show up through sleep, appetite, digestion, pain, and concentration changes.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/heartburn-warning-signs/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-heartburn-warning-signs/hero.svg</image:loc>
      <image:title>속쓰림과 흉통 구분 질문: 반복되는 불편감을 기록하는 법</image:title>
      <image:caption>속쓰림처럼 느껴지는 불편감도 흉통, 호흡곤란, 식은땀, 팔·턱 통증과 함께 나타나면 즉시 확인해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/heartburn-warning-signs/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-heartburn-warning-signs/hero.svg</image:loc>
      <image:title>Heartburn or Chest Pain: Questions for Repeating Discomfort</image:title>
      <image:caption>Discomfort that feels like heartburn needs urgent attention if it appears with chest pain, shortness of breath, sweating, or arm or jaw pain.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/headache-migraine-red-flags/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-headache-migraine-red-flags/hero.svg</image:loc>
      <image:title>두통과 편두통 기록법: 평소와 다른 두통을 구분하기</image:title>
      <image:caption>두통은 흔하지만 갑작스럽고 심한 두통, 신경 증상, 발열, 외상 후 두통처럼 평소와 다른 양상은 빠르게 확인해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/headache-migraine-red-flags/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-headache-migraine-red-flags/hero.svg</image:loc>
      <image:title>Headache and Migraine Tracking: Spotting What Is Different</image:title>
      <image:caption>Headaches are common, but sudden severe pain, neurologic symptoms, fever, or headache after injury should be treated differently from a usual pattern.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/back-pain-seek-care/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-back-pain-seek-care/hero.svg</image:loc>
      <image:title>허리 통증 기록법: 쉬어도 되는 통증과 확인해야 할 신호</image:title>
      <image:caption>허리 통증은 흔하지만 다리 힘 빠짐, 감각 이상, 배뇨 문제, 외상 후 통증처럼 확인이 필요한 신호를 구분해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/back-pain-seek-care/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-back-pain-seek-care/hero.svg</image:loc>
      <image:title>Back Pain Tracking: When to Watch and When to Seek Care</image:title>
      <image:caption>Back pain is common, but warning signals such as leg weakness, numbness, bladder problems, or pain after injury need careful attention.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/antibiotics-when-not-needed/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-antibiotics-when-not-needed/hero.svg</image:loc>
      <image:title>항생제가 필요하지 않을 때: 감기와 바이러스 감염을 구분해 묻기</image:title>
      <image:caption>항생제는 세균 감염 치료에 쓰이는 약이며 감기 같은 바이러스 감염에는 도움이 되지 않을 수 있어 필요한 경우를 의료진과 확인해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/antibiotics-when-not-needed/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-antibiotics-when-not-needed/hero.svg</image:loc>
      <image:title>When Antibiotics Are Not Needed: Asking Better Questions About Viral Illness</image:title>
      <image:caption>Antibiotics treat bacterial infections and may not help viral illnesses such as common colds, so the right question is when they are actually needed.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/otc-medicine-label/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-otc-medicine-label/hero.svg</image:loc>
      <image:title>일반의약품 라벨 읽기: 같은 성분 중복 복용을 피하는 법</image:title>
      <image:caption>일반의약품은 쉽게 살 수 있지만 같은 성분 중복, 복용 간격, 기존 질환, 다른 약과의 상호작용을 확인해야 안전하다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/otc-medicine-label/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-otc-medicine-label/hero.svg</image:loc>
      <image:title>Reading OTC Medicine Labels: Avoiding Duplicate Ingredients</image:title>
      <image:caption>Over-the-counter medicines are accessible, but safety still requires checking duplicate ingredients, timing, conditions, and interactions.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/food-safety-four-steps/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-food-safety-four-steps/hero.svg</image:loc>
      <image:title>식중독 예방 4단계: 손, 분리, 조리온도, 냉장 시간을 지키기</image:title>
      <image:caption>식중독 예방은 좋은 재료보다 손 씻기, 교차오염 방지, 충분한 가열, 적절한 냉장 시간을 반복하는 과정에 달려 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/food-safety-four-steps/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-food-safety-four-steps/hero.svg</image:loc>
      <image:title>Four Food Safety Steps: Clean, Separate, Cook, and Chill</image:title>
      <image:caption>Food safety depends on repeated habits: cleaning, preventing cross-contamination, cooking thoroughly, and chilling properly.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/vaccination-record-review/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-vaccination-record-review/hero.svg</image:loc>
      <image:title>성인 예방접종 기록 점검: 기억보다 기록과 일정표를 믿기</image:title>
      <image:caption>성인 예방접종은 어릴 때 맞은 기억만으로 충분하지 않으며 나이, 직업, 여행, 질환, 임신 여부에 따라 필요한 접종이 달라질 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/vaccination-record-review/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-vaccination-record-review/hero.svg</image:loc>
      <image:title>Adult Vaccination Record Review: Use Records, Not Memory</image:title>
      <image:caption>Adult vaccination needs can change with age, work, travel, medical conditions, and pregnancy; memory alone is not enough.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/respiratory-virus-prevention/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-respiratory-virus-prevention/hero.svg</image:loc>
      <image:title>호흡기 바이러스 예방 루틴: 손씻기, 환기, 마스크, 휴식 판단</image:title>
      <image:caption>호흡기 감염 예방은 한 가지 방법이 아니라 손위생, 환기, 증상 시 휴식, 마스크, 백신 같은 여러 층을 상황에 맞게 조합하는 일이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/respiratory-virus-prevention/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-respiratory-virus-prevention/hero.svg</image:loc>
      <image:title>Respiratory Virus Prevention: Hands, Air, Masks, and Staying Home</image:title>
      <image:caption>Respiratory virus prevention is layered: hand hygiene, ventilation, staying home when sick, masks, and vaccines depending on context.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/prediabetes-risk-screen/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-prediabetes-risk-screen/hero.svg</image:loc>
      <image:title>당뇨병 전단계 위험 읽기: 체중보다 가족력과 검사 주기까지 보기</image:title>
      <image:caption>당뇨병 전단계 위험은 체중만으로 판단하기 어렵고 가족력, 활동량, 혈압, 나이, 검사 결과를 함께 봐야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/prediabetes-risk-screen/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-prediabetes-risk-screen/hero.svg</image:loc>
      <image:title>Prediabetes Risk: Look Beyond Weight to Family History and Screening</image:title>
      <image:caption>Prediabetes risk cannot be read from weight alone; family history, activity, blood pressure, age, and test results all matter.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/blood-pressure-home-check/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-blood-pressure-home-check/hero.svg</image:loc>
      <image:title>가정 혈압 측정 루틴: 한 번의 숫자보다 기록 패턴 보기</image:title>
      <image:caption>혈압은 한 번의 측정보다 올바른 자세, 같은 시간대, 반복 기록, 의료진과의 공유가 더 중요한 생활 지표다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/blood-pressure-home-check/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-blood-pressure-home-check/hero.svg</image:loc>
      <image:title>Home Blood Pressure Checks: Look for Patterns, Not One Number</image:title>
      <image:caption>Blood pressure is more useful as a repeated record with proper position, consistent timing, and clinician review than as one isolated reading.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/heat-illness-prevention/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-heat-illness-prevention/hero.svg</image:loc>
      <image:title>폭염 건강 루틴: 물, 그늘, 휴식, 취약시간을 한 번에 보기</image:title>
      <image:caption>폭염 대응은 물만 마시는 문제가 아니라 활동 시간, 그늘, 휴식, 의복, 기존 질환, 고령자 돌봄을 함께 조정하는 일이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/heat-illness-prevention/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-heat-illness-prevention/hero.svg</image:loc>
      <image:title>Heat Illness Prevention: Water, Shade, Rest, and Timing Together</image:title>
      <image:caption>Heat safety requires activity timing, shade, rest, clothing, existing conditions, and care for vulnerable people, not only drinking water.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/hydration-dehydration-signs/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-hydration-dehydration-signs/hero.svg</image:loc>
      <image:title>수분 부족 신호 읽기: 갈증보다 소변색과 상황을 같이 보기</image:title>
      <image:caption>수분 관리는 물을 많이 마시는 경쟁이 아니라 더위, 운동, 질병, 소변색, 어지러움 같은 상황 신호를 함께 보는 일이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/hydration-dehydration-signs/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-hydration-dehydration-signs/hero.svg</image:loc>
      <image:title>Hydration and Dehydration Signs: Context Beyond Thirst</image:title>
      <image:caption>Hydration is not a contest to drink the most water; it is reading heat, activity, illness, urine color, dizziness, and context together.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/added-sugar-drinks/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-added-sugar-drinks/hero.svg</image:loc>
      <image:title>당류 음료 줄이기: 간식보다 먼저 컵 안의 당을 보기</image:title>
      <image:caption>당류 섭취는 디저트뿐 아니라 커피음료, 주스, 탄산음료, 에너지음료에서 빠르게 늘어날 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/added-sugar-drinks/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-added-sugar-drinks/hero.svg</image:loc>
      <image:title>Reducing Sugary Drinks: Check the Cup Before the Snack</image:title>
      <image:caption>Added sugars can rise quickly through coffee drinks, juice, soda, and energy drinks, not only desserts.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/sodium-label-reading/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-sodium-label-reading/hero.svg</image:loc>
      <image:title>나트륨 표시 읽기: 짠맛보다 하루 총량을 먼저 보기</image:title>
      <image:caption>나트륨은 짠맛이 강한 음식에만 있는 것이 아니라 빵, 소스, 가공식품처럼 자주 먹는 음식에서 누적될 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/sodium-label-reading/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-sodium-label-reading/hero.svg</image:loc>
      <image:title>Reading Sodium Labels: Daily Total Before Salty Taste</image:title>
      <image:caption>Sodium does not come only from obviously salty foods; it can accumulate through bread, sauces, and processed foods eaten often.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/healthy-diet-plate/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-healthy-diet-plate/hero.svg</image:loc>
      <image:title>건강한 식단 접시 구성: 탄수화물 끊기보다 균형을 먼저 보기</image:title>
      <image:caption>건강한 식단은 특정 영양소를 악마화하기보다 채소, 통곡물, 단백질, 건강한 지방, 수분을 균형 있게 배치하는 방식에서 시작한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/healthy-diet-plate/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-healthy-diet-plate/hero.svg</image:loc>
      <image:title>Healthy Plate Basics: Balance Before Cutting Entire Food Groups</image:title>
      <image:caption>A healthy diet starts with balanced vegetables, whole grains, protein, healthy fats, and fluids rather than demonizing one nutrient.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/strength-training-basics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-strength-training-basics/hero.svg</image:loc>
      <image:title>근력운동 초보 기준: 무게보다 자세와 회복을 먼저 보기</image:title>
      <image:caption>근력운동은 무거운 무게보다 기본 동작, 통증 없는 범위, 회복일, 점진적 증가를 안전하게 관리하는 것이 먼저다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/strength-training-basics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-strength-training-basics/hero.svg</image:loc>
      <image:title>Strength Training Basics: Form and Recovery Before Heavier Weight</image:title>
      <image:caption>Strength training starts with basic movements, pain-free range, recovery days, and gradual progression before heavier weights.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/walking-activity-start/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-walking-activity-start/hero.svg</image:loc>
      <image:title>걷기 운동 시작법: 150분 목표보다 지속 가능한 첫 주 만들기</image:title>
      <image:caption>운동은 목표 시간을 크게 잡는 것보다 현재 활동량을 기준으로 작은 걷기 블록을 쌓는 편이 지속 가능하다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/walking-activity-start/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-walking-activity-start/hero.svg</image:loc>
      <image:title>Starting a Walking Plan: Build the First Sustainable Week</image:title>
      <image:caption>Physical activity is easier to sustain when you build small walking blocks from your current baseline instead of starting with an intimidating target.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_health_literacy/sleep-routine-adults/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-sleep-routine-adults/hero.svg</image:loc>
      <image:title>성인 수면 루틴 만들기: 잠이 안 올 때 먼저 바꿀 환경과 시간표</image:title>
      <image:caption>수면 관리는 특별한 보조제보다 일정한 기상 시간, 빛 노출, 카페인 시간, 침실 환경을 반복해서 조정하는 생활 루틴에서 시작한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_health_literacy/sleep-routine-adults/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-19-sleep-routine-adults/hero.svg</image:loc>
      <image:title>Adult Sleep Routine: Environment and Timing Before Sleep Hacks</image:title>
      <image:caption>Sleep management starts with repeatable routines such as wake time, light exposure, caffeine timing, and bedroom environment before special hacks.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/clean-tech-industrial-policy/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-clean-tech-industrial-policy/hero.svg</image:loc>
      <image:title>청정기술 산업정책: 보조금 경쟁보다 공급망 위치를 보기</image:title>
      <image:caption>청정기술 산업정책은 보조금 규모보다 태양광, 배터리, 전력기기, 전기차, 수소 장비의 어느 공급망 단계에 설 것인지가 중요하다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/clean-tech-industrial-policy/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-clean-tech-industrial-policy/hero.svg</image:loc>
      <image:title>Clean-Tech Industrial Policy: Supply-Chain Position Before Subsidy Headlines</image:title>
      <image:caption>Clean-tech industrial policy depends less on subsidy size than on where a country sits in solar, batteries, grid equipment, EVs, and hydrogen equipment supply chains.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/energy-import-bill-exchange-rate/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-energy-import-bill-exchange-rate/hero.svg</image:loc>
      <image:title>에너지 수입액과 환율: 원화 약세가 전기·가스비로 오는 경로</image:title>
      <image:caption>에너지 가격이 안정돼도 원화가 약하면 수입액과 공기업 비용 부담이 커질 수 있어 유가와 환율을 같이 봐야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/energy-import-bill-exchange-rate/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-energy-import-bill-exchange-rate/hero.svg</image:loc>
      <image:title>Energy Import Bills and Exchange Rates: How a Weaker Won Reaches Power and Gas Costs</image:title>
      <image:caption>Even when global energy prices stabilize, a weaker won can raise import bills and utility cost pressure, so fuel prices and exchange rates belong together.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/resilience-budget-local-government/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-resilience-budget-local-government/hero.svg</image:loc>
      <image:title>지자체 회복력 예산: 재난 후 복구보다 예방 투자를 먼저 보기</image:title>
      <image:caption>지자체 회복력 예산은 제방, 배수, 폭염쉼터, 산사태, 취약계층 보호처럼 재난 전 피해를 줄이는 투자에 얼마나 배분되는지가 핵심이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/resilience-budget-local-government/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-resilience-budget-local-government/hero.svg</image:loc>
      <image:title>Local Resilience Budgets: Prevention Before Post-Disaster Recovery</image:title>
      <image:caption>Local resilience budgets should be judged by how much they invest before disasters in levees, drainage, cooling shelters, landslide prevention, and protection of vulnerable people.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/climate-finance-project-quality/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-climate-finance-project-quality/hero.svg</image:loc>
      <image:title>기후금융 프로젝트 품질: 녹색 이름보다 실제 감축과 적응 효과 보기</image:title>
      <image:caption>기후금융은 녹색 이름이 붙었다고 충분하지 않으며 실제 감축량, 적응 효과, 추가성, 지역 피해 감소, 사후 측정 방식이 중요하다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/climate-finance-project-quality/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-climate-finance-project-quality/hero.svg</image:loc>
      <image:title>Climate-Finance Project Quality: Impact Before Green Labels</image:title>
      <image:caption>Climate finance is not sufficient because a project has a green label; actual emissions reduction, adaptation impact, additionality, local loss reduction, and measurement matter.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/energy-efficiency-first-fuel/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-energy-efficiency-first-fuel/hero.svg</image:loc>
      <image:title>에너지 효율은 첫 번째 연료다: 절약이 아니라 생산성 전략으로 보기</image:title>
      <image:caption>에너지 효율은 덜 쓰자는 캠페인이 아니라 같은 생산과 생활을 더 적은 에너지로 달성해 수입비용, 전력망 투자, 배출을 동시에 줄이는 전략이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/energy-efficiency-first-fuel/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-energy-efficiency-first-fuel/hero.svg</image:loc>
      <image:title>Energy Efficiency as the First Fuel: Productivity, Not Just Saving</image:title>
      <image:caption>Energy efficiency is not merely using less; it delivers the same output and comfort with less energy, reducing import bills, grid investment, and emissions together.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/water-stress-energy-industry/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-water-stress-energy-industry/hero.svg</image:loc>
      <image:title>물 스트레스와 에너지 산업: 전력·반도체·배터리의 숨은 제약</image:title>
      <image:caption>물 스트레스는 발전소 냉각, 반도체 초순수, 배터리 공정, 데이터센터 냉각을 동시에 제약할 수 있는 산업 인프라 리스크다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/water-stress-energy-industry/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-water-stress-energy-industry/hero.svg</image:loc>
      <image:title>Water Stress and Energy-Intensive Industry: A Hidden Constraint for Power, Chips, and Batteries</image:title>
      <image:caption>Water stress can constrain power-plant cooling, semiconductor ultrapure water, battery processes, and data-centre cooling at the same time.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/extreme-weather-supply-chain-map/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-extreme-weather-supply-chain-map/hero.svg</image:loc>
      <image:title>이상기후 공급망 지도: 공장보다 항만·도로·전력부터 표시하기</image:title>
      <image:caption>이상기후 공급망 관리는 공장 위치만이 아니라 항만, 도로, 철도, 전력, 물류창고, 협력사 복구 능력을 지도화해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/extreme-weather-supply-chain-map/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-extreme-weather-supply-chain-map/hero.svg</image:loc>
      <image:title>Extreme-Weather Supply-Chain Map: Ports, Roads, and Power Before Factories</image:title>
      <image:caption>Extreme-weather supply-chain planning requires mapping ports, roads, rail, power, warehouses, and supplier recovery capacity, not only factory locations.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/climate-risk-scenario-planning/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-climate-risk-scenario-planning/hero.svg</image:loc>
      <image:title>기후 리스크 시나리오: 평균 전망보다 꼬리 위험을 먼저 보기</image:title>
      <image:caption>기후 리스크는 평균 기온이나 평균 강수량보다 극단값, 동시다발 충격, 취약 인프라, 복구 능력이 실제 피해를 좌우한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/climate-risk-scenario-planning/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-climate-risk-scenario-planning/hero.svg</image:loc>
      <image:title>Climate-Risk Scenario Planning: Tail Risks Before Average Forecasts</image:title>
      <image:caption>Climate risk is driven less by average temperature or rainfall than by extremes, compound shocks, fragile infrastructure, and recovery capacity.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/climate-policy-news-reading-system/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-climate-policy-news-reading-system/hero.svg</image:loc>
      <image:title>기후·에너지 정책 뉴스 읽는 시스템: 목표, 수단, 비용, 시간표</image:title>
      <image:caption>기후·에너지 정책은 목표 수치만 보면 과장되거나 과소평가되기 쉽고, 실제로는 정책수단, 재원, 인허가, 전력망, 산업 수요를 함께 봐야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/climate-policy-news-reading-system/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-climate-policy-news-reading-system/hero.svg</image:loc>
      <image:title>A Reading System for Climate and Energy Policy News: Targets, Tools, Costs, Timelines</image:title>
      <image:caption>Climate and energy policy is easy to overrate or dismiss if read only through targets; tools, funding, permits, grids, and industrial demand decide implementation.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/renewable-ppa-re100-export/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-renewable-ppa-re100-export/hero.svg</image:loc>
      <image:title>재생에너지 PPA와 RE100: 수출기업이 전력계약을 봐야 하는 이유</image:title>
      <image:caption>RE100과 재생에너지 PPA는 이미지 캠페인이 아니라 고객 요구, 탄소공시, 전력가격, 공급망 평가와 연결되는 수출 경쟁력 요소다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/renewable-ppa-re100-export/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-renewable-ppa-re100-export/hero.svg</image:loc>
      <image:title>Renewable PPAs and RE100: Why Exporters Need to Read Power Contracts</image:title>
      <image:caption>RE100 and renewable PPAs are not branding exercises; they connect customer requirements, climate disclosure, power prices, and supply-chain evaluation.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/korea-battery-supply-chain-rules/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-korea-battery-supply-chain-rules/hero.svg</image:loc>
      <image:title>한국 배터리 공급망 규칙: 보조금보다 원산지와 광물 기준을 보기</image:title>
      <image:caption>배터리 산업의 경쟁력은 셀 기술뿐 아니라 원산지 규정, 핵심광물 조달, 재활용, 중국 의존도, 미국·유럽 정책 변화에 좌우된다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/korea-battery-supply-chain-rules/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-korea-battery-supply-chain-rules/hero.svg</image:loc>
      <image:title>Korea Battery Supply-Chain Rules: Origin and Minerals Before Subsidies</image:title>
      <image:caption>Battery competitiveness depends not only on cell technology but also on origin rules, critical-mineral sourcing, recycling, China exposure, and US and European policy shifts.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/korea-semiconductor-power-demand/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-korea-semiconductor-power-demand/hero.svg</image:loc>
      <image:title>한국 반도체 전력 수요: 팹 증설 뉴스에서 전력망까지 읽기</image:title>
      <image:caption>반도체 팹 증설은 장비 투자 뉴스만이 아니라 전력 품질, 용수, 송전망, 재생에너지 조달, 지역 인프라 부담까지 포함한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/korea-semiconductor-power-demand/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-korea-semiconductor-power-demand/hero.svg</image:loc>
      <image:title>Korea Semiconductor Power Demand: From Fab Expansion to Grid Capacity</image:title>
      <image:caption>Semiconductor fab expansion is not only equipment capex; it includes power quality, water, transmission, renewable procurement, and regional infrastructure pressure.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/small-business-energy-risk-plan/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-small-business-energy-risk-plan/hero.svg</image:loc>
      <image:title>소상공인 에너지 리스크 계획: 전기·가스비를 고정비처럼 관리하기</image:title>
      <image:caption>소상공인은 에너지비가 매출보다 늦게 반영되는 경우가 많아 계절별 사용량, 설비 효율, 계약 조건, 가격 전가 가능성을 미리 봐야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/small-business-energy-risk-plan/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-small-business-energy-risk-plan/hero.svg</image:loc>
      <image:title>Small-Business Energy Risk Plan: Manage Power and Gas as Core Fixed Costs</image:title>
      <image:caption>Small businesses often feel energy costs after revenue decisions are set, so seasonal use, equipment efficiency, contracts, and pricing power need advance review.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/household-energy-saving-bills/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-household-energy-saving-bills/hero.svg</image:loc>
      <image:title>가정 에너지 절감: 전기요금 뉴스보다 사용 패턴을 먼저 보기</image:title>
      <image:caption>가정 에너지 절감은 전기요금 인상 뉴스에 반응하는 일이 아니라 냉난방, 대기전력, 조명, 가전 교체, 시간대 사용을 조정하는 생활 시스템이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/household-energy-saving-bills/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-household-energy-saving-bills/hero.svg</image:loc>
      <image:title>Household Energy Savings: Usage Patterns Before Tariff Headlines</image:title>
      <image:caption>Household energy saving is not just reacting to tariff news; it is a system of cooling, heating, standby power, lighting, appliance replacement, and time-of-use habits.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/climate-migration-labor-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-climate-migration-labor-risk/hero.svg</image:loc>
      <image:title>기후 이주와 노동 리스크: 인구 문제가 공급망 문제가 되는 순간</image:title>
      <image:caption>기후 충격은 농업, 건설, 물류, 돌봄 노동을 흔들고 지역 이주와 노동력 부족을 통해 공급망 비용으로 이어질 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/climate-migration-labor-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-climate-migration-labor-risk/hero.svg</image:loc>
      <image:title>Climate Migration and Labour Risk: When Population Stress Becomes Supply-Chain Stress</image:title>
      <image:caption>Climate shocks can disrupt agriculture, construction, logistics, and care work, then move into supply-chain costs through migration and labour shortages.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/food-energy-water-nexus/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-food-energy-water-nexus/hero.svg</image:loc>
      <image:title>식량·에너지·물 넥서스: 기후 이슈가 장바구니 가격으로 오는 길</image:title>
      <image:caption>가뭄, 홍수, 에너지 가격, 비료 비용, 물 관리가 연결되면 기후 리스크는 농산물 가격과 식품기업 원가로 이동한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/food-energy-water-nexus/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-food-energy-water-nexus/hero.svg</image:loc>
      <image:title>Food-Energy-Water Nexus: How Climate Risk Reaches Grocery Prices</image:title>
      <image:caption>When drought, floods, energy prices, fertilizer costs, and water management interact, climate risk moves into grocery prices and food-company costs.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/sea-level-port-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-sea-level-port-risk/hero.svg</image:loc>
      <image:title>해수면 상승과 항만 리스크: 무역국가가 놓치면 안 되는 비용</image:title>
      <image:caption>해수면 상승은 먼 미래의 해안선 문제가 아니라 항만, 물류창고, 보험, 배후 산업단지, 수출입 일정에 영향을 주는 리스크다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/sea-level-port-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-sea-level-port-risk/hero.svg</image:loc>
      <image:title>Sea-Level Rise and Port Risk: A Hidden Cost for Trading Economies</image:title>
      <image:caption>Sea-level rise is not only a future coastline issue; it affects ports, warehouses, insurance, industrial zones, and import-export schedules.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/heavy-rain-flood-insurance/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-heavy-rain-flood-insurance/hero.svg</image:loc>
      <image:title>집중호우와 홍수보험: 재난 뉴스에서 재무 리스크까지 읽기</image:title>
      <image:caption>집중호우 리스크는 침수 피해, 배수 인프라, 보험 보장, 부동산 가치, 지방재정까지 연결되는 재무 리스크다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/heavy-rain-flood-insurance/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-heavy-rain-flood-insurance/hero.svg</image:loc>
      <image:title>Heavy Rain and Flood Insurance: From Disaster News to Financial Risk</image:title>
      <image:caption>Heavy-rain risk links flood losses, drainage infrastructure, insurance coverage, property values, and local public finance.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/extreme-heat-city-planning/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-extreme-heat-city-planning/hero.svg</image:loc>
      <image:title>도시 폭염 대책: 기온보다 체감온도와 취약시간을 보기</image:title>
      <image:caption>도시 폭염은 최고기온만이 아니라 습도, 야간 최저기온, 그늘, 냉방 접근성, 야외 노동시간이 피해 규모를 결정한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/extreme-heat-city-planning/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-extreme-heat-city-planning/hero.svg</image:loc>
      <image:title>Urban Heat Planning: Heat Index and Vulnerable Hours Before Temperature</image:title>
      <image:caption>Urban heat risk depends on humidity, nighttime minimums, shade, cooling access, and outdoor work hours, not only the headline temperature.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/adaptation-finance-flood-heat/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-adaptation-finance-flood-heat/hero.svg</image:loc>
      <image:title>기후 적응 금융: 홍수와 폭염 피해를 줄이는 돈의 쓰임</image:title>
      <image:caption>기후 적응 금융은 배출 감축과 달리 이미 커진 폭염, 홍수, 가뭄, 해수면 리스크에 대비해 인프라와 사회 안전망을 바꾸는 투자다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/adaptation-finance-flood-heat/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-adaptation-finance-flood-heat/hero.svg</image:loc>
      <image:title>Adaptation Finance: How Money Reduces Flood and Heat Damage</image:title>
      <image:caption>Adaptation finance differs from mitigation: it funds infrastructure and social protection against heat, floods, droughts, and sea-level risks already increasing.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/climate-disclosure-scope-emissions/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-climate-disclosure-scope-emissions/hero.svg</image:loc>
      <image:title>기후공시와 Scope 배출량: ESG 보고서에서 실제로 봐야 할 것</image:title>
      <image:caption>기후공시는 홍보 문구보다 Scope 1, 2, 3 배출량, 산정 범위, 감축 목표, 자본지출 계획이 일관되는지 확인해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/climate-disclosure-scope-emissions/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-climate-disclosure-scope-emissions/hero.svg</image:loc>
      <image:title>Climate Disclosure and Scope Emissions: What to Read in ESG Reports</image:title>
      <image:caption>Climate disclosure should be read through Scope 1, 2, and 3 emissions, boundary choices, reduction targets, and capital expenditure plans rather than promotional language.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/carbon-pricing-ets-basics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-carbon-pricing-ets-basics/hero.svg</image:loc>
      <image:title>탄소가격과 배출권거래제: 세금 논쟁 전에 원리를 이해하기</image:title>
      <image:caption>탄소가격은 배출 비용을 가격에 반영해 투자 방향을 바꾸는 정책 도구이며, 세금과 배출권거래제는 작동 방식이 다르다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/carbon-pricing-ets-basics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-carbon-pricing-ets-basics/hero.svg</image:loc>
      <image:title>Carbon Pricing and Emissions Trading: Understand the Mechanism Before the Tax Debate</image:title>
      <image:caption>Carbon pricing is a policy tool that reflects emissions costs in prices and investment decisions; carbon taxes and emissions trading work differently.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/lng-contracts-price-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-lng-contracts-price-risk/hero.svg</image:loc>
      <image:title>LNG 장기계약과 현물가격: 가스비 뉴스를 읽는 핵심 차이</image:title>
      <image:caption>LNG 가격 뉴스는 현물가격, 장기계약, 유가연동, 환율, 운송비가 섞여 있어 같은 가스라도 실제 구매 비용이 다르게 나타난다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/lng-contracts-price-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-lng-contracts-price-risk/hero.svg</image:loc>
      <image:title>LNG Long-Term Contracts and Spot Prices: The Key Difference in Gas News</image:title>
      <image:caption>LNG news blends spot prices, long-term contracts, oil-indexation, exchange rates, and shipping costs, so the same gas can imply different purchase costs.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/coal-phase-down-reliability/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-coal-phase-down-reliability/hero.svg</image:loc>
      <image:title>석탄 감축과 전력 신뢰도: 폐쇄 일정만 보면 놓치는 것들</image:title>
      <image:caption>석탄 감축은 배출을 줄이는 핵심 과제지만 폐쇄 일정, 대체 전원, 송전망, 지역 일자리, 전력예비율을 함께 맞춰야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/coal-phase-down-reliability/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-coal-phase-down-reliability/hero.svg</image:loc>
      <image:title>Coal Phase-Down and Reliability: What Closure Dates Miss</image:title>
      <image:caption>Coal phase-down is central to emissions reduction, but closure dates need to align with replacement supply, grids, local jobs, and reserve margins.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/nuclear-restart-new-build-debate/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-nuclear-restart-new-build-debate/hero.svg</image:loc>
      <image:title>원전 재가동과 신규 건설 논쟁: 전력 안정성과 시간표를 분리하기</image:title>
      <image:caption>원전 논쟁은 찬반 구호보다 기존 설비 이용률, 신규 건설 기간, 안전 규제, 폐기물, 전력망 위치를 분리해야 현실적으로 읽힌다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/nuclear-restart-new-build-debate/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-nuclear-restart-new-build-debate/hero.svg</image:loc>
      <image:title>Nuclear Restarts and New Builds: Separate Reliability from Timelines</image:title>
      <image:caption>Nuclear debates become clearer when existing fleet availability, new-build timelines, safety regulation, waste, and grid location are separated from slogans.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/hydrogen-ammonia-realistic-use/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-hydrogen-ammonia-realistic-use/hero.svg</image:loc>
      <image:title>수소와 암모니아의 현실적 용도: 만능 연료보다 선택적 도구로 보기</image:title>
      <image:caption>수소와 암모니아는 모든 에너지 문제의 답이 아니라 전기화가 어려운 산업, 장거리 운송, 저장, 일부 발전 보조 용도에서 먼저 검토해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/hydrogen-ammonia-realistic-use/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-hydrogen-ammonia-realistic-use/hero.svg</image:loc>
      <image:title>Hydrogen and Ammonia: Read Them as Selective Tools, Not Universal Fuels</image:title>
      <image:caption>Hydrogen and ammonia are not answers to every energy problem; they should first be tested in hard-to-electrify industry, long-distance transport, storage, and selected power uses.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/industrial-electrification-heat/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-industrial-electrification-heat/hero.svg</image:loc>
      <image:title>산업 전기화와 공정열: 모든 열을 전기로 바꿀 수는 없다</image:title>
      <image:caption>산업 전기화는 저온 열과 고온 공정, 연속 생산, 전력 품질, 설비 교체 주기가 달라서 업종별로 다른 속도로 진행된다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/industrial-electrification-heat/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-industrial-electrification-heat/hero.svg</image:loc>
      <image:title>Industrial Electrification and Process Heat: Not Every Heat Load Is Equal</image:title>
      <image:caption>Industrial electrification moves at different speeds because low-temperature heat, high-temperature processes, continuous production, power quality, and replacement cycles differ by sector.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/heat-pumps-building-efficiency/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-heat-pumps-building-efficiency/hero.svg</image:loc>
      <image:title>히트펌프와 건물 효율: 냉난방비를 줄이는 전기화의 조건</image:title>
      <image:caption>히트펌프는 냉난방 전기화를 이끌 수 있지만 단열, 피크 전력, 설치 품질, 전기요금 구조가 맞아야 비용 절감 효과가 커진다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/heat-pumps-building-efficiency/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-heat-pumps-building-efficiency/hero.svg</image:loc>
      <image:title>Heat Pumps and Building Efficiency: Conditions for Lower Heating and Cooling Costs</image:title>
      <image:caption>Heat pumps can support building electrification, but insulation, peak power, installation quality, and tariff design shape the cost benefit.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/ev-charging-grid-load/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-ev-charging-grid-load/hero.svg</image:loc>
      <image:title>전기차 충전과 전력망: 충전기 숫자보다 피크 부하를 보기</image:title>
      <image:caption>전기차 충전 문제는 충전기 대수만으로 해결되지 않으며 언제, 어디서, 얼마나 빠르게 충전하는지가 전력망 부담을 결정한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/ev-charging-grid-load/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-ev-charging-grid-load/hero.svg</image:loc>
      <image:title>EV Charging and the Grid: Peak Load Before Charger Counts</image:title>
      <image:caption>EV charging cannot be judged by charger counts alone; when, where, and how fast vehicles charge determines the grid burden.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/ev-market-shift-2026/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-ev-market-shift-2026/hero.svg</image:loc>
      <image:title>2026 전기차 시장 읽기: 성장 둔화 뉴스와 구조적 전환을 구분하기</image:title>
      <image:caption>전기차 시장은 국가별 보조금, 가격, 충전 인프라, 중국 수출, 중고차 가치가 달라서 한 지역 둔화로 전체 전환을 판단하기 어렵다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/ev-market-shift-2026/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-ev-market-shift-2026/hero.svg</image:loc>
      <image:title>Reading the 2026 EV Market: Separate Slowdowns from Structural Change</image:title>
      <image:caption>EV markets vary by subsidies, prices, charging, Chinese exports, and used-car values, so one regional slowdown does not explain the entire transition.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/critical-minerals-refining-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-critical-minerals-refining-risk/hero.svg</image:loc>
      <image:title>핵심광물 정제 리스크: 매장량보다 가공 집중도를 먼저 보기</image:title>
      <image:caption>핵심광물 리스크는 광산 매장량만이 아니라 정제·가공 시설이 어디에 집중되어 있는지, 수출통제가 어디서 나오는지에 달려 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/critical-minerals-refining-risk/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-critical-minerals-refining-risk/hero.svg</image:loc>
      <image:title>Critical Minerals Refining Risk: Processing Concentration Before Reserves</image:title>
      <image:caption>Critical-minerals risk depends not only on mine reserves but also on where refining and processing are concentrated and where export controls emerge.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/battery-storage-flexibility/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-battery-storage-flexibility/hero.svg</image:loc>
      <image:title>배터리 저장장치의 역할: 발전소가 아니라 전력망 유연성으로 보기</image:title>
      <image:caption>배터리 저장장치는 전기를 새로 만드는 설비가 아니라 피크 시간 이동, 재생에너지 변동성 완화, 주파수 안정에 쓰이는 유연성 자산이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/battery-storage-flexibility/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-battery-storage-flexibility/hero.svg</image:loc>
      <image:title>Battery Storage: Read It as Grid Flexibility, Not Just Generation</image:title>
      <image:caption>Battery storage does not create electricity; it shifts peak load, smooths renewable variability, and supports frequency stability as a flexibility asset.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/offshore-wind-supply-chain/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-offshore-wind-supply-chain/hero.svg</image:loc>
      <image:title>해상풍력 공급망: 터빈보다 항만, 선박, 전력망을 먼저 보기</image:title>
      <image:caption>해상풍력 프로젝트는 터빈 기술만으로 움직이지 않고 항만, 설치선, 해저케이블, 주민 수용성, 전력망 접속이 함께 맞아야 진행된다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/offshore-wind-supply-chain/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-offshore-wind-supply-chain/hero.svg</image:loc>
      <image:title>Offshore Wind Supply Chains: Ports, Vessels, and Grids Before Turbines</image:title>
      <image:caption>Offshore wind projects do not move on turbine technology alone; ports, installation vessels, subsea cables, local acceptance, and grid connections all matter.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/solar-pv-curtailment-grid/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-solar-pv-curtailment-grid/hero.svg</image:loc>
      <image:title>태양광 출력제어: 전기가 남는 문제가 아니라 전력망이 막히는 문제</image:title>
      <image:caption>태양광 출력제어는 재생에너지가 쓸모없다는 뜻이 아니라 시간, 장소, 수요, 전력망이 맞지 않을 때 생기는 운영 신호다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/solar-pv-curtailment-grid/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-solar-pv-curtailment-grid/hero.svg</image:loc>
      <image:title>Solar Curtailment: Not Too Much Power, but Power in the Wrong Place</image:title>
      <image:caption>Solar curtailment does not mean renewables are useless; it is an operating signal that timing, location, demand, and grids are mismatched.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/renewables-growth-forecast-2030/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-renewables-growth-forecast-2030/hero.svg</image:loc>
      <image:title>재생에너지 2030 전망: 설치량보다 계통 흡수 능력을 같이 보기</image:title>
      <image:caption>태양광과 풍력 증가는 전력 생산비를 낮출 수 있지만 허가, 계통, 저장, 시장 설계가 따라오지 않으면 실제 활용률이 떨어진다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/renewables-growth-forecast-2030/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-renewables-growth-forecast-2030/hero.svg</image:loc>
      <image:title>Renewables to 2030: Installed Capacity Is Not the Whole Story</image:title>
      <image:caption>Solar and wind growth can lower power costs, but utilization falls if permitting, grids, storage, and market design do not keep pace.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/power-grid-bottlenecks-transition/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-power-grid-bottlenecks-transition/hero.svg</image:loc>
      <image:title>에너지 전환의 병목은 발전량만이 아니라 전력망이다</image:title>
      <image:caption>재생에너지와 전기화가 늘어날수록 전력망 투자, 계통 접속, 변압기 공급, 지역 수용성이 전환 속도를 좌우한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/power-grid-bottlenecks-transition/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-power-grid-bottlenecks-transition/hero.svg</image:loc>
      <image:title>The Energy Transition Bottleneck Is the Grid, Not Only Generation</image:title>
      <image:caption>As renewables and electrification grow, grid investment, connection queues, transformer supply, and local acceptance can determine the real transition speed.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/energy-security-oil-gas-shocks/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-energy-security-oil-gas-shocks/hero.svg</image:loc>
      <image:title>에너지 안보 읽기: 유가와 가스 가격 충격을 분리해서 보는 법</image:title>
      <image:caption>에너지 안보는 유가 한 줄이 아니라 원유, LNG, 전력, 환율, 재고, 지정학 리스크가 동시에 움직이는 복합 비용 문제다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/energy-security-oil-gas-shocks/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-energy-security-oil-gas-shocks/hero.svg</image:loc>
      <image:title>Reading Energy Security: Separate Oil and Gas Price Shocks</image:title>
      <image:caption>Energy security is not one oil-price headline; it is a combined cost problem across crude oil, LNG, electricity, exchange rates, inventories, and geopolitical risk.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_climate_energy/ai-data-center-electricity-demand/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-ai-data-center-electricity-demand/hero.svg</image:loc>
      <image:title>AI 데이터센터 전력 수요: 기술 뉴스가 전력망 뉴스가 되는 이유</image:title>
      <image:caption>AI 투자는 칩과 모델의 문제가 아니라 지역 전력망, 변전 설비, 냉각, 전력구매계약까지 묶인 인프라 경쟁으로 바뀌고 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_climate_energy/ai-data-center-electricity-demand/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-18-ai-data-center-electricity-demand/hero.svg</image:loc>
      <image:title>AI Data-Center Electricity Demand: Why Tech News Is Becoming Grid News</image:title>
      <image:caption>AI investment is becoming an infrastructure race that links chips and models with local grids, substations, cooling, and power purchase agreements.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/complaint-escalation-map/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-complaint-escalation-map/hero.svg</image:loc>
      <image:title>소비자 민원 제기 순서: 판매자, 플랫폼, 결제사, 기관으로 단계화하기</image:title>
      <image:caption>소비자 민원은 처음부터 모든 기관에 보내기보다 판매자, 플랫폼, 결제사, 감독기관 순서로 같은 증거를 정리해 단계적으로 올리는 편이 효과적이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/complaint-escalation-map/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-complaint-escalation-map/hero.svg</image:loc>
      <image:title>Consumer Complaint Escalation Map: Seller, Platform, Payment Provider, Agency</image:title>
      <image:caption>Consumer complaints work better when the same evidence is escalated step by step through seller, platform, payment provider, and agency instead of being scattered everywhere.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/home-repair-contractor-deposit/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-home-repair-contractor-deposit/hero.svg</image:loc>
      <image:title>집수리 계약금 분쟁: 견적서, 공정표, 선금 조건을 먼저 고정하기</image:title>
      <image:caption>집수리와 인테리어 계약은 계약금, 공정표, 자재, 완료일, 추가비용 승인, 하자보수 조건을 문서로 남겨야 분쟁을 줄일 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/home-repair-contractor-deposit/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-home-repair-contractor-deposit/hero.svg</image:loc>
      <image:title>Home Repair Contractor Deposit: Lock Estimate, Milestones, and Payment Terms First</image:title>
      <image:caption>Home repair contracts need written records of deposit, milestones, materials, completion date, extra-work approval, and warranty terms to reduce disputes.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/rental-car-damage-fees/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-rental-car-damage-fees/hero.svg</image:loc>
      <image:title>렌터카 손상비 분쟁: 인수·반납 사진이 핵심 증거</image:title>
      <image:caption>렌터카 손상비는 차량 인수 전후 사진, 연료·주행거리, 기존 흠집, 보험 조건, 반납 확인 기록이 없으면 다투기 어렵다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/rental-car-damage-fees/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-rental-car-damage-fees/hero.svg</image:loc>
      <image:title>Rental Car Damage Fees: Pickup and Return Photos Are Core Evidence</image:title>
      <image:caption>Rental car damage fees are difficult to dispute without pickup and return photos, fuel and mileage records, pre-existing damage, insurance terms, and return confirmation.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/gym-membership-cancel/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-gym-membership-cancel/hero.svg</image:loc>
      <image:title>헬스장 회원권 해지: 구두 약속보다 계약서와 해지 확인</image:title>
      <image:caption>헬스장 회원권 분쟁은 약정 기간, 자동연장, 중도해지 수수료, 양도 가능 여부, 해지 확인서를 계약서에서 확인해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/gym-membership-cancel/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-gym-membership-cancel/hero.svg</image:loc>
      <image:title>Gym Membership Cancellation: Contract and Confirmation Over Verbal Promises</image:title>
      <image:caption>Gym membership disputes depend on contract term, auto-renewal, early cancellation fee, transferability, and written cancellation confirmation.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/identity-theft-after-shopping/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-identity-theft-after-shopping/hero.svg</image:loc>
      <image:title>쇼핑 후 개인정보 도용 의심: 결제 분쟁과 신원도용 대응을 나누기</image:title>
      <image:caption>쇼핑 이후 개인정보 도용이 의심되면 결제 취소만으로 끝내지 말고 계정, 카드, 신용정보, 신고 기록을 단계별로 정리해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/identity-theft-after-shopping/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-identity-theft-after-shopping/hero.svg</image:loc>
      <image:title>Identity Theft After Shopping: Separate Payment Dispute From Identity Recovery</image:title>
      <image:caption>If identity theft is suspected after shopping, payment reversal is not enough; accounts, cards, credit records, and reports need a staged response.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/children-app-privacy-consent/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-children-app-privacy-consent/hero.svg</image:loc>
      <image:title>아동 앱 개인정보 동의: 무료 게임의 권한과 결제를 같이 보기</image:title>
      <image:caption>아동 앱은 무료처럼 보여도 위치, 연락처, 광고 식별자, 앱 내 결제, 구독 동의가 얽힐 수 있어 보호자 설정을 먼저 확인해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/children-app-privacy-consent/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-children-app-privacy-consent/hero.svg</image:loc>
      <image:title>Children&apos;s App Privacy Consent: Permissions and Purchases Together</image:title>
      <image:caption>Children&apos;s apps may look free while combining location, contacts, ad identifiers, in-app purchases, and subscription consent, so guardian settings matter first.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/mobile-plan-contract-change/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-mobile-plan-contract-change/hero.svg</image:loc>
      <image:title>휴대폰 요금제 변경: 위약금과 할인 반환금을 먼저 계산하기</image:title>
      <image:caption>휴대폰 요금제 변경은 월 요금만 보면 안 되고 약정, 단말기 할부, 선택약정 할인, 부가서비스, 위약금까지 총비용으로 봐야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/mobile-plan-contract-change/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-mobile-plan-contract-change/hero.svg</image:loc>
      <image:title>Mobile Plan Change: Calculate Penalties and Lost Discounts First</image:title>
      <image:caption>Mobile plan changes should be read as total cost including contract term, device installment, plan discount, add-ons, and penalties.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/broadband-label-speed-bill/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-broadband-label-speed-bill/hero.svg</image:loc>
      <image:title>인터넷 요금제 라벨 읽기: 속도보다 총비용과 제한 조건 보기</image:title>
      <image:caption>인터넷 요금제는 다운로드 속도뿐 아니라 월 총액, 장비 임대료, 데이터 제한, 약정, 할인 종료 후 요금을 함께 봐야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/broadband-label-speed-bill/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-broadband-label-speed-bill/hero.svg</image:loc>
      <image:title>Broadband Label Reading: Total Cost and Limits Before Speed</image:title>
      <image:caption>Broadband plans should be compared by total monthly cost, equipment rental, data limits, contract term, and post-promotion price, not speed alone.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/telecom-bill-cramming/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-telecom-bill-cramming/hero.svg</image:loc>
      <image:title>통신요금 무단 부가서비스: 작은 금액도 매월 확인하기</image:title>
      <image:caption>통신요금 고지서의 작은 부가서비스도 반복 청구되면 큰 비용이 되므로 서비스명, 가입일, 승인 기록, 해지 확인을 확인해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/telecom-bill-cramming/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-telecom-bill-cramming/hero.svg</image:loc>
      <image:title>Telecom Bill Cramming: Check Small Monthly Add-Ons</image:title>
      <image:caption>Small add-ons on phone bills become costly when repeated, so service name, enrollment date, authorization record, and cancellation confirmation should be checked.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/hotel-resort-fee-check/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-hotel-resort-fee-check/hero.svg</image:loc>
      <image:title>호텔 리조트피와 추가요금: 숙박비 총액을 비교하는 법</image:title>
      <image:caption>숙박 예약은 객실 요금만이 아니라 리조트피, 세금, 청소비, 주차비, 보증금, 취소 수수료를 포함한 총액으로 비교해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/hotel-resort-fee-check/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-hotel-resort-fee-check/hero.svg</image:loc>
      <image:title>Hotel Resort Fees and Add-Ons: Compare the Total Stay Cost</image:title>
      <image:caption>Hotel comparison needs total stay cost including resort fees, taxes, cleaning fees, parking, deposits, and cancellation fees.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/travel-booking-platform-dispute/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-travel-booking-platform-dispute/hero.svg</image:loc>
      <image:title>여행 예약 플랫폼 분쟁: 항공사·호텔·플랫폼 책임을 나누기</image:title>
      <image:caption>여행 예약 플랫폼 분쟁은 실제 서비스 제공자와 결제·예약 중개자가 달라 취소 규정, 환불 주체, 고객센터 기록을 분리해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/travel-booking-platform-dispute/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-travel-booking-platform-dispute/hero.svg</image:loc>
      <image:title>Travel Booking Platform Dispute: Split Airline, Hotel, and Platform Responsibility</image:title>
      <image:caption>Travel booking disputes often split service provider from payment or booking intermediary, so cancellation terms, refund party, and support records must be separated.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/flight-delay-documentation/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-flight-delay-documentation/hero.svg</image:loc>
      <image:title>항공편 지연 기록법: 보상보다 먼저 증거를 모으기</image:title>
      <image:caption>항공편 지연은 원인, 지연 시간, 안내 방송, 식사·숙박 제공, 연결편 손실, 추가 비용 영수증을 한 타임라인에 모아야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/flight-delay-documentation/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-flight-delay-documentation/hero.svg</image:loc>
      <image:title>Flight Delay Documentation: Evidence Before Compensation Claims</image:title>
      <image:caption>Flight delays should be documented with cause, delay time, announcements, meals or lodging offered, missed connections, and extra-cost receipts.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/flight-cancellation-refund/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-flight-cancellation-refund/hero.svg</image:loc>
      <image:title>항공편 취소 환불: 바우처와 현금 환불을 구분하기</image:title>
      <image:caption>항공편 취소 환불은 누가 취소했는지, 대체편을 수락했는지, 결제수단이 무엇인지에 따라 처리 경로가 달라진다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/flight-cancellation-refund/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-flight-cancellation-refund/hero.svg</image:loc>
      <image:title>Flight Cancellation Refund: Separate Vouchers From Cash Refunds</image:title>
      <image:caption>Flight-cancellation refunds depend on who cancelled, whether an alternative was accepted, and what payment method was used.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/repair-estimate-consent/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-repair-estimate-consent/hero.svg</image:loc>
      <image:title>수리 견적과 동의 기록: 예상보다 비싼 청구를 줄이는 법</image:title>
      <image:caption>수리 분쟁은 사전 견적, 추가 작업 승인, 교체 부품, 보증 여부, 결제 전 설명을 기록하면 불필요한 청구 논쟁을 줄일 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/repair-estimate-consent/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-repair-estimate-consent/hero.svg</image:loc>
      <image:title>Repair Estimates and Consent Records: Reducing Surprise Bills</image:title>
      <image:caption>Repair disputes are easier to manage when initial estimate, approval for extra work, parts replaced, warranty status, and pre-payment explanation are recorded.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/warranty-vs-service-contract/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-warranty-vs-service-contract/hero.svg</image:loc>
      <image:title>보증과 서비스계약 차이: 무료 권리와 유료 상품을 구분하기</image:title>
      <image:caption>보증, 연장보증, 서비스계약은 비용, 보장 범위, 제외 조건, 청구 절차가 달라서 결제 전 같은 표로 비교해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/warranty-vs-service-contract/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-warranty-vs-service-contract/hero.svg</image:loc>
      <image:title>Warranty vs Service Contract: Separate Included Rights From Paid Add-Ons</image:title>
      <image:caption>Warranties, extended warranties, and service contracts differ in cost, coverage, exclusions, and claim process, so compare them in one table before paying.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/used-car-before-buying/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-used-car-before-buying/hero.svg</image:loc>
      <image:title>중고차 구매 전 체크: 가격보다 이력과 계약 조건을 먼저 보기</image:title>
      <image:caption>중고차 구매는 낮은 가격보다 차량 이력, 보증 범위, 사고·침수 여부, 수리 기록, 금융 조건, 계약서 문구를 먼저 확인해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/used-car-before-buying/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-used-car-before-buying/hero.svg</image:loc>
      <image:title>Used Car Before Buying: History and Contract Terms Before Price</image:title>
      <image:caption>Used-car buying should start with history, warranty coverage, accident or flood records, repair records, finance terms, and contract wording before price.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/vehicle-recall-vin-check/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-vehicle-recall-vin-check/hero.svg</image:loc>
      <image:title>자동차 리콜 VIN 확인: 중고차와 가족차도 주기적으로 보기</image:title>
      <image:caption>자동차 리콜은 차량번호보다 VIN과 제조 연식으로 확인하는 것이 정확하며 중고차 구매 전후에도 미수리 리콜을 확인해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/vehicle-recall-vin-check/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-vehicle-recall-vin-check/hero.svg</image:loc>
      <image:title>Vehicle Recall VIN Check: Review Used and Family Cars Regularly</image:title>
      <image:caption>Vehicle recalls are more accurately checked by VIN and model year, and open recalls should be reviewed before and after buying a used car.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/food-recall-home-routine/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-food-recall-home-routine/hero.svg</image:loc>
      <image:title>식품 리콜 확인: 냉장고와 영수증을 같이 보는 습관</image:title>
      <image:caption>식품 리콜은 브랜드명만으로 부족하고 제품명, 유통기한, 로트번호, 구매처, 보관 상태를 함께 확인해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/food-recall-home-routine/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-food-recall-home-routine/hero.svg</image:loc>
      <image:title>Food Recall Routine: Check the Refrigerator and Receipt Together</image:title>
      <image:caption>Food recalls require more than brand recognition; product name, expiration date, lot code, store, and storage status should be checked together.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/product-recall-check-routine/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-product-recall-check-routine/hero.svg</image:loc>
      <image:title>제품 리콜 확인 루틴: 아이용품과 전자제품은 구매 후에도 확인하기</image:title>
      <image:caption>제품 안전 리콜은 구매 후에도 발생할 수 있으므로 영수증, 모델명, 제조번호를 저장하고 리콜 데이터베이스를 주기적으로 확인해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/product-recall-check-routine/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-product-recall-check-routine/hero.svg</image:loc>
      <image:title>Product Recall Check Routine: Keep Checking After You Buy</image:title>
      <image:caption>Safety recalls can appear after purchase, so receipts, model numbers, and serial numbers should be saved and checked against recall databases.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/cross-border-shopping-complaint/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-cross-border-shopping-complaint/hero.svg</image:loc>
      <image:title>해외직구 분쟁 제기: 국내 쇼핑몰처럼 처리되지 않을 때</image:title>
      <image:caption>해외직구는 언어, 관할, 반품 배송비, 통관, 결제 분쟁 절차가 달라서 주문 전 판매자 위치와 분쟁 창구를 확인해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/cross-border-shopping-complaint/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-cross-border-shopping-complaint/hero.svg</image:loc>
      <image:title>Cross-Border Shopping Complaint: When It Does Not Work Like a Local Store</image:title>
      <image:caption>Cross-border shopping adds language, jurisdiction, return shipping, customs, and payment-dispute differences, so seller location and complaint channels matter before ordering.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/marketplace-seller-verification/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-marketplace-seller-verification/hero.svg</image:loc>
      <image:title>마켓플레이스 판매자 확인: 플랫폼 이름만 믿지 않기</image:title>
      <image:caption>마켓플레이스 구매는 플랫폼, 실제 판매자, 배송 주체, 반품 주소, 고객센터가 다를 수 있어 거래 상대를 먼저 확인해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/marketplace-seller-verification/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-marketplace-seller-verification/hero.svg</image:loc>
      <image:title>Marketplace Seller Verification: Do Not Trust the Platform Name Alone</image:title>
      <image:caption>Marketplace purchases can split platform, seller, shipper, return address, and support desk, so identify the actual counterparty first.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/junk-fees-total-price/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-junk-fees-total-price/hero.svg</image:loc>
      <image:title>숨은 수수료와 총가격 비교: 결제 마지막 화면까지 봐야 하는 이유</image:title>
      <image:caption>숨은 수수료는 기본 가격 비교를 무너뜨리므로 배송비, 서비스료, 플랫폼 수수료, 취소 수수료를 포함한 총가격으로 비교해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/junk-fees-total-price/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-junk-fees-total-price/hero.svg</image:loc>
      <image:title>Junk Fees and Total Price: Why the Last Checkout Screen Matters</image:title>
      <image:caption>Hidden fees break simple price comparison, so shipping, service fees, platform fees, and cancellation fees need to be included in total price.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/dark-pattern-checkout/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-dark-pattern-checkout/hero.svg</image:loc>
      <image:title>다크패턴 결제 화면: 숨은 동의와 반복 결제를 찾는 법</image:title>
      <image:caption>다크패턴은 소비자가 의도하지 않은 선택을 하도록 화면을 설계하는 방식이므로 체크박스, 회색 글씨, 기본 선택, 타이머 문구를 확인해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/dark-pattern-checkout/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-dark-pattern-checkout/hero.svg</image:loc>
      <image:title>Dark Pattern Checkout: Finding Hidden Consent and Recurring Charges</image:title>
      <image:caption>Dark patterns steer choices through interface design, so check boxes, grey text, default selections, countdown language, and recurring-charge wording.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/fake-review-triage/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-fake-review-triage/hero.svg</image:loc>
      <image:title>가짜 리뷰 판별 루틴: 별점보다 패턴과 증거를 보기</image:title>
      <image:caption>가짜 리뷰는 별점 하나로 판단하기 어렵고 작성 시점, 반복 문구, 사진의 구체성, 구매 인증, 부정 리뷰 대응을 함께 봐야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/fake-review-triage/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-fake-review-triage/hero.svg</image:loc>
      <image:title>Fake Review Triage: Patterns and Evidence Before Star Ratings</image:title>
      <image:caption>Fake reviews are hard to spot from stars alone; timing, repeated wording, photo specificity, verified purchases, and seller responses need to be read together.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/bnpl-refund-dispute/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-bnpl-refund-dispute/hero.svg</image:loc>
      <image:title>BNPL 환불 분쟁: 할부 앱과 판매자 기록을 따로 관리하기</image:title>
      <image:caption>후불결제와 BNPL은 판매자 환불과 결제앱 상환 일정이 따로 움직일 수 있어 환불 승인일과 청구 중단 여부를 분리해서 봐야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/bnpl-refund-dispute/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-bnpl-refund-dispute/hero.svg</image:loc>
      <image:title>BNPL Refund Dispute: Track the App and the Seller Separately</image:title>
      <image:caption>BNPL refunds can split seller approval from payment-app repayment schedules, so refund approval and payment pause need separate tracking.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/debit-bank-unauthorized-charge/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-debit-bank-unauthorized-charge/hero.svg</image:loc>
      <image:title>체크카드·계좌 무단출금: 발견 즉시 해야 할 기록과 신고</image:title>
      <image:caption>계좌 무단거래는 발견 시각, 거래 내역, 카드·계좌 차단, 금융기관 신고, 경찰 또는 소비자기관 신고 기록을 빠르게 남겨야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/debit-bank-unauthorized-charge/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-debit-bank-unauthorized-charge/hero.svg</image:loc>
      <image:title>Debit Card or Bank Unauthorized Charge: Records and Reports to Make Fast</image:title>
      <image:caption>Unauthorized bank or debit transactions require fast records of discovery time, transaction details, account blocking, bank notice, and complaint records.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/credit-card-charge-dispute/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-credit-card-charge-dispute/hero.svg</image:loc>
      <image:title>신용카드 결제 이의제기: 차지백 전에 확인할 순서</image:title>
      <image:caption>신용카드 이의제기는 청구 오류, 미배송, 취소 미반영, 중복 결제처럼 사유를 분리하고 카드사 기한 안에 자료를 제출해야 한다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/credit-card-charge-dispute/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-credit-card-charge-dispute/hero.svg</image:loc>
      <image:title>Credit Card Charge Dispute: What to Check Before a Chargeback</image:title>
      <image:caption>Credit card disputes require separating billing errors, non-delivery, failed cancellation, and duplicate charges, then submitting evidence within issuer deadlines.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/return-refund-evidence-folder/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-return-refund-evidence-folder/hero.svg</image:loc>
      <image:title>반품과 환불 증거 폴더: 영수증, 사진, 대화 기록을 한곳에 모으기</image:title>
      <image:caption>반품·환불은 감정적 항의보다 구매 조건, 상품 상태, 반품 접수, 배송 증빙, 판매자 답변을 한 폴더로 묶는 편이 효과적이다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/return-refund-evidence-folder/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-return-refund-evidence-folder/hero.svg</image:loc>
      <image:title>Return and Refund Evidence Folder: Receipts, Photos, and Messages Together</image:title>
      <image:caption>Return and refund disputes are stronger when purchase terms, item condition, return request, shipping proof, and seller messages are stored in one folder.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/online-order-never-arrived/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-online-order-never-arrived/hero.svg</image:loc>
      <image:title>온라인 주문이 오지 않을 때: 배송 지연과 미배송을 구분하기</image:title>
      <image:caption>온라인 주문 분쟁은 주문일, 약속 배송일, 판매자 답변, 운송장 상태, 결제수단을 시간순으로 정리해야 해결 속도가 빨라진다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/online-order-never-arrived/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-online-order-never-arrived/hero.svg</image:loc>
      <image:title>Online Order Never Arrived: Separate Delay From Non-Delivery</image:title>
      <image:caption>Online order disputes move faster when order date, promised delivery, seller responses, tracking status, and payment method are placed on a timeline.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_consumer_rights/subscription-cancel-free-trial/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-subscription-cancel-free-trial/hero.svg</image:loc>
      <image:title>무료체험과 자동결제 해지: 캘린더와 증거를 먼저 남기기</image:title>
      <image:caption>무료체험은 체험 기간, 자동결제일, 해지 경로, 확인 메일을 함께 기록해야 예상하지 못한 반복 결제를 줄일 수 있다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_consumer_rights/subscription-cancel-free-trial/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2026-05-17-subscription-cancel-free-trial/hero.svg</image:loc>
      <image:title>Free Trial and Auto-Renewal Cancellation: Calendar and Evidence First</image:title>
      <image:caption>Free trials become safer when the trial period, renewal date, cancellation path, and confirmation email are recorded together.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-using-gitignore/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>.gitignore 파일을 사용하여 Git 추적에서 파일 제외하는 방법</image:title>
      <image:caption>`.gitignore` 파일을 생성하고 사용하여 특정 파일 및 디렉터리가 Git 저장소에 추가되는 것을 방지하는 방법을 알아보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-submodules/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git 서브모듈(Submodule)로 프로젝트 의존성 관리하기</image:title>
      <image:caption>`git submodule`을 사용하여 외부 저장소를 메인 프로젝트의 하위 디렉터리로 포함하고 관리하는 방법을 알아보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-rpc-failed-curl-56/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git 오류 해결: &quot;error: RPC failed; curl 56 Recv failure&quot;</image:title>
      <image:caption>네트워크 문제나 대용량 저장소 크기로 인해 자주 발생하는 Git의 &quot;error: RPC failed; curl 56 Recv failure&quot; 오류를 해결하고 수정하는 방법을 알아보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-resolving-merge-conflicts/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git 병합 충돌(Merge Conflict) 해결하는 방법</image:title>
      <image:caption>Git에서 브랜치를 합칠 때 발생하는 병합 충돌을 이해하고 해결하는 단계별 가이드입니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-lfs/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git LFS로 대용량 파일 관리하는 방법</image:title>
      <image:caption>Git LFS(Large File Storage)를 사용하여 작업 흐름을 늦추지 않고 Git 저장소의 대용량 바이너리 파일을 효율적으로 처리하는 방법을 알아보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-lf-will-be-replaced-by-crlf/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git 경고 해결: &quot;LF will be replaced by CRLF&quot;</image:title>
      <image:caption>크로스 플랫폼 프로젝트를 위한 줄 바꿈 정규화를 구성하여 Git의 &quot;LF will be replaced by CRLF&quot; 경고를 이해하고 해결하는 방법을 알아보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-interactive-rebase/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git Interactive Rebase로 커밋 수정하는 방법</image:title>
      <image:caption>`git rebase -i`를 사용하여 이전 커밋들을 합치거나, 수정하거나, 삭제하는 방법을 배워보세요. 프로젝트 히스토리를 더 깔끔하고 이해하기 쉽게 만들 수 있습니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-hooks/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git Hooks를 사용하여 작업 자동화하기</image:title>
      <image:caption>Git hooks를 사용하여 커밋 전이나 푸시 후와 같은 Git 작업 흐름의 특정 지점에서 사용자 지정 스크립트를 실행하는 방법을 알아보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-fatal-early-eof/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git 오류 해결: &quot;fatal: early EOF&quot;</image:title>
      <image:caption>일반적으로 원격 서버로부터의 불완전한 데이터 전송을 나타내는 Git의 &quot;fatal: early EOF&quot; 오류를 진단하고 수정하는 방법을 알아보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-fatal-could-not-read-username/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git 오류 해결: &quot;fatal: could not read Username for &apos;https://...&apos;: terminal prompts disabled&quot;</image:title>
      <image:caption>자격 증명 헬퍼를 사용하거나 SSH 인증으로 전환하여 Git 오류 &quot;fatal: could not read Username for &apos;https://...&apos;: terminal prompts disabled&quot;를 해결하는 방법을 알아보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-cherry-pick/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git에서 다른 브랜치의 특정 커밋 가져오기 (Cherry-Pick)</image:title>
      <image:caption>`git cherry-pick`을 사용하여 브랜치 전체를 병합하지 않고 다른 브랜치에 있는 특정 커밋만 현재 브랜치에 적용하는 방법을 알아보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-bisect/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>`git bisect`를 사용하여 버그를 유발한 커밋 찾기</image:title>
      <image:caption>`git bisect`를 사용하여 커밋 히스토리에서 이진 검색을 수행하고 버그를 유발한 정확한 커밋을 신속하게 찾아내는 방법에 대한 단계별 가이드입니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-using-gitignore/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Use .gitignore to Exclude Files from Git Tracking</image:title>
      <image:caption>Learn how to create and use a `.gitignore` file to prevent specific files and directories from being added to your Git repository.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-submodules/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Use Git Submodules to Manage Project Dependencies</image:title>
      <image:caption>Learn how to use `git submodule` to include and manage external repositories as subdirectories within your main project.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-rpc-failed-curl-56/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Fix &quot;error: RPC failed; curl 56 Recv failure&quot; in Git</image:title>
      <image:caption>Troubleshoot and fix the &quot;error: RPC failed; curl 56 Recv failure&quot; in Git, which is often caused by network issues or large repository sizes.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-resolving-merge-conflicts/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Resolve Merge Conflicts in Git</image:title>
      <image:caption>A step-by-step guide to understanding and resolving merge conflicts that occur when combining branches in Git.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-lfs/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Manage Large Files in Git with Git LFS</image:title>
      <image:caption>Learn how to use Git LFS (Large File Storage) to efficiently handle large binary files in your Git repository without slowing down your workflow.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-lf-will-be-replaced-by-crlf/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Fix &quot;LF will be replaced by CRLF&quot; Warning in Git</image:title>
      <image:caption>Understand and resolve the &quot;LF will be replaced by CRLF&quot; warning in Git by configuring line ending normalization for cross-platform projects.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-interactive-rebase/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Use Git Interactive Rebase to Modify Commits</image:title>
      <image:caption>Learn how to use `git rebase -i` to combine, edit, or delete previous commits for a cleaner and more understandable project history.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-hooks/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Automate Tasks with Git Hooks</image:title>
      <image:caption>Discover how to use Git hooks to trigger custom scripts at specific points in the Git workflow, such as before a commit or after a push.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-fatal-early-eof/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Fix &quot;fatal: early EOF&quot; Error in Git</image:title>
      <image:caption>Learn how to diagnose and fix the &quot;fatal: early EOF&quot; error in Git, which usually indicates an incomplete data transfer from the remote server.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-fatal-could-not-read-username/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Fix &quot;fatal: could not read Username for &apos;https://...&apos;: terminal prompts disabled&quot; in Git</image:title>
      <image:caption>Resolve the Git error &quot;fatal: could not read Username for &apos;https://...&apos;: terminal prompts disabled&quot; by using a credential helper or switching to SSH authentication.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-cherry-pick/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Cherry-Pick a Commit from Another Branch in Git</image:title>
      <image:caption>Learn how to use `git cherry-pick` to apply a specific commit from one branch to another without merging the entire branch.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-bisect/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Use `git bisect` to Find the Commit That Introduced a Bug</image:title>
      <image:caption>A step-by-step guide on using `git bisect` to perform a binary search on your commit history and quickly pinpoint the exact commit that caused a bug.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-typeerror-unsupported-operand-types/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>Python TypeError: unsupported operand type(s) for + 오류 해결 방법</image:title>
      <image:caption>Python에서 호환되지 않는 타입으로 연산을 시도할 때 발생하는 TypeError: unsupported operand type(s) for + 오류를 해결하세요. 이 가이드는 숫자, 문자열 및 기타 객체에 대한 타입 변환을 처리하는 방법을 설명합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-timeouterror-winerror-10060/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>Python TimeoutError: [WinError 10060] 연결 시도 실패 오류 해결 방법</image:title>
      <image:caption>네트워크 연결 시간 초과 시 발생하는 Python TimeoutError: [WinError 10060] 오류를 해결하는 방법을 알아보세요. 이 가이드는 방화벽, 잘못된 주소, 서버 문제 등 원인을 다루고 명확한 해결책을 제공합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-systemerror-returned-null-without-setting-error/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>Python SystemError:  returned NULL without setting an error 오류 해결 방법</image:title>
      <image:caption>드물지만 혼란스러운 Python SystemError:  returned NULL without setting an error 오류를 해결하세요. 이 가이드는 C 확장 모듈 문제나 손상된 설치와 같은 잠재적 원인을 탐색합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-permissionerror-errno-13-permission-denied/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>Python PermissionError: [Errno 13] Permission denied 오류 해결 방법</image:title>
      <image:caption>Python에서 파일 권한을 올바르게 관리하여 PermissionError: [Errno 13] Permission denied 오류를 해결하세요. 이 가이드는 원인을 설명하고 Windows, macOS, Linux용 해결책을 제공합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-notadirectoryerror-errno-20-not-a-directory/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>Python NotADirectoryError: [Errno 20] Not a directory 오류 해결 방법</image:title>
      <image:caption>Python에서 디렉터리 경로가 필요한 곳에 파일 경로를 사용하여 발생하는 NotADirectoryError: [Errno 20] Not a directory 오류를 이해하고 해결하세요. 경로를 검증하여 이 흔한 문제를 피하는 방법을 배웁니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-keyboardinterrupt/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>Python KeyboardInterrupt 예외 처리 방법</image:title>
      <image:caption>Python에서 KeyboardInterrupt는 사용자가 Ctrl+C를 눌러 프로그램을 강제 종료할 때 발생하는 예외입니다. 이 예외를 올바르게 처리하면 프로그램을 안전하게 종료하고 리소스를 정리할 수 있습니다. 이 글에서는 KeyboardInterrupt를 처리하는 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-isadirectoryerror-errno-21-is-a-directory/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>Python IsADirectoryError: [Errno 21] Is a directory 오류 해결 방법</image:title>
      <image:caption>Python에서 디렉터리를 파일처럼 다루려고 할 때 발생하는 IsADirectoryError: [Errno 21] Is a directory 오류를 해결하는 방법을 배우세요. 이 가이드는 경로를 확인하고 올바른 파일 작업을 사용하는 방법을 보여줍니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-floatingpointerror/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>Python FloatingPointError 해결 방법</image:title>
      <image:caption>Python에서 FloatingPointError는 부동 소수점 연산이 실패할 때 발생합니다. 이 오류는 일반적으로 잘 발생하지 않지만, 특정 수학적 계산에서 나타날 수 있습니다. 이 글에서는 FloatingPointError의 원인과 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-variables-var-vs-let-vs-const/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript 변수: var, let, const의 차이점</image:title>
      <image:caption>JavaScript에서 var, let, const의 차이점을 깊이 알아보세요. 스코프, 호이스팅, 재할당 규칙을 이해하여 더 깨끗하고 예측 가능하며 현대적인 JS 코드를 작성하세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-typeerror-reduce-of-empty-array-with-no-initial-value/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript TypeError: Reduce of empty array with no initial value 해결 방법</image:title>
      <image:caption>JavaScript에서 &quot;TypeError: Reduce of empty array with no initial value&quot;는 초기값 없이 빈 배열에 대해 reduce() 메서드를 호출할 때 발생하는 오류입니다. 이 글에서는 이 오류의 원인을 분석하고 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-syntaxerror-unterminated-string-literal/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript SyntaxError: Unterminated string literal 해결 방법</image:title>
      <image:caption>JavaScript에서 &quot;SyntaxError: Unterminated string literal&quot;은 문자열이 제대로 닫히지 않았을 때 발생하는 구문 오류입니다. 이 오류는 주로 따옴표나 줄 바꿈 문제로 인해 발생합니다. 이 글에서는 오류의 원인과 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-promise-all-vs-promise-race/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript 프로미스: Promise.all vs. Promise.race</image:title>
      <image:caption>여러 비동기 작업을 처리하기 위한 JavaScript의 Promise.all과 Promise.race의 차이점을 알아보세요. 모든 프로미스가 완료될 때까지 기다려야 하는 경우와 가장 먼저 완료된 프로미스에 따라 행동해야 하는 경우를 이해하세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-jquery-is-not-defined/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript &quot;jQuery is not defined&quot; 오류 해결 방법</image:title>
      <image:caption>흔한 &quot;Uncaught ReferenceError: jQuery is not defined&quot; 오류는 스크립트가 jQuery를 사용하기 전에 라이브러리가 올바르게 로드되었는지 확인하여 해결할 수 있습니다. 이 가이드는 원인과 해결책을 다룹니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-innerhtml-vs-textcontent/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript innerHTML vs. textContent: 어느 것을 사용해야 할까요?</image:title>
      <image:caption>JavaScript에서 innerHTML과 textContent의 주요 차이점을 이해하세요. 웹 애플리케이션에서 더 나은 보안, 성능 및 예측 가능성을 위해 각 속성을 언제 사용해야 하는지 알아보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-equality-double-vs-triple-equals/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript 동등 연산자: == vs. === (느슨한 비교 vs. 엄격한 비교)</image:title>
      <image:caption>JavaScript에서 느슨한 동등 연산자(==)와 엄격한 동등 연산자(===)의 중요한 차이점을 배우세요. 타입 강제 변환이 어떻게 작동하는지 이해하고, 일반적인 버그를 피하기 위해 거의 항상 ===를 사용해야 하는 이유를 알아보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-async-await-error-handling/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript async/await 오류 처리 마스터하기</image:title>
      <image:caption>JavaScript에서 try...catch 블록을 사용하여 async/await 함수의 오류를 올바르게 처리하는 방법을 배우세요. 처리되지 않은 프로미스 거부를 피하고, 견고하고 신뢰할 수 있는 비동기 코드를 작성하세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-try-with-resources/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java try-with-resources로 메모리 누수 방지하기</image:title>
      <image:caption>Java의 try-with-resources 구문을 사용하여 스트림이나 커넥션과 같은 리소스를 자동으로 닫고, 흔한 메모리 누수를 방지하며 코드를 더 깔끔하게 만드는 방법을 알아보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-string-vs-stringbuilder-vs-stringbuffer/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java: String vs. StringBuilder vs. StringBuffer 비교</image:title>
      <image:caption>Java에서 문자열을 다루는 세 가지 주요 클래스인 String, StringBuilder, StringBuffer의 핵심 차이점을 이해하여 더 효율적이고 최적화된 코드를 작성하는 방법을 알아보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-stream-api/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java Stream API로 데이터 처리하기</image:title>
      <image:caption>데이터 컬렉션 처리를 위한 Java Stream API의 강력한 기능을 알아보세요. 스트림을 사용하여 복잡한 데이터 조작을 위한 선언적이고 효율적이며 가독성 높은 코드를 작성하는 방법을 배웁니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-lambda-expressions/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java 람다 표현식(Lambda Expressions)으로 간결한 코드 작성하기</image:title>
      <image:caption>Java 람다 표현식이 무엇인지, 함수형 인터페이스의 사용을 어떻게 단순화하는지, 그리고 더 깔끔하고 표현력 있는 코드를 작성하기 위해 사용하는 방법을 알아보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-generics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java 제네릭(Generics)을 사용한 타입 안정성 확보</image:title>
      <image:caption>Java 제네릭이 어떻게 작동하는지, 컴파일 시점에 타입 안정성을 어떻게 제공하는지, 그리고 컬렉션 및 사용자 정의 클래스와 함께 사용하여 유연하고 재사용 가능한 코드를 만드는 방법을 알아보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-error-variable-might-not-have-been-initialized/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java &quot;error: variable ... might not have been initialized&quot; 해결 방법</image:title>
      <image:caption>Java에서 &quot;variable might not have been initialized&quot; 오류는 지역 변수가 사용되기 전에 값이 할당되었음을 보장할 수 없을 때 발생합니다. 이 문제를 해결하는 방법을 알아보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-error-unreachable-statement/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java &quot;error: unreachable statement&quot; 해결 방법</image:title>
      <image:caption>절대 실행될 수 없는 코드가 있을 때 발생하는 Java의 &quot;unreachable statement&quot; 컴파일 시간 오류의 원인을 이해하고 해결하는 방법을 알아보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-error-missing-return-statement/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java &quot;error: missing return statement&quot; 해결 방법</image:title>
      <image:caption>Java에서 &quot;error: missing return statement&quot; 오류는 반환 타입이 명시된 메서드의 모든 코드 경로가 값을 반환하도록 보장하지 않을 때 발생합니다. 이 문제를 해결하는 방법을 알아보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-error-illegalargumentexception/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java에서 IllegalArgumentException 처리하는 방법</image:title>
      <image:caption>IllegalArgumentException이 무엇인지, 왜 발생하는지, 그리고 메서드 인자를 검증하고 코드의 견고성을 향상시키기 위해 효과적으로 사용하는 방법을 알아보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-equals-and-hashcode/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java에서 equals()와 hashCode() 이해하기</image:title>
      <image:caption>Java에서 equals()를 오버라이드할 때 왜 항상 hashCode()도 오버라이드해야 하는지 알아보세요. 이 두 메서드 간의 규약을 이해하고 해시 기반 컬렉션에서 어떻게 동작하는지 확인합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-dependency-injection/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java 의존성 주입(Dependency Injection)으로 결합도 낮추기</image:title>
      <image:caption>의존성 주입(DI)의 원리를 이해하고, Spring과 같은 프레임워크 예제를 통해 Java에서 느슨하게 결합되고, 테스트하기 쉬우며, 유지보수하기 좋은 애플리케이션을 구축하는 데 어떻게 도움이 되는지 알아보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-checked-vs-unchecked-exceptions/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java 예외: Checked Exception vs. Unchecked Exception</image:title>
      <image:caption>Java의 checked exception과 unchecked exception의 차이점, 사용 시기, 그리고 코드 설계와 안정성에 미치는 영향을 알아보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-reverting-a-commit/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git에서 커밋을 되돌리는 방법 (git revert)</image:title>
      <image:caption>Git에서 특정 커밋의 변경 사항을 안전하게 되돌려야 할 때가 있습니다. &apos;git revert&apos;는 기존 커밋을 삭제하지 않고 변경 내용을 취소하는 새로운 커밋을 생성하여 이 문제를 해결합니다. 이 글에서는 git revert의 사용법과 장점을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-typeerror-unsupported-operand-types/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix Python TypeError: unsupported operand type(s) for +</image:title>
      <image:caption>Fix the TypeError: unsupported operand type(s) for + in Python by ensuring you are using compatible types in your operations. This guide explains how to handle type conversions for numbers, strings, and other objects.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-timeouterror-winerror-10060/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix Python TimeoutError: [WinError 10060] A connection attempt failed</image:title>
      <image:caption>Learn how to resolve the Python TimeoutError: [WinError 10060], which occurs when a network connection times out. This guide covers causes like firewalls, incorrect addresses, and server issues, providing clear solutions.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-systemerror-returned-null-without-setting-error/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix Python SystemError:  returned NULL without setting an error</image:title>
      <image:caption>Troubleshoot the rare but confusing SystemError:  returned NULL without setting an error in Python. This guide explores potential causes, such as issues with C extensions or corrupted installations.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-permissionerror-errno-13-permission-denied/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix Python PermissionError: [Errno 13] Permission denied</image:title>
      <image:caption>Resolve the PermissionError: [Errno 13] Permission denied in Python by learning how to manage file permissions correctly. This guide explains the causes and provides solutions for Windows, macOS, and Linux.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-notadirectoryerror-errno-20-not-a-directory/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix Python NotADirectoryError: [Errno 20] Not a directory</image:title>
      <image:caption>Understand and fix the NotADirectoryError: [Errno 20] Not a directory in Python. This error appears when a file path is used where a directory path is expected. Learn to validate paths and avoid this common issue.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-keyboardinterrupt/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Handle KeyboardInterrupt in Python</image:title>
      <image:caption>In Python, KeyboardInterrupt is an exception raised when the user presses Ctrl+C to forcefully terminate a program. Handling this exception correctly allows you to shut down your program gracefully and clean up resources. This post explains how to handle KeyboardInterrupt.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-isadirectoryerror-errno-21-is-a-directory/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix Python IsADirectoryError: [Errno 21] Is a directory</image:title>
      <image:caption>Learn to fix the IsADirectoryError: [Errno 21] Is a directory in Python. This error occurs when you try to treat a directory as a file. This guide shows you how to check paths and use the correct file operations.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-floatingpointerror/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix Python FloatingPointError</image:title>
      <image:caption>In Python, a FloatingPointError occurs when a floating-point operation fails. This error is not common but can appear in specific mathematical calculations. This post explains the causes of FloatingPointError and how to fix it.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-variables-var-vs-let-vs-const/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript Variables: The Difference Between var, let, and const</image:title>
      <image:caption>Dive into the differences between var, let, and const in JavaScript. Understand scope, hoisting, and reassignment rules to write cleaner, more predictable, and modern JS code.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-typeerror-reduce-of-empty-array-with-no-initial-value/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix JavaScript TypeError: Reduce of empty array with no initial value</image:title>
      <image:caption>In JavaScript, &quot;TypeError: Reduce of empty array with no initial value&quot; occurs when you call the reduce() method on an empty array without providing an initial value. This post analyzes the cause of this error and explains how to fix it.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-syntaxerror-unterminated-string-literal/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix JavaScript SyntaxError: Unterminated string literal</image:title>
      <image:caption>In JavaScript, &quot;SyntaxError: Unterminated string literal&quot; is a syntax error that occurs when a string is not closed properly. This error is usually caused by issues with quotes or line breaks. This post explains the causes of the error and how to fix it.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-promise-all-vs-promise-race/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript Promises: Promise.all vs. Promise.race</image:title>
      <image:caption>Learn the difference between Promise.all and Promise.race in JavaScript for handling multiple asynchronous operations. Understand when to wait for all promises to complete and when to act on the first one that settles.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-jquery-is-not-defined/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix &quot;jQuery is not defined&quot; Error in JavaScript</image:title>
      <image:caption>Resolve the common &quot;Uncaught ReferenceError: jQuery is not defined&quot; by ensuring the jQuery library is loaded correctly before your script attempts to use it. This guide covers the causes and solutions.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-innerhtml-vs-textcontent/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript innerHTML vs. textContent: Which Should You Use?</image:title>
      <image:caption>Understand the key differences between innerHTML and textContent in JavaScript. Learn when to use each property for better security, performance, and predictability in your web applications.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-equality-double-vs-triple-equals/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript Equality: == vs. === (Loose vs. Strict)</image:title>
      <image:caption>Learn the critical difference between loose equality (==) and strict equality (===) in JavaScript. Understand how type coercion works and why you should almost always use === to avoid common bugs.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-async-await-error-handling/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>Mastering async/await Error Handling in JavaScript</image:title>
      <image:caption>Learn how to properly handle errors in async/await functions using try...catch blocks in JavaScript. Avoid unhandled promise rejections and write robust, reliable asynchronous code.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-try-with-resources/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Prevent Memory Leaks with try-with-resources in Java</image:title>
      <image:caption>Learn how to use the try-with-resources statement in Java to automatically close resources like streams and connections, preventing common memory leaks and making your code cleaner.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-string-vs-stringbuilder-vs-stringbuffer/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java: String vs. StringBuilder vs. StringBuffer</image:title>
      <image:caption>Understand the key differences between String, StringBuilder, and StringBuffer in Java to write more efficient and optimized code for string manipulation.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-stream-api/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Processing Data with Java Stream API</image:title>
      <image:caption>Discover the power of the Java Stream API for processing collections of data. Learn how to use streams to write declarative, efficient, and readable code for complex data manipulations.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-lambda-expressions/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Writing Concise Code with Lambda Expressions in Java</image:title>
      <image:caption>Learn what Java Lambda Expressions are, how they simplify the use of functional interfaces, and how to use them to write cleaner, more expressive code.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-generics/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Using Generics in Java for Type Safety</image:title>
      <image:caption>Discover how Java Generics work, how they provide type safety at compile time, and how to use them to create flexible and reusable code with collections and custom classes.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-error-variable-might-not-have-been-initialized/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>How to Fix &quot;error: variable ... might not have been initialized&quot; in Java</image:title>
      <image:caption>Resolve the &quot;variable might not have been initialized&quot; error in Java by ensuring every local variable has a value before it is accessed.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-error-unreachable-statement/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>How to Fix &quot;error: unreachable statement&quot; in Java</image:title>
      <image:caption>Understand and fix the &quot;unreachable statement&quot; compile-time error in Java, which occurs when a piece of code can never be executed.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-error-missing-return-statement/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>How to Fix &quot;error: missing return statement&quot; in Java</image:title>
      <image:caption>Learn how to resolve the &quot;error: missing return statement&quot; in Java by ensuring all code paths in a method that declares a return type actually return a value.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-error-illegalargumentexception/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>How to Handle IllegalArgumentException in Java</image:title>
      <image:caption>Learn what IllegalArgumentException is, why it&apos;s thrown, and how to use it effectively to validate method arguments and improve code robustness.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-equals-and-hashcode/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Understanding equals() and hashCode() in Java</image:title>
      <image:caption>Learn why you must always override hashCode() if you override equals() in Java. Understand the contract between these two methods and how they work with hash-based collections.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-dependency-injection/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Lowering Coupling with Dependency Injection in Java</image:title>
      <image:caption>Understand the principle of Dependency Injection (DI) and how it helps in building loosely coupled, testable, and maintainable applications in Java, with examples from frameworks like Spring.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-checked-vs-unchecked-exceptions/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java Exceptions: Checked vs. Unchecked</image:title>
      <image:caption>Learn the difference between checked and unchecked exceptions in Java, when to use them, and how they impact your code&apos;s design and robustness.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-reverting-a-commit/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Revert a Commit in Git (git revert)</image:title>
      <image:caption>Sometimes you need to safely undo the changes from a specific commit in Git. &apos;git revert&apos; solves this by creating a new commit that undoes the changes without deleting the original commit. This post explains how to use git revert and its advantages.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-unicodedecodeerror/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>파이썬 &quot;UnicodeDecodeError: &apos;utf-8&apos; codec can&apos;t decode byte&quot; 오류 해결 방법</image:title>
      <image:caption>파이썬의 &quot;UnicodeDecodeError&quot;를 해결합니다. 이 오류는 기본 &apos;utf-8&apos; 코덱과 일치하지 않는 인코딩으로 파일을 읽을 때 발생합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-typeerror-object-is-not-iterable/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>파이썬 TypeError: &apos;...&apos; object is not iterable 해결 방법</image:title>
      <image:caption>파이썬에서 반복 불가능한(non-iterable) 객체를 순회하려고 할 때 발생하는 `TypeError: &apos;...&apos; object is not iterable` 오류의 원인과 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-typeerror-missing-required-positional-argument/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>파이썬 TypeError: missing 1 required positional argument 해결 방법</image:title>
      <image:caption>파이썬에서 함수나 메서드를 호출할 때 필수적인 위치 인자(positional argument)를 전달하지 않아 발생하는 `TypeError: missing 1 required positional argument` 오류의 원인과 해결책을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-runtimeerror-dictionary-changed-size-during-iteration/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>파이썬 RuntimeError: dictionary changed size during iteration 해결 방법</image:title>
      <image:caption>파이썬에서 딕셔너리를 순회하는 도중 크기를 변경하면 발생하는 `RuntimeError: dictionary changed size during iteration` 오류의 원인과 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-recursion-error/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>Python &quot;RecursionError: maximum recursion depth exceeded&quot; 해결 방법</image:title>
      <image:caption>Python에서 RecursionError는 재귀 호출의 깊이가 최대 한도를 초과할 때 발생합니다. 이 글에서는 오류의 원인과 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-os-error-no-space-left/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>Python &quot;OSError: [Errno 28] No space left on device&quot; 해결 방법</image:title>
      <image:caption>Python에서 &quot;OSError: [Errno 28] No space left on device&quot;는 디스크 공간이 부족할 때 발생합니다. 이 글에서는 오류의 원인과 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-memory-error/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>Python &quot;MemoryError&quot; 해결 방법</image:title>
      <image:caption>Python에서 MemoryError는 프로그램이 시스템의 가용 메모리를 모두 소진했을 때 발생합니다. 이 글에서는 MemoryError의 원인과 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-connection-refused/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>Python &quot;ConnectionError: [Errno 111] Connection refused&quot; 해결 방법</image:title>
      <image:caption>Python에서 &quot;Connection refused&quot; 오류는 네트워크 연결 시 대상 서버가 연결을 거부할 때 발생합니다. 이 글에서는 오류의 원인과 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-websocket-connection-failed/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript &quot;WebSocket connection to &apos;...&apos; failed&quot; 해결 방법</image:title>
      <image:caption>JavaScript에서 WebSocket 연결 실패는 다양한 원인으로 발생할 수 있습니다. 이 글에서는 &quot;WebSocket connection to &apos;...&apos; failed&quot; 오류의 일반적인 원인과 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-uncaught-in-promise/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>자바스크립트 Uncaught (in promise) 오류 해결 방법</image:title>
      <image:caption>자바스크립트에서 프로미스(Promise) 체인에서 발생한 예외가 처리되지 않았을 때 나타나는 `Uncaught (in promise)` 오류의 원인과 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-this-is-undefined/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript에서 &quot;this is undefined&quot; 문제 해결 방법</image:title>
      <image:caption>JavaScript에서 &apos;this&apos;는 호출 컨텍스트에 따라 동적으로 결정됩니다. 이로 인해 콜백 함수나 이벤트 핸들러에서 &apos;this&apos;가 undefined가 되는 문제가 자주 발생합니다. 이 글에서는 원인과 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-syntaxerror-unexpected-end-of-input/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>자바스크립트 SyntaxError: Unexpected end of input 해결 방법</image:title>
      <image:caption>자바스크립트 코드를 파싱하는 동안 엔진이 코드 블록의 끝을 예상치 못하게 만났을 때 발생하는 `SyntaxError: Unexpected end of input` 오류의 일반적인 원인과 해결책을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-syntaxerror-missing-parenthesis-after-argument-list/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>자바스크립트 SyntaxError: missing ) after argument list 해결 방법</image:title>
      <image:caption>자바스크립트에서 함수를 호출할 때 인자 목록 뒤에 닫는 괄호 `)`를 빠뜨려 발생하는 `SyntaxError: missing ) after argument list` 오류의 원인과 해결책을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-syntaxerror-invalid-or-unexpected-token/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript &quot;SyntaxError: Invalid or unexpected token&quot; 오류 해결 방법</image:title>
      <image:caption>이 포스트에서는 JavaScript 엔진이 언어의 구문 규칙을 위반하는 코드를 만났을 때 발생하는 &quot;SyntaxError: Invalid or unexpected token&quot; 오류의 해결 방법을 설명합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-referenceerror-assignment-to-undeclared-variable/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript &quot;ReferenceError: assignment to undeclared variable&quot; 오류 해결 방법</image:title>
      <image:caption>이 포스트는 JavaScript의 엄격 모드(strict mode)에서 선언되지 않은 변수에 값을 할당할 때 발생하는 &quot;ReferenceError: assignment to undeclared variable&quot; 오류를 해결하는 방법을 설명합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-insecure-mixed-content/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript &quot;Insecure mixed content&quot; 오류 해결 방법</image:title>
      <image:caption>&quot;Insecure mixed content&quot;는 HTTPS 페이지에서 안전하지 않은 HTTP 리소스를 로드할 때 발생하는 브라우저 보안 경고입니다. 이 글에서는 원인과 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-event-listener-leaks/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript 이벤트 리스너 메모리 누수 (Event Listener Leaks) 해결 방법</image:title>
      <image:caption>이벤트 리스너를 제거하지 않으면 메모리 누수가 발생하여 애플리케이션 성능이 저하될 수 있습니다. 이 글에서는 JavaScript에서 이벤트 리스너 누수의 원인과 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-numberformatexception/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>java.lang.NumberFormatException 해결 방법</image:title>
      <image:caption>부적절한 형식의 문자열을 숫자 값으로 변환하려고 할 때 발생하는 java.lang.NumberFormatException을 해결하는 방법을 알아보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-error-semicolon-expected/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java &quot;Error: &apos;;&apos; expected&quot; 해결 방법</image:title>
      <image:caption>Java에서 &quot;&apos;;&apos; expected&quot;는 문장의 끝을 나타내는 세미콜론이 누락되었을 때 발생하는 기본적인 컴파일 오류입니다. 이 글에서는 오류의 원인과 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-error-public-class-must-be-defined-in-file/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>자바 Error: a public class ... must be defined in a file called ... .java 해결 방법</image:title>
      <image:caption>자바에서 `public` 클래스의 이름과 `.java` 파일의 이름이 일치하지 않을 때 발생하는 컴파일 오류의 원인과 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-error-public-class-in-wrong-file/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java &quot;Error: a public class ... must be defined in a file called ... .java&quot; 해결 방법</image:title>
      <image:caption>Java에서 이 컴파일 오류는 public 클래스의 이름과 소스 파일의 이름이 일치하지 않을 때 발생합니다. 이 글에서는 오류의 원인과 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-error-incompatible-types/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java &quot;Error: incompatible types&quot; 해결 방법</image:title>
      <image:caption>Java에서 &quot;incompatible types&quot; 오류는 서로 호환되지 않는 타입의 값을 변수에 할당하거나 메서드에 전달하려고 할 때 발생하는 컴파일 오류입니다. 이 글에서는 원인과 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-error-cannot-find-symbol/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java &quot;Error: cannot find symbol&quot; 해결 방법</image:title>
      <image:caption>Java에서 &quot;cannot find symbol&quot;은 컴파일러가 코드에서 사용된 식별자(변수, 메서드, 클래스 등)를 찾을 수 없을 때 발생하는 매우 흔한 컴파일 오류입니다. 이 글에서는 원인과 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-concurrentmodificationexception/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java ConcurrentModificationException 처리 방법</image:title>
      <image:caption>Java에서 ConcurrentModificationException을 해결하는 방법을 배웁니다. 이 예외는 컬렉션을 반복하는 동안 수정될 때 발생합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-revert-vs-reset-safe-undo/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git revert와 reset 차이: 안전하게 커밋 되돌리기</image:title>
      <image:caption>공유 브랜치에서 Git 커밋을 되돌릴 때 git revert와 git reset 중 무엇을 써야 하는지, 안전한 선택 기준을 정리합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-resetting-a-commit/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git 커밋 되돌리기: git reset의 세 가지 옵션 (soft, mixed, hard) 완벽 가이드</image:title>
      <image:caption>git reset은 특정 커밋으로 프로젝트의 상태를 되돌리는 강력한 명령어입니다. 이 글에서는 git reset의 세 가지 주요 옵션인 --soft, --mixed, --hard의 차이점과 사용법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-fatal-index-file-corrupt/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git &quot;fatal: index file corrupt&quot; 해결 방법</image:title>
      <image:caption>Git에서 &quot;fatal: index file corrupt&quot;는 스테이징 영역의 상태를 추적하는 인덱스 파일이 손상되었을 때 발생합니다. 이 글에서는 오류의 원인과 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-fatal-bad-object/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git &quot;fatal: bad object&quot; 오류 해결 방법</image:title>
      <image:caption>이 가이드는 Git 저장소의 객체가 손상되거나 누락되었음을 나타내는 &quot;fatal: bad object&quot; 오류를 해결하는 방법을 설명합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-error-object-file-is-empty/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git &quot;error: object file ... is empty&quot; 해결 방법</image:title>
      <image:caption>Git에서 &quot;error: object file ... is empty&quot;는 Git 객체 파일이 손상되어 내용이 비어있을 때 발생합니다. 이 글에서는 오류의 원인과 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-detached-head-state/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git &quot;Detached HEAD&quot; 상태 해결 방법</image:title>
      <image:caption>Git의 &quot;Detached HEAD&quot; 상태가 무엇인지, 왜 발생하는지, 그리고 작업을 잃지 않고 안전하게 브랜치로 돌아가는 방법을 이해합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-amending-a-commit/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git 최신 커밋 수정하기: git commit --amend 완벽 가이드</image:title>
      <image:caption>git commit --amend는 가장 최근의 커밋을 수정할 수 있는 유용한 명령어입니다. 커밋 메시지를 변경하거나, 빠뜨린 파일을 추가하는 등 마지막 커밋을 보완할 때 사용합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-unicodedecodeerror/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix Python&apos;s &quot;UnicodeDecodeError: &apos;utf-8&apos; codec can&apos;t decode byte&quot;</image:title>
      <image:caption>Resolve the &quot;UnicodeDecodeError&quot; in Python. This error occurs when reading a file with an encoding that doesn&apos;t match the default &apos;utf-8&apos; codec.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-typeerror-object-is-not-iterable/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix Python TypeError: &apos;...&apos; object is not iterable</image:title>
      <image:caption>Learn how to fix the `TypeError: &apos;...&apos; object is not iterable` in Python, which occurs when you try to loop over a non-iterable object like an integer or None.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-typeerror-missing-required-positional-argument/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix Python TypeError: missing 1 required positional argument</image:title>
      <image:caption>Learn how to fix the `TypeError: missing 1 required positional argument` in Python, which occurs when you call a function or method without providing a mandatory positional argument.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-runtimeerror-dictionary-changed-size-during-iteration/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix Python RuntimeError: dictionary changed size during iteration</image:title>
      <image:caption>Learn how to fix the `RuntimeError: dictionary changed size during iteration` in Python, which occurs when you modify a dictionary while looping over it.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-recursion-error/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix &quot;RecursionError: maximum recursion depth exceeded&quot; in Python</image:title>
      <image:caption>In Python, a RecursionError occurs when the depth of recursive calls exceeds the maximum limit. This article explains the cause of the error and how to fix it.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-os-error-no-space-left/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix &quot;OSError: [Errno 28] No space left on device&quot; in Python</image:title>
      <image:caption>In Python, &quot;OSError: [Errno 28] No space left on device&quot; occurs when there is insufficient disk space. This article explains the causes of the error and how to fix it.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-memory-error/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix &quot;MemoryError&quot; in Python</image:title>
      <image:caption>In Python, a MemoryError occurs when the program exhausts the available system memory. This article explains the causes of MemoryError and how to fix it.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-connection-refused/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix &quot;ConnectionError: [Errno 111] Connection refused&quot; in Python</image:title>
      <image:caption>In Python, a &quot;Connection refused&quot; error occurs when a network connection is rejected by the target server. This article explains the causes of the error and how to fix it.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-websocket-connection-failed/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix &quot;WebSocket connection to &apos;...&apos; failed&quot; in JavaScript</image:title>
      <image:caption>A WebSocket connection failure in JavaScript can occur for various reasons. This article explores the common causes of the &quot;WebSocket connection to &apos;...&apos; failed&quot; error and how to resolve it.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-uncaught-in-promise/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix JavaScript Uncaught (in promise) Error</image:title>
      <image:caption>Learn how to resolve the `Uncaught (in promise)` error in JavaScript, which appears when a Promise rejection is not handled by a `.catch()` block or a try...catch statement.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-this-is-undefined/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix &quot;this is undefined&quot; in JavaScript</image:title>
      <image:caption>In JavaScript, &apos;this&apos; is dynamically determined by the calling context. This often leads to issues where &apos;this&apos; becomes undefined in callback functions or event handlers. This article explains why this happens and how to fix it.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-syntaxerror-unexpected-end-of-input/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix JavaScript SyntaxError: Unexpected end of input</image:title>
      <image:caption>Learn how to fix the `SyntaxError: Unexpected end of input` in JavaScript, which typically occurs when the parser unexpectedly reaches the end of the script due to missing brackets or braces.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-syntaxerror-missing-parenthesis-after-argument-list/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix JavaScript SyntaxError: missing ) after argument list</image:title>
      <image:caption>Learn how to fix the `SyntaxError: missing ) after argument list` in JavaScript, a common error caused by forgetting to add a closing parenthesis `)` after a function&apos;s argument list.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-syntaxerror-invalid-or-unexpected-token/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix &quot;SyntaxError: Invalid or unexpected token&quot; in JavaScript</image:title>
      <image:caption>This post explains how to resolve the &quot;SyntaxError: Invalid or unexpected token&quot; in JavaScript, which occurs when the JavaScript engine encounters code that violates the language&apos;s syntax rules.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-referenceerror-assignment-to-undeclared-variable/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix &quot;ReferenceError: assignment to undeclared variable&quot; in JavaScript</image:title>
      <image:caption>This post explains how to fix the &quot;ReferenceError: assignment to undeclared variable&quot; in JavaScript, which occurs in strict mode when you assign a value to a variable that has not been declared.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-insecure-mixed-content/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix &quot;Insecure mixed content&quot; Error in JavaScript</image:title>
      <image:caption>&quot;Insecure mixed content&quot; is a browser security warning that occurs when an HTTPS page loads insecure HTTP resources. This article explains the cause and how to fix it.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-event-listener-leaks/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix JavaScript Event Listener Leaks</image:title>
      <image:caption>Failing to remove event listeners can cause memory leaks and degrade application performance. This article explains the causes of event listener leaks in JavaScript and how to fix them.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-numberformatexception/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>How to Handle java.lang.NumberFormatException</image:title>
      <image:caption>Learn how to fix the java.lang.NumberFormatException, which occurs when you try to convert a string with an improper format into a numeric value.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-error-semicolon-expected/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>How to Fix &quot;Error: &apos;;&apos; expected&quot; in Java</image:title>
      <image:caption>In Java, &quot;&apos;;&apos; expected&quot; is a basic compilation error that occurs when a semicolon is missing at the end of a statement. This article explains the cause of the error and how to fix it.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-error-public-class-must-be-defined-in-file/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>How to Fix Java Error: a public class ... must be defined in a file called ... .java</image:title>
      <image:caption>Understand and resolve the Java compile error that occurs when the name of a `public` class does not match the name of its `.java` file.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-error-public-class-in-wrong-file/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>How to Fix &quot;Error: a public class ... must be defined in a file called ... .java&quot; in Java</image:title>
      <image:caption>This compilation error in Java occurs when the name of a public class does not match the name of its source file. This article explains the cause of the error and how to fix it.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-error-incompatible-types/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>How to Fix &quot;Error: incompatible types&quot; in Java</image:title>
      <image:caption>In Java, the &quot;incompatible types&quot; error is a compilation error that occurs when you try to assign a value of an incompatible type to a variable or pass it to a method. This article explains its causes and solutions.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-error-cannot-find-symbol/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>How to Fix &quot;Error: cannot find symbol&quot; in Java</image:title>
      <image:caption>In Java, &quot;cannot find symbol&quot; is a very common compilation error that occurs when the compiler cannot find the identifier (variable, method, class, etc.) used in the code. This article explains its causes and solutions.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-concurrentmodificationexception/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>How to Handle ConcurrentModificationException in Java</image:title>
      <image:caption>Learn how to fix ConcurrentModificationException in Java. This exception occurs when a collection is modified while it is being iterated over.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-revert-vs-reset-safe-undo/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git revert vs reset: How to Safely Undo a Commit</image:title>
      <image:caption>Learn when to use git revert instead of git reset so you can safely undo a commit without rewriting shared history.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-resetting-a-commit/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Undoing a Commit in Git: A Complete Guide to the Three Options of git reset (soft, mixed, hard)</image:title>
      <image:caption>git reset is a powerful command for reverting a project&apos;s state to a specific commit. This article explains the differences and usage of the three main options of git reset: --soft, --mixed, and --hard.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-fatal-index-file-corrupt/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Fix &quot;fatal: index file corrupt&quot; in Git</image:title>
      <image:caption>In Git, &quot;fatal: index file corrupt&quot; occurs when the index file, which tracks the staging area, is damaged. This article explains the cause of the error and how to fix it.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-fatal-bad-object/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Fix &quot;fatal: bad object&quot; Error in Git</image:title>
      <image:caption>This guide explains how to resolve the &quot;fatal: bad object&quot; error in Git, which indicates a corrupted or missing object in the Git repository.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-error-object-file-is-empty/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Fix &quot;error: object file ... is empty&quot; in Git</image:title>
      <image:caption>In Git, &quot;error: object file ... is empty&quot; occurs when a Git object file is corrupted and has no content. This article explains the cause of the error and how to fix it.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-detached-head-state/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Fix Git &quot;Detached HEAD&quot; State</image:title>
      <image:caption>Understand what a &quot;Detached HEAD&quot; state in Git is, why it happens, and how to safely get back to a branch without losing your work.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-amending-a-commit/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Amending the Latest Commit in Git: A Complete Guide to git commit --amend</image:title>
      <image:caption>git commit --amend is a useful command for modifying the most recent commit. It is used to fix the last commit, such as changing the commit message or adding forgotten files.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-taberror-inconsistent-use-of-tabs-and-spaces/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>파이썬 &apos;TabError: inconsistent use of tabs and spaces in indentation&apos; 오류 해결 방법</image:title>
      <image:caption>에디터를 설정하여 들여쓰기에 공백을 사용하고 기존 탭을 공백으로 변환하여 파이썬의 &quot;TabError: inconsistent use of tabs and spaces in indentation&quot; 오류를 해결하는 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-violation-click-handler-took-too-long/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript &apos;[Violation] &apos;click&apos; handler took ...ms&apos; 경고 해결 방법</image:title>
      <image:caption>`setTimeout`, Web Worker, `requestAnimationFrame`과 같은 기술을 사용하여 무거운 작업을 지연시켜 오래 실행되는 &apos;click&apos; 핸들러를 최적화하고 브라우저 응답성을 개선합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-failed-to-fetch/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript &apos;Failed to fetch&apos; 오류 해결 방법</image:title>
      <image:caption>JavaScript 코드에서 네트워크 문제, CORS 정책, 잘못된 요청 URL을 확인하여 &quot;Failed to fetch&quot; 오류를 해결하고 문제를 해결하는 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-unsupportedoperationexception/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>java.lang.UnsupportedOperationException 처리 방법</image:title>
      <image:caption>`Arrays.asList()`와 같이 수정 불가능한 컬렉션을 수정하려고 할 때 주로 발생하는 `UnsupportedOperationException`을 이해하고 해결하는 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-fatal-branch-already-exists/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git &apos;fatal: A branch named &apos;...&apos; already exists&apos; 오류 해결 방법</image:title>
      <image:caption>다른 이름을 선택하거나, 이전 브랜치를 삭제하거나, 기존 브랜치로 체크아웃하여 Git의 &quot;fatal: A branch named &apos;...&apos; already exists&quot; 오류를 해결하는 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-taberror-inconsistent-use-of-tabs-and-spaces/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix &apos;TabError: inconsistent use of tabs and spaces in indentation&apos; in Python</image:title>
      <image:caption>Resolve Python&apos;s &quot;TabError: inconsistent use of tabs and spaces in indentation&quot; by configuring your editor to use spaces for indentation and converting existing tabs to spaces.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-violation-click-handler-took-too-long/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix &apos;[Violation] &apos;click&apos; handler took ...ms&apos; in JavaScript</image:title>
      <image:caption>Optimize long-running &apos;click&apos; handlers and improve browser responsiveness by deferring heavy tasks with techniques like `setTimeout`, Web Workers, and `requestAnimationFrame`.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-failed-to-fetch/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix &apos;Failed to fetch&apos; Errors in JavaScript</image:title>
      <image:caption>Troubleshoot and fix the &quot;Failed to fetch&quot; error by checking for network issues, CORS policies, and incorrect request URLs in your JavaScript code.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-unsupportedoperationexception/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>How to Handle java.lang.UnsupportedOperationException</image:title>
      <image:caption>Understand and resolve `UnsupportedOperationException` in Java, which typically occurs when trying to modify unmodifiable collections like those from `Arrays.asList()`.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-fatal-branch-already-exists/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Fix &apos;fatal: A branch named &apos;...&apos; already exists&apos; in Git</image:title>
      <image:caption>Resolve the &quot;fatal: A branch named &apos;...&apos; already exists&quot; error in Git by choosing a different name, deleting the old branch, or checking out the existing one.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-zerodivisionerror-division-by-zero/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>Python ZeroDivisionError: division by zero 해결 방법</image:title>
      <image:caption>나누기를 수행하기 전에 제수가 0인지 확인하여 Python의 &apos;ZeroDivisionError: division by zero&apos;를 예방합니다. 견고한 오류 처리를 위해 조건문과 try-except 블록을 사용하는 방법을 배웁니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-valueerror-invalid-literal-for-int/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>Python ValueError: invalid literal for int() with base 10 해결 방법</image:title>
      <image:caption>변환하려는 문자열이 유효한 정수인지 확인하여 Python의 &apos;ValueError: invalid literal for int()&apos;를 해결합니다. 안전한 변환을 위해 try-except 블록을 사용하고, str.isdigit() 메서드로 유효성을 검사하는 법을 배웁니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-unboundlocalerror-local-variable-referenced-before-assignment/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>Python UnboundLocalError: local variable referenced before assignment 해결 방법</image:title>
      <image:caption>변수 스코프를 이해하여 Python의 UnboundLocalError를 해결합니다. `global` 및 `nonlocal` 키워드를 사용하거나, 변수가 접근되기 전에 항상 함수 스코프 내에서 값이 할당되도록 하는 방법을 배웁니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-importerror-cannot-import-name/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>&quot;Python &quot;ImportError: cannot import name &apos;...&apos; from &apos;...&apos;&quot; 오류 해결 방법&quot;</image:title>
      <image:caption>&quot;순환 참조, 오타, 잘못된 모듈 경로를 확인하여 Python의 &quot;ImportError: cannot import name &apos;...&apos; from &apos;...&apos;&quot; 오류를 해결하세요.&quot;</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-uncaught-urierror-uri-malformed/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript에서 Uncaught URIError: URI malformed 오류 해결 방법</image:title>
      <image:caption>URI 디코딩 함수를 사용하기 전에 문자열이 올바르게 형식화되었는지 확인하여 JavaScript의 &apos;Uncaught URIError: URI malformed&apos; 오류를 이해하고 해결합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-typeerror-is-not-a-function/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>&quot;JavaScript &quot;TypeError: &apos;...&apos; is not a function&quot; 오류 해결 방법&quot;</image:title>
      <image:caption>&quot;호출하려는 변수가 실제 함수인지 확인하고, 스코프 문제나 오타를 점검하여 JavaScript의 &quot;TypeError: &apos;...&apos; is not a function&quot; 오류를 해결하세요.&quot;</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-typeerror-assignment-to-constant/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript &quot;TypeError: Assignment to constant variable&quot; 오류 해결 방법</image:title>
      <image:caption>`const`의 속성을 배우고, 재할당이 필요한 변수에는 `let`을 사용하여 JavaScript의 &quot;TypeError: Assignment to constant variable&quot; 오류를 이해하고 해결하세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-syntaxerror-invalid-token/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript &quot;SyntaxError: Invalid or unexpected token&quot; 오류 해결 방법</image:title>
      <image:caption>오타, 쉼표나 괄호와 같은 문자 누락, 잘못된 구문을 확인하여 JavaScript의 &quot;SyntaxError: Invalid or unexpected token&quot; 오류를 해결하세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-referenceerror-undeclared-variable/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript &quot;ReferenceError: assignment to undeclared variable&quot; 오류 해결 방법</image:title>
      <image:caption>값을 할당하기 전에 `let`, `const` 또는 `var`로 변수를 올바르게 선언하여 JavaScript의 strict mode에서 발생하는 &quot;ReferenceError: assignment to undeclared variable&quot; 오류를 해결하세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-cross-origin-read-blocking/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>Cross-Origin Read Blocking (CORB) 오류 해결 방법</image:title>
      <image:caption>서버가 올바른 Content-Type 및 CORS 헤더를 전송하도록 하여 브라우저의 Cross-Origin Read Blocking (CORB) 경고를 해결하는 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-stackoverflowerror/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java StackOverflowError 해결 방법</image:title>
      <image:caption>코드에서 무한 재귀를 식별하여 Java의 StackOverflowError를 이해하고 해결합니다. 재귀 함수를 디버깅하고, 반복적인 해결책으로 리팩토링하며, 필요할 때 스레드 스택 크기를 늘리는 방법을 배웁니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-sqlexception/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java &quot;java.sql.SQLException&quot; 예외 처리 방법</image:title>
      <image:caption>데이터베이스 연결, 구문을 올바르게 관리하고 try-catch-finally 블록을 사용하여 리소스가 닫히도록 보장함으로써 java.sql.SQLException을 처리하는 방법을 배웁니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-outofmemoryerror/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java OutOfMemoryError 해결 방법</image:title>
      <image:caption>메모리 누수나 불충분한 힙 크기와 같은 원인을 파악하여 Java의 OutOfMemoryError를 이해하고 해결합니다. 힙 덤프를 분석하고 JVM 설정을 조정하여 이 심각한 오류를 예방하는 방법을 배웁니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-numberformatexception-handling/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java NumberFormatException 예외 처리 방법</image:title>
      <image:caption>파싱 전 문자열을 검증하고, 안전한 숫자 변환을 위해 try-catch 블록을 사용하여 Java의 NumberFormatException을 예방하고 처리하는 방법을 배웁니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-noclassdeffounderror/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java NoClassDefFoundError 해결 방법</image:title>
      <image:caption>컴파일 시점에는 있었지만 런타임에 누락된 클래스로 인해 발생하는 Java의 NoClassDefFoundError의 원인을 이해하고 해결합니다. 클래스패스를 확인하고, 의존성을 관리하며, 정적 초기화 실패를 수정하는 방법을 배웁니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-ioexception/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java에서 java.io.IOException 이해하고 처리하기</image:title>
      <image:caption>`try-catch` 블록과 `try-with-resources`를 사용하여 I/O 작업이 실패하거나 중단되었음을 알리는 체크 예외 `java.io.IOException`을 처리하는 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-illegalstateexception/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java IllegalStateException 해결 방법</image:title>
      <image:caption>Java의 IllegalStateException의 원인을 이해하고 객체가 올바른 상태에 있을 때만 메서드를 호출하여 해결하는 방법을 배웁니다. 실용적인 예제를 통해 확인하세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-illegalargumentexception/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java IllegalArgumentException 예외 처리 방법</image:title>
      <image:caption>메서드 시작 시 명시적 검사를 수행하여 인수가 유효한지 확인하고, Java의 IllegalArgumentException을 효과적으로 사용하고 처리하는 방법을 배웁니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-filenotfoundexception/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java `java.io.FileNotFoundException` 해결 방법</image:title>
      <image:caption>파일 경로, 권한을 확인하고 올바른 리소스 처리 방법을 사용하여 `java.io.FileNotFoundException`을 해결하는 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-classcastexception/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Java에서 java.lang.ClassCastException 해결 방법</image:title>
      <image:caption>객체를 캐스팅하기 전에 `instanceof`와 같은 검사를 통해 타입 안전성을 확보하여 `java.lang.ClassCastException`을 이해하고 예방하는 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-the-requested-url-returned-error-403/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git 오류 해결: The requested URL returned error: 403</image:title>
      <image:caption>Git의 &apos;403 Forbidden&apos; 오류를 자격 증명 업데이트, 개인용 액세스 토큰(PAT) 사용, 또는 저장소 권한 확인을 통해 해결하세요. 이 흔한 인증 문제를 해결하는 단계를 배웁니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-refusing-to-merge-unrelated-histories/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git에서 &apos;fatal: refusing to merge unrelated histories&apos; 오류 해결 방법</image:title>
      <image:caption>두 프로젝트의 커밋 기록이 다를 때 `--allow-unrelated-histories` 플래그를 사용하여 Git의 &apos;fatal: refusing to merge unrelated histories&apos; 오류를 해결하는 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-permission-denied-publickey/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git 오류 해결: Permission Denied (publickey)</image:title>
      <image:caption>SSH 키를 올바르게 생성하고, ssh-agent에 추가하고, Git 호스팅 제공업체에 등록하여 Git의 &apos;Permission denied (publickey)&apos; 오류를 해결하는 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-fatal-unable-to-access-url-returned-error-404/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git 오류 해결: unable to access &apos;...&apos;: The requested URL returned error: 404</image:title>
      <image:caption>Git의 &apos;404 Not Found&apos; 오류를 원격 URL의 오타 확인, 저장소 존재 및 권한 검증, 올바른 인증을 통해 해결하세요. 이 흔한 URL 관련 문제를 해결하는 방법을 배웁니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-fatal-pathspec-did-not-match/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>&quot;Git &quot;fatal: pathspec &apos;...&apos; did not match any files&quot; 오류 해결 방법&quot;</image:title>
      <image:caption>&quot;오타, 올바른 파일 경로를 확인하고, 필요 시 파일이 Git에 의해 추적되고 있는지 확인하여 &quot;fatal: pathspec &apos;...&apos; did not match any files&quot; Git 오류를 해결하세요.&quot;</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-fatal-pathspec-did-not-match-any-files/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git 오류 해결: pathspec &apos;...&apos; did not match any files</image:title>
      <image:caption>Git의 &apos;pathspec did not match any files&apos; 오류를 오타 확인, 파일 경로 검증, 특수 문자 처리 방법 이해를 통해 해결하세요. 이 흔한 문제를 진단하고 고치는 법을 배웁니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-failed-to-push-some-refs/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git에서 &apos;error: failed to push some refs to&apos; 오류 해결 방법</image:title>
      <image:caption>원격 저장소의 최신 변경 사항을 가져온 후 자신의 변경 사항을 푸시하여 Git의 &apos;failed to push some refs&apos; 오류를 해결합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-error-src-refspec-does-not-match-any/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git &apos;error: src refspec ... does not match any&apos; 오류 해결 방법</image:title>
      <image:caption>푸시하려는 브랜치가 로컬에 존재하고 이름이 올바르게 입력되었는지 확인하여 Git &quot;src refspec ... does not match any&quot; 오류를 해결하는 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-error-local-changes-overwritten-by-merge/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>&quot;Git &quot;error: Your local changes... would be overwritten by merge&quot; 오류 해결 방법&quot;</image:title>
      <image:caption>pull 또는 merge 전에 로컬 변경 사항을 스태시, 커밋 또는 폐기하여 Git 병합 오류를 해결하세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-error-403-forbidden/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git &quot;The requested URL returned error: 403&quot; 오류 해결 방법</image:title>
      <image:caption>자격 증명을 업데이트하거나, 개인용 액세스 토큰(PAT)을 사용하거나, 더 안전한 액세스를 위해 SSH 인증으로 전환하여 Git 403 Forbidden 오류를 해결하세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-zerodivisionerror-division-by-zero/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix Python&apos;s ZeroDivisionError: division by zero</image:title>
      <image:caption>Prevent Python&apos;s &apos;ZeroDivisionError: division by zero&apos; by checking if the divisor is zero before performing a division. Learn to use conditional statements and try-except blocks for robust error handling.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-valueerror-invalid-literal-for-int/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix Python&apos;s ValueError: invalid literal for int() with base 10</image:title>
      <image:caption>Resolve Python&apos;s &apos;ValueError: invalid literal for int()&apos; by ensuring the string you are converting is a valid integer. Learn to use try-except blocks for safe conversion and the str.isdigit() method for validation.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-unboundlocalerror-local-variable-referenced-before-assignment/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix Python&apos;s UnboundLocalError: local variable referenced before assignment</image:title>
      <image:caption>Resolve Python&apos;s UnboundLocalError by understanding variable scope. Learn to use the `global` and `nonlocal` keywords or ensure a variable is always assigned a value within a function&apos;s scope before it is accessed.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-importerror-cannot-import-name/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>&quot;How to Fix Python&apos;s \&quot;ImportError: cannot import name &apos;...&apos; from &apos;...&apos;\&quot;&quot;</image:title>
      <image:caption>&quot;Resolve Python&apos;s \&quot;ImportError: cannot import name &apos;...&apos; from &apos;...&apos;\&quot; by checking for circular imports, typos, and incorrect module paths.&quot;</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-uncaught-urierror-uri-malformed/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix Uncaught URIError: URI malformed in JavaScript</image:title>
      <image:caption>Understand and resolve the JavaScript &apos;Uncaught URIError: URI malformed&apos; by ensuring strings are correctly formatted before using URI decoding functions.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-typeerror-is-not-a-function/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix &quot;TypeError: &apos;...&apos; is not a function&quot; in JavaScript</image:title>
      <image:caption>Fix the &quot;TypeError: &apos;...&apos; is not a function&quot; in JavaScript by ensuring the variable you are calling is actually a function and checking for scope issues or typos.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-typeerror-assignment-to-constant/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix &quot;TypeError: Assignment to constant variable&quot; in JavaScript</image:title>
      <image:caption>Understand and fix the &quot;TypeError: Assignment to constant variable&quot; in JavaScript by learning the properties of `const` and using `let` for variables that need to be reassigned.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-syntaxerror-invalid-token/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix &quot;SyntaxError: Invalid or unexpected token&quot; in JavaScript</image:title>
      <image:caption>Resolve the &quot;SyntaxError: Invalid or unexpected token&quot; in JavaScript by checking for typos, missing characters like commas or parentheses, and incorrect syntax.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-referenceerror-undeclared-variable/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix &quot;ReferenceError: assignment to undeclared variable&quot; in JavaScript</image:title>
      <image:caption>Resolve the &quot;ReferenceError: assignment to undeclared variable&quot; in JavaScript&apos;s strict mode by properly declaring variables with `let`, `const`, or `var` before assigning values.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-cross-origin-read-blocking/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix Cross-Origin Read Blocking (CORB) Errors</image:title>
      <image:caption>Resolve Cross-Origin Read Blocking (CORB) warnings in your browser by ensuring the server sends the correct Content-Type and CORS headers for your API requests.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-stackoverflowerror/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>How to Fix Java&apos;s StackOverflowError</image:title>
      <image:caption>Understand and resolve Java&apos;s StackOverflowError by identifying infinite recursion in your code. Learn how to debug recursive functions, refactor them into iterative solutions, and increase the thread stack size when necessary.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-sqlexception/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>How to Handle java.sql.SQLException in Java</image:title>
      <image:caption>Learn to handle java.sql.SQLException by properly managing database connections, statements, and using try-catch-finally blocks to ensure resources are closed.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-outofmemoryerror/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>How to Fix Java&apos;s OutOfMemoryError</image:title>
      <image:caption>Understand and resolve Java&apos;s OutOfMemoryError by identifying its causes, such as memory leaks or insufficient heap size. Learn how to analyze heap dumps and tune JVM settings to prevent this critical error.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-numberformatexception-handling/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>How to Handle NumberFormatException in Java</image:title>
      <image:caption>Learn to prevent and handle Java&apos;s NumberFormatException by validating strings before parsing and using try-catch blocks for safe numeric conversion.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-noclassdeffounderror/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>How to Fix Java&apos;s NoClassDefFoundError</image:title>
      <image:caption>Resolve Java&apos;s NoClassDefFoundError by understanding its cause: a class that was present at compile time is missing at runtime. Learn to check your classpath, manage dependencies, and fix static initializer failures.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-ioexception/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>Understanding and Handling java.io.IOException in Java</image:title>
      <image:caption>Learn how to handle the checked exception `java.io.IOException`, which signals that an I/O operation has failed or been interrupted, by using `try-catch` blocks and `try-with-resources`.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-illegalstateexception/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>How to Fix Java&apos;s IllegalStateException</image:title>
      <image:caption>Understand and resolve Java&apos;s IllegalStateException by ensuring methods are called only when an object is in the appropriate state. Learn through practical examples.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-illegalargumentexception/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>How to Handle IllegalArgumentException in Java</image:title>
      <image:caption>Learn to use and handle Java&apos;s IllegalArgumentException effectively by performing explicit checks at the beginning of your methods to ensure arguments are valid.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-filenotfoundexception/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>How to Fix java.io.FileNotFoundException in Java</image:title>
      <image:caption>Learn how to resolve the java.io.FileNotFoundException by checking file paths, permissions, and using proper resource handling techniques.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-classcastexception/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>How to Fix java.lang.ClassCastException in Java</image:title>
      <image:caption>Understand and prevent `java.lang.ClassCastException` by ensuring type safety with checks like `instanceof` before casting objects.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-the-requested-url-returned-error-403/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Fix Git Error: The requested URL returned error: 403</image:title>
      <image:caption>Resolve Git&apos;s &apos;403 Forbidden&apos; error by updating your credentials, using a personal access token (PAT), or checking your repository permissions. Learn the steps to fix this common authentication issue.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-refusing-to-merge-unrelated-histories/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Fix &apos;fatal: refusing to merge unrelated histories&apos; in Git</image:title>
      <image:caption>Learn how to resolve the &apos;fatal: refusing to merge unrelated histories&apos; error in Git by using the `--allow-unrelated-histories` flag when two projects have different commit histories.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-permission-denied-publickey/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Fix Git Error: Permission Denied (publickey)</image:title>
      <image:caption>Resolve the &apos;Permission denied (publickey)&apos; error in Git by correctly generating an SSH key, adding it to the ssh-agent, and registering it with your Git hosting provider.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-fatal-unable-to-access-url-returned-error-404/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Fix Git Error: unable to access &apos;...&apos;: The requested URL returned error: 404</image:title>
      <image:caption>Resolve Git&apos;s &apos;404 Not Found&apos; error by checking the remote URL for typos, verifying repository existence and permissions, and ensuring you are authenticated correctly. Learn to fix this common URL-related issue.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-fatal-pathspec-did-not-match/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Fix &quot;fatal: pathspec &apos;...&apos; did not match any files&quot; in Git</image:title>
      <image:caption>Resolve the Git error &quot;fatal: pathspec &apos;...&apos; did not match any files&quot; by checking for typos, correct file paths, and ensuring the file is tracked by Git when necessary.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-fatal-pathspec-did-not-match-any-files/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Fix Git Error: pathspec &apos;...&apos; did not match any files</image:title>
      <image:caption>Resolve the Git error &apos;pathspec did not match any files&apos; by checking for typos, verifying file paths, and understanding how Git handles special characters. Learn to troubleshoot and fix this common issue.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-failed-to-push-some-refs/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Fix &apos;error: failed to push some refs to&apos; in Git</image:title>
      <image:caption>Resolve the Git error &apos;failed to push some refs&apos; by fetching the latest changes from the remote repository before pushing your own.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-error-src-refspec-does-not-match-any/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Fix &apos;error: src refspec ... does not match any&apos; in Git</image:title>
      <image:caption>Resolve the Git error &quot;src refspec ... does not match any&quot; by ensuring the branch you are trying to push exists locally and the name is spelled correctly.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-error-local-changes-overwritten-by-merge/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Fix &quot;error: Your local changes to the following files would be overwritten by merge&quot; in Git</image:title>
      <image:caption>Resolve the Git merge error by stashing, committing, or discarding your local changes before pulling or merging.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-error-403-forbidden/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Fix &quot;The requested URL returned error: 403&quot; in Git</image:title>
      <image:caption>Resolve the Git 403 Forbidden error by updating your credentials, using a personal access token (PAT), or switching to SSH authentication for more secure access.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-typeerror-can-only-concatenate-str-not-int-to-str/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>Python TypeError: can only concatenate str (not &apos;int&apos;) to str 해결 방법</image:title>
      <image:caption>Python에서 &apos;TypeError: can only concatenate str (not &apos;int&apos;) to str&apos;는 문자열에 정수와 같은 다른 타입의 데이터를 직접 연결하려 할 때 발생합니다. 이 오류의 원인과 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-syntaxerror-invalid-syntax/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>Python SyntaxError: invalid syntax 오류 완벽 가이드</image:title>
      <image:caption>Python에서 가장 흔한 오류 중 하나인 SyntaxError: invalid syntax의 원인과 해결 방법을 쉽고 명확하게 설명합니다. 콜론 누락, 괄호 불일치 등 다양한 예시를 통해 문법 오류를 빠르게 해결하세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-nameerror-name-is-not-defined/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>Python NameError: name &apos;...&apos; is not defined 오류 해결 방법</image:title>
      <image:caption>변수나 함수가 정의되기 전에 사용될 때 발생하는 Python NameError의 원인과 해결 방법을 알아봅니다. 오타, 변수 범위 등 흔한 원인을 확인하세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-modulenotfounderror/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>Python ModuleNotFoundError 해결 방법</image:title>
      <image:caption>Python에서 발생하는 ModuleNotFoundError: No module named &apos;...&apos; 오류의 원인을 파악하고, 이를 해결하기 위한 다양한 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-keyerror/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>Python KeyError 해결 방법: 딕셔너리 키 오류</image:title>
      <image:caption>Python에서 존재하지 않는 딕셔너리 키에 접근할 때 발생하는 KeyError의 원인을 이해하고, 이를 해결하는 효과적인 방법들을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-indexerror-list-index-out-of-range/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>Python &apos;IndexError: list index out of range&apos; 오류 해결 방법</image:title>
      <image:caption>Python의 &apos;IndexError: list index out of range&apos; 오류의 원인과 해결책을 알아봅니다. 리스트 길이 확인, 올바른 반복문 사용 등 오류를 방지하는 방법을 확인하세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-indentationerror-expected-an-indented-block/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>Python IndentationError: expected an indented block 오류 해결법</image:title>
      <image:caption>Python의 핵심 문법인 들여쓰기! IndentationError의 원인과 해결 방법을 명확히 알아보고, 탭과 공백 혼용 문제를 해결하여 깔끔한 코드를 작성하는 방법을 배워보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-filenotfounderror/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>Python FileNotFoundError 해결 방법</image:title>
      <image:caption>Python에서 파일을 다룰 때 흔히 발생하는 FileNotFoundError: [Errno 2] No such file or directory 오류의 원인과 해결책을 상세히 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-attributeerror-nonetype/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>Python AttributeError: &apos;NoneType&apos; object has no attribute &apos;...&apos; 해결 방법</image:title>
      <image:caption>Python에서 자주 발생하는 오류인 AttributeError: &apos;NoneType&apos; object has no attribute &apos;...&apos;의 원인을 파악하고 이를 방지하는 방법을 상세히 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-uncaught-typeerror-cannot-read-properties-of-undefined/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript &apos;undefined&apos;의 속성을 읽을 수 없음(Uncaught TypeError) 오류 해결 방법</image:title>
      <image:caption>JavaScript에서 &apos;Uncaught TypeError: Cannot read properties of undefined&apos; 오류가 발생하는 원인을 파악하고, 효과적인 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-uncaught-syntaxerror-unexpected-token/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript 오류 &apos;Uncaught SyntaxError: Unexpected token&apos; 해결 방법</image:title>
      <image:caption>&apos;Uncaught SyntaxError: Unexpected token&apos;은 JavaScript 엔진이 문법적으로 예상치 못한 토큰을 만났을 때 발생하는 구문 오류입니다. 이 오류의 일반적인 원인과 해결책을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-uncaught-referenceerror-is-not-defined/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript 오류 &apos;Uncaught ReferenceError: is not defined&apos; 해결 방법</image:title>
      <image:caption>&apos;Uncaught ReferenceError: ... is not defined&apos;는 JavaScript에서 변수나 함수가 선언되지 않았거나 접근할 수 없는 스코프에 있을 때 발생하는 흔한 오류입니다. 원인과 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-uncaught-rangeerror-maximum-call-stack-size-exceeded/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript &apos;Maximum call stack size exceeded&apos; 오류 해결 방법</image:title>
      <image:caption>JavaScript에서 &apos;Uncaught RangeError: Maximum call stack size exceeded&apos; 오류가 발생하는 원인인 무한 재귀를 파악하고, 함수에 올바른 종료 조건을 구현하여 문제를 해결하는 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-typeerror-cannot-read-properties-of-null/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>JavaScript TypeError: Cannot read properties of null 오류 해결하기</image:title>
      <image:caption>JavaScript 개발자라면 누구나 한 번쯤 마주치는 &apos;Cannot read properties of null&apos; 오류. 이 오류의 원인을 명확히 이해하고, DOM 로딩 시점과 조건부 접근을 통해 효과적으로 해결하는 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-nullpointerexception-npe/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>자바 NullPointerException (NPE) 완벽 정복 가이드</image:title>
      <image:caption>자바 개발자의 영원한 숙제, NullPointerException(NPE)의 발생 원인을 알아보고, null 체크, Optional, 어노테이션 등 NPE를 방지하고 우아하게 처리하는 다양한 실용적인 방법을 배워보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-arrayindexoutofboundsexception/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>java.lang.ArrayIndexOutOfBoundsException 해결 방법</image:title>
      <image:caption>java.lang.ArrayIndexOutOfBoundsException은 배열의 유효한 인덱스 범위를 벗어나 접근할 때 발생하는 흔한 런타임 예외입니다. 이 글에서는 오류의 원인과 해결 방법을 자세히 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-fatal-remote-origin-already-exists/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git 오류 &apos;fatal: remote origin already exists&apos; 해결 방법</image:title>
      <image:caption>&apos;fatal: remote origin already exists&apos;는 원격 저장소를 추가하려 할 때 &apos;origin&apos;이라는 이름이 이미 사용 중일 때 발생하는 오류입니다. 이 글에서는 원인과 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-fatal-not-a-git-repository/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Git 오류 &apos;fatal: not a git repository&apos; 해결 방법</image:title>
      <image:caption>&apos;fatal: not a git repository&apos;는 Git 명령을 Git 저장소가 아닌 디렉터리에서 실행했을 때 발생하는 일반적인 오류입니다. 이 글에서는 원인과 해결 방법을 알아봅니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-typeerror-can-only-concatenate-str-not-int-to-str/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix Python TypeError: can only concatenate str (not &apos;int&apos;) to str</image:title>
      <image:caption>The &apos;TypeError: can only concatenate str (not &apos;int&apos;) to str&apos; in Python occurs when you try to concatenate a string with a non-string type, like an integer. This article explains the cause and how to fix it.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-syntaxerror-invalid-syntax/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>A Complete Guide to Python&apos;s SyntaxError: invalid syntax</image:title>
      <image:caption>Clearly understand and resolve one of Python&apos;s most common errors: SyntaxError: invalid syntax. Learn to fix issues like missing colons, mismatched parentheses, and more with simple examples.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-nameerror-name-is-not-defined/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix Python&apos;s NameError: name &apos;...&apos; is not defined</image:title>
      <image:caption>Understand and fix the Python NameError, which occurs when a variable or function is used before it&apos;s defined. Learn common causes like typos and scope issues.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-modulenotfounderror/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix ModuleNotFoundError in Python</image:title>
      <image:caption>A guide to resolving the ModuleNotFoundError: No module named &apos;...&apos; in Python. Learn how to install and manage modules to avoid this common error.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-keyerror/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix Python&apos;s KeyError: &apos;...&apos;</image:title>
      <image:caption>Learn how to fix the Python KeyError, which occurs when you try to access a key that does not exist in a dictionary. This guide covers several effective methods.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-indexerror-list-index-out-of-range/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix Python&apos;s IndexError: list index out of range</image:title>
      <image:caption>Learn how to fix the &apos;IndexError: list index out of range&apos; in Python. This guide covers common causes and solutions, including checking list length and using loops correctly.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-indentationerror-expected-an-indented-block/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix Python&apos;s IndentationError: expected an indented block</image:title>
      <image:caption>Master Python&apos;s core syntax: indentation! Understand the causes of and solutions for IndentationError, fix mixed tabs and spaces, and learn to write clean, error-free code.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-filenotfounderror/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix FileNotFoundError in Python</image:title>
      <image:caption>A detailed guide on how to handle the FileNotFoundError: [Errno 2] No such file or directory in Python. Learn the common causes and effective solutions.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-attributeerror-nonetype/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix AttributeError: &apos;NoneType&apos; object has no attribute &apos;...&apos;</image:title>
      <image:caption>A comprehensive guide to understanding and fixing the common Python error: AttributeError: &apos;NoneType&apos; object has no attribute &apos;...&apos;. Learn why it occurs and how to prevent it.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-uncaught-typeerror-cannot-read-properties-of-undefined/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix Uncaught TypeError: Cannot read properties of undefined</image:title>
      <image:caption>Learn how to resolve the &apos;Uncaught TypeError: Cannot read properties of undefined&apos; error in JavaScript by identifying its causes and applying effective solutions.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-uncaught-syntaxerror-unexpected-token/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix &apos;Uncaught SyntaxError: Unexpected token&apos; in JavaScript</image:title>
      <image:caption>&apos;Uncaught SyntaxError: Unexpected token&apos; is a syntax error that occurs when the JavaScript engine encounters a token that it does not expect grammatically. This article explores the common causes and solutions for this error.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-uncaught-referenceerror-is-not-defined/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix &apos;Uncaught ReferenceError: is not defined&apos; in JavaScript</image:title>
      <image:caption>&apos;Uncaught ReferenceError: ... is not defined&apos; is a common error in JavaScript that occurs when a variable or function is not declared or is outside the accessible scope. Let&apos;s explore its causes and solutions.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-uncaught-rangeerror-maximum-call-stack-size-exceeded/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix &apos;Maximum call stack size exceeded&apos; in JavaScript</image:title>
      <image:caption>Resolve the &apos;Uncaught RangeError: Maximum call stack size exceeded&apos; in JavaScript by identifying infinite recursion and implementing proper base cases in your functions.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-typeerror-cannot-read-properties-of-null/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix JavaScript&apos;s TypeError: Cannot read properties of null</image:title>
      <image:caption>Every JavaScript developer encounters &apos;Cannot read properties of null&apos;. Clearly understand its cause and learn how to effectively fix it by managing DOM loading times and using conditional access.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-nullpointerexception-npe/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>A Complete Guide to Conquering Java&apos;s NullPointerException (NPE)</image:title>
      <image:caption>Explore the causes of Java&apos;s infamous NullPointerException (NPE) and learn practical, effective methods to prevent and handle it gracefully using null checks, Optional, annotations, and more.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-arrayindexoutofboundsexception/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>How to Fix java.lang.ArrayIndexOutOfBoundsException</image:title>
      <image:caption>java.lang.ArrayIndexOutOfBoundsException is a common runtime exception that occurs when you try to access an array with an invalid index. This article explains the causes of the error and how to fix it.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-fatal-remote-origin-already-exists/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Fix &apos;fatal: remote origin already exists&apos; in Git</image:title>
      <image:caption>The &apos;fatal: remote origin already exists&apos; error occurs when you try to add a remote named &apos;origin&apos; that is already in use. This article explains the cause and how to resolve it.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-fatal-not-a-git-repository/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Fix &apos;fatal: not a git repository&apos; Error</image:title>
      <image:caption>The &apos;fatal: not a git repository&apos; error is a common issue that occurs when you run a Git command in a directory that is not a Git repository. This article explains the causes and how to fix it.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/javascript-typeerror-undefined-not-function/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>TypeError: undefined is not a function 오류 해결 방법 (JavaScript)</image:title>
      <image:caption>TypeError: undefined is not a function 오류 원인과 해결책을 다룬다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/java-nullpointerexception-java/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>How to Fix &quot;ModuleNotFoundError: No module named &apos;…&apos;&quot; in Python</image:title>
      <image:caption>NullPointerException은 null 참조 접근 시 발생. null 검사, Optional, 초기화, 어노테이션 사용으로 예방.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/javascript-typeerror-undefined-not-function/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_js.png</image:loc>
      <image:title>How to Fix &quot;TypeError: undefined is not a function&quot; in JavaScript</image:title>
      <image:caption>&quot;TypeError: undefined is not a function&quot; occurs when code attempts to call a value that isn&apos;t a function. Learn to identify the root cause—such as typos, load order issues, or incorrect imports—and apply targeted fixes.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/java-nullpointerexception-java/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_java.png</image:loc>
      <image:title>How to Fix &quot;NullPointerException&quot; Error in Java</image:title>
      <image:caption>NullPointerException happens when code accesses a null reference. Prevent it with null checks, proper initialization, Optional, and nullability annotations.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-modulenotfounderror-no-module-named/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title> ModuleNotFoundError: No module named ‘…’ 오류 해결 방법</image:title>
      <image:caption>Python에서 모듈을 찾지 못해 발생하는 `ModuleNotFoundError`의 주요 원인과 해결책을 정리. 패키지 설치, 가상환경 활성화, 경로 설정, 이름 충돌 방지 방법 안내.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-modulenotfounderror-no-module-named/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix &quot;ModuleNotFoundError: No module named &apos;…&apos;&quot; in Python</image:title>
      <image:caption>&quot;Learn to resolve Python&apos;s &apos;ModuleNotFoundError&apos; by installing the correct package, activating the right environment, and checking your import paths.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/git-permission-denied-publickey-windows/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>Permission denied (publickey) 오류 해결 방법 (Windows Git SSH)</image:title>
      <image:caption>Git SSH 연결 시 발생하는 “Permission denied (publickey) 오류를 SSH 키 생성, 에이전트 등록, 공개키 업로드로 해결하는 방법.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/git-permission-denied-publickey-windows/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_git.png</image:loc>
      <image:title>How to Fix &quot;Permission denied (publickey)&quot; Error with Git on Windows</image:title>
      <image:caption>Fix Git&apos;s &quot;Permission denied (publickey)&quot; error on Windows by creating an SSH key, adding it to the SSH agent, and registering it with your Git host.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_troubleshooting/python-certificate-verify-failed/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>SSL: CERTIFICATE_VERIFY_FAILED 오류 해결 방법 (Windows Python)</image:title>
      <image:caption>Windows Python에서 SSL: CERTIFICATE_VERIFY_FAILED 오류를 certifi 설치, REQUESTS_CA_BUNDLE/SSL_CERT_FILE 설정, 올바른 CA 번들 사용으로 해결하는 방법.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_troubleshooting/python-certificate-verify-failed/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/header_images/overlay_image_python.png</image:loc>
      <image:title>How to Fix &quot;SSL: CERTIFICATE_VERIFY_FAILED&quot; Error in Python on Windows</image:title>
      <image:caption>Learn to fix the SSL: CERTIFICATE_VERIFY_FAILED error in Python on Windows by installing certifi, setting REQUESTS_CA_BUNDLE or SSL_CERT_FILE, and using a proper CA bundle.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/easy-labeling-guide-1/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2025-07-20-easy-labeling-guide-1/image-20250720232427171.png</image:loc>
      <image:title>Easy Labeling 가이드 (1) - 이미지와 라벨 불러오기</image:title>
      <image:caption>YOLO 라벨링 툴 Easy Labeling의 첫 번째 가이드입니다. PC에서 이미지 폴더와 라벨 파일을 불러오고, 클래스 파일을 활용하는 기본적인 방법을 안내합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/easy-labeling-guide-1/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2025-07-20-easy-labeling-guide-1/image-20250720232427171.png</image:loc>
      <image:title>Easy Labeling Guide (1) - Loading Images and Labels</image:title>
      <image:caption>This is the first guide for the YOLO labeling tool, Easy Labeling. It provides basic instructions on how to load image folders and label files from your PC and how to use class files.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/easy-labeling-in-depth-features/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2025-07-15-introducing-easy-labeling-in-depth-features/image-20250715235507837.png</image:loc>
      <image:title>YOLO 라벨링 끝판왕, Easy Labeling 주요 기능 파헤치기</image:title>
      <image:caption>AI 객체 탐지를 위한 YOLO 데이터 라벨링, 아직도 힘드신가요? Easy Labeling의 강력한 기능으로 데이터셋 구축 시간을 단축하세요. 로컬 파일 연동, 고급 Annotation 기능, 효율적인 단축키 등 YOLO 라벨링 생산성을 극대화하는 모든 비법을 공개합니다.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/easy-labeling-in-depth-features/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2025-07-15-introducing-easy-labeling-in-depth-features/image-20250715235507837.png</image:loc>
      <image:title>A Deep Dive into Easy Labeling&apos;s Features for YOLO Data Labeling</image:title>
      <image:caption>Unlock maximum efficiency in your YOLO data labeling workflow. This guide explores Easy Labeling&apos;s powerful features, from local file access and advanced annotation tools to smart label management for object detection. Everything you need for efficient dataset creation is here.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/ko_easy_labeling/easy-labeling-development/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2025-07-13-easy-labeling-development/image-20250715203036663.png</image:loc>
      <image:title>YOLO 데이터 라벨링, 설치 없이 웹에서 바로! Easy Labeling 개발기</image:title>
      <image:caption>YOLO 객체 탐지 모델 학습, 데이터 라벨링 때문에 힘드셨나요? 설치가 필요 없는 웹 기반 YOLO 라벨링 도구, Easy Labeling의 개발 과정과 주요 기능을 소개합니다. 로컬 파일을 직접 사용하여 빠르고 안전하게 인공지능 데이터셋을 구축하는 방법을 알아보세요.</image:caption>
    </image:image>
  </url>
  

  
  
  <url>
    <loc>https://mouseball54.github.io/en_easy_labeling/easy-labeling-development/</loc>
    <image:image>
      <image:loc>https://mouseball54.github.io/images/2025-07-13-introducing-easy-labeling/image-20250715203044117.png</image:loc>
      <image:title>Introducing Easy Labeling: A Free Web-Based Tool for YOLO Object Detection</image:title>
      <image:caption>Discover Easy Labeling, a free, web-based image annotation tool designed for YOLO object detection. Create high-quality datasets for computer vision projects with full YOLO format support, local file processing for speed and privacy, and no installation required.</image:caption>
    </image:image>
  </url>
  

</urlset>
